Use Case · Support

Knowledge base on the Software Lifecycle Cloud

A knowledge base on KERNSTACK is the publishing and retrieval layer for help content in one project: articles live as files in a bucket with their versions, text and vector indexes are declared over them, feedback lands in a table, and the same corpus can power both the public help pages and the assistant your product queries at runtime.

Object BucketsFull-Text SearchVector SearchEdge Gateway
Talk to us Read Technical Documentation → Software Lifecycle Cloud →

The engineering bottleneck with assembled stacks

Writers publish articles into a help-center tool while the product team maintains a second, stale copy for in-app answers. Feedback — “this article did not solve it” — evaporates into the tool’s dashboard, so the articles that fail are indistinguishable from the ones that work, and every AI feature the company attempts starts by re-collecting a corpus it already pays to store.

Architecture on the Software Lifecycle Cloud

Articles are bucket objects, so publishing is a file operation with versions kept beside the current text. Indexes declared over the bucket make the corpus searchable by readers and retrievable by functions. A small table keyed by article and day collects helpful/not-helpful marks from the help UI, which gives editors a repair queue ranked by evidence.

One corpus for humans and machines

The structural decision is refusing to fork the corpus. The article a customer reads on the help site and the passage an assistant retrieves are the same object in the same bucket. Fix the wording once and both surfaces improve; retire an article and it leaves the index instead of lingering in a vector copy nobody remembers to purge.

  • Draft and published states are bucket prefixes; the help site is a gateway prefix route over the published prefix
  • Feedback marks keyed by article expose the worst-performing pages without an analytics project
  • Release notes can join the corpus as dated articles, so “what changed” becomes searchable too

Editorial workflow without a CMS procurement

Writers keep working in Markdown or HTML files; the project supplies versions, search, and delivery. What this deliberately is not: a visual CMS with roles and approval chains. Teams that need editorial workflow software should keep it — and can still sync its output into the bucket so the product retrieves from the same corpus customers read.

FAQ

Frequently asked questions

It replaces the storage and delivery of articles, and adds product-side retrieval. If your team values a visual editor and editorial roles, keep the tool for writing and publish its output into the bucket; do not keep two divergent corpora.

As files: keep dated copies beside the current article in the bucket and let the index point at the published prefix. Rollback is publishing the previous file again — a bucket operation, not a database restore.

Yes. Feedback is rows in a table keyed by article, so a simple function or an internal page lists articles by down-votes. That table is also where support deflection quality gets measured over time.

Connected in the Project Graph

Related capabilities, architectures, and comparisons

Category PillarThe Software Lifecycle CloudWhy people and agents build, deploy, and operate on a single vertically integrated stack.Service · DataBucketsObject storage with presigned uploadService · DataSearchFull-text search over project recordsService · RetrievalVector searchVector and hybrid retrievalService · EdgeGatewayHTTP, WebSocket, and prefix routesIndustry SolutionE-commerce Cloud SolutionsE-commerce on KERNSTACK owns the parts of commerce that constitute the business: the catalogue and its search, carts and checkout state, the order lifecycle, raw payment events reconciled into provable order states, and fulfilment workflows with human steps for the exceptions. Cards stay with the payment provider; the data that makes the business worth buying moves onto infrastructure the merchant controls, in Europe.Use Case · ProductExperiment assignmentAssignment is a pure function of the subject key and the experiment’s salt — stable across requests, no coordination needed. The function records the assignment row once and serves the variant; outcome handlers were already writing events, which now simply carry the experiment id the assignment returned. Analysis reads assignments and outcomes from neighbouring tables with the same keys.Use Case · AgenciesAgency client deliveryThe studio’s delivery shape is a template stack.json: gateway, functions or workers in the client’s stack languages, tables, buckets, and apps under one target per client, on European infrastructure the studio can name in the pitch. Previews run the same declaration; the client’s approval happens in the bound conversation with a live link. Every client’s meter is separate by construction — the studio sees delivery cost per client without allocation spreadsheets.

Ship your stack on the Software Lifecycle Cloud.

Closed preview on dedicated European infrastructure. Bring a repository or start from a blueprint.

Talk to us See pricing & credits →