Use Case · Content

Content delivery on the Software Lifecycle Cloud

Content delivery on KERNSTACK serves published content from the same project as the product: drafts and published pages are bucket objects under separate prefixes, a gateway prefix route delivers them — CDN-enabled where traffic justifies it — and editors publish by moving a file, with the API that reads the same content declared one route away. One project, one deploy story, no CMS host with its own uptime personality.

Object BucketsEdge GatewayCDN EdgeApproval Workflows
Talk to us Read Technical Documentation → Software Lifecycle Cloud →

The engineering bottleneck with assembled stacks

Editors publish pages onto a CMS host while the product lives elsewhere, so every page is a small treaty between two systems: the marketing site’s deploy rhythm against the product’s, the CMS’s outage against the launch calendar, and content the app needs (pricing tables, legal text, help snippets) copied by hand between them until the copies disagree.

Architecture on the Software Lifecycle Cloud

Content is files with states: draft prefix, published prefix, and archived versions beside them. Publishing promotes a file; the prefix route serves the published tree with a default key, canonical redirects, and hard 404s for what does not exist (fallback_mode: not_found, so analytics stays honest). Apps fetch the same objects at runtime through the routes file the platform writes, instead of baking URLs into builds.

Promotion as a file move

Because publishing is a bucket operation, the editorial controls are boring in the best way: who may write the published prefix, which workflow step approves a page, when the scheduled launch promotes it. A workflow can hold publication at a human step — legal reads the landing page before it exists publicly — and the whole event is in the project’s history.

  • Draft and published states are prefixes; rollback is republishing the previous file
  • Legal or brand approval becomes a human workflow step before promotion, recorded with a name
  • Content is delivered from your zone with optional CDN on the route — no second host to secure

What this is not

It is not a visual CMS: no page builder, no editorial roles product, no media library UI. Teams that need those keep their CMS for writing and publish its output here — delivery, versioning, and the API-adjacent content come home, which is where the operational pain actually lived.

FAQ

Frequently asked questions

By promoting files from the draft prefix to the published prefix — through whatever editing tool produced them, or a small admin app in the same project. Promotion can be gated by a workflow’s human step when a page needs legal eyes.

Yes. A workflow with a time-based step performs the promotion at launch time; the page exists in draft until the moment it should not, and the scheduled run is visible in the project like any other workflow.

Yes. Apps and functions read the published objects or their extracted fields from the same bucket, so the pricing page and the in-app pricing table stop being two hand-synced truths.

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 · EdgeGatewayHTTP, WebSocket, and prefix routesService · EdgeCDNCached delivery for apps and assetsService · OrchestrationWorkflowsDurable workflows with human pausesIndustry 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 →