Use Case · Product

GraphQL API on the Software Lifecycle Cloud

A GraphQL API on KERNSTACK is your GraphQL server, run properly: a nodejs worker hosts the schema and resolvers, resolvers read the project’s tables and buckets through the SDK, and the gateway exposes one route to it. Honest framing first: KERNSTACK has no native GraphQL product — what it gives the pattern is the declared backend behind the schema, so resolvers, data, and files share one project and one review.

Container WorkersEdge GatewayNoSQL TablesObject Buckets
Talk to us Read Technical Documentation → Software Lifecycle Cloud →

The engineering bottleneck with assembled stacks

Frontend engineers want one query surface over several stores and end up operating a federation hobby: a gateway process on a VM, resolvers reaching into three vendors’ databases, and a schema whose production shape exists nowhere in git. The query language delivered the ergonomics; the plumbing underneath stayed artisanal.

Architecture on the Software Lifecycle Cloud

The worker is the GraphQL server (your framework of choice), deployed beside the data it resolves. Tables are keyed for resolver patterns — by id, by owner, by time — and persisted queries can be stored as rows when clients are first-party apps. Gateway routing keeps the endpoint private or public per environment, and the schema file lives in the repository the worker deploys from, versioned with the resolvers.

Resolvers over keyed data, honestly

GraphQL does not repeal data modelling: resolvers that fan out into per-field table reads will feel it at scale, exactly as anywhere else. The stack’s contribution is colocation and declaration — the worker, tables, and buckets are one project, so the N+1 you inevitably write is visible, measurable, and fixable in one repo instead of across vendor boundaries.

  • Schema and resolvers version together in git; the worker deploys from the same stack.json as its data
  • Persisted queries for first-party clients are table rows, so the allowed-query list is data you can audit
  • Files resolve to presigned bucket URLs — GraphQL returns references, never proxies bytes

When REST-shaped routes are simpler

If your clients are your own two apps with stable screens, screen-shaped routes (the mobile-BFF pattern) may serve you with less machinery. GraphQL earns the worker when genuinely different clients shape genuinely different queries over the same data — and this stack hosts that honestly, as code you own.

FAQ

Frequently asked questions

No, and this page will not pretend otherwise. You run your GraphQL server as a nodejs worker; KERNSTACK provides the declared tables, buckets, gateway route, and deploy discipline around it. The schema stays your code, framework and all.

Through the KERNSTACK SDK against the project’s tables and buckets, with access keys injected inside deployed workers. Key design follows resolver patterns — predictable, because your schema is known at declaration time.

Yes. Store approved query documents as table rows keyed by hash; the worker resolves only hashes it finds. That list is auditable data, so “what can the app ask our backend” has a literal answer.

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 · ComputeWorkersContainer workers for long jobsService · EdgeGatewayHTTP, WebSocket, and prefix routesService · DataTablesServerless key-value and document tablesService · DataBucketsObject storage with presigned uploadIndustry 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 →