Templates Gallery · Official CLI Blueprints
Scaffold a runnable stack in one command.
Start from an atomic WebAssembly function or container worker in Go, Node.js, Python, or PHP — or initialize the complete full-stack platform reference demo.
function · go Go WebAssembly HTTP Function Starter (func-go-minimal) Minimal Go function: a single HTTP handler returning 'hello world'. Scaffold a Go HTTP function compiled to WebAssembly, wired into stack.json and the KERNSTACK gateway in one CLI command. demo · go-python-sveltekit KERNSTACK Full-Stack Platform Reference Demo (kernstack init --demo) Platform demonstration: web app plus REST, GraphQL, tables, websockets, presigned upload, image transform, worker volumes, and a workflow with human approval. Scaffold the complete multi-service architecture in one command. worker · go Go Container Worker Starter (work-go-minimal) Minimal Go worker that responds with 'hello from worker' on every invoke. Run compiled Go binaries as managed container workers on KERNSTACK — built for heavy compute, streaming pipelines, and volume-mounted workloads. worker · nodejs Node.js Container Worker Starter (work-nodejs-minimal) Minimal Node.js worker that responds with 'hello from nodejs worker' on every invoke. Deploy Node.js backends, webhook consumers, and full-stack SSR workers on KERNSTACK with the official Node.js SDK and zero AWS configuration. worker · php PHP Container Worker Starter (work-php-minimal) Minimal PHP worker that responds with 'hello from php worker' on every invoke. Bring PHP workloads, agency client backends, and commerce integrations onto the Software Lifecycle Cloud with declarative infrastructure in stack.json. worker · python Python Worker Starter for AI & Data (work-python-minimal) Minimal Python worker that responds with 'hello from python worker' on every invoke. Run Python data pipelines, document chunkers, and AI orchestration workers next to your KERNSTACK Tables, Vector Search, and Inference endpoints.
FAQ
Frequently asked questions
Use kernstack init --demo for the full-stack platform demonstration, or kernstack add function|worker <name> --blueprint <id> to add an atomic Go, Node.js, Python, or PHP template to your project.
Yes. Scaffolding a function or worker automatically vendors the matching language SDK into .kernstack/sdk-<lang>-v1/.
Yes. Every template in this gallery is generated directly from the blueprint.json manifests in the official KERNSTACK blueprints repository.
Connected in the Project Graph
Related capabilities, architectures, and comparisons
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.Use Case · AgentsAgent operations consoleThe raw material already exists in the project: hosted git lists branches including agent/<id>, each agent branch maps to its environment, and every deploy begins as a plan a person approved. The console view arranges that material — branch, environment URL, plan summary, approval state — into the board engineering managers actually ask for, with conversations and board topics carrying the discussion around each run.Use Case · AgentsAI agent backendHosted git carries the repository; agent branches namespace the experiments. The agent edits code and stack.json together, runs kernstack plan --json to verify its own change set, and a reviewer checks the same plan. Environments multiply cheaply because a project is declared, not hand-assembled: the agent-<id> environment runs the branch’s stack for click-through review.Use Case · OperationsApproval workflowThe workflow declares the path: extraction or computation steps first, then the human step, then whatever the approval unlocks — payment release, publication, shipment. Approvers see a queue of titled tasks with the underlying record one click deep; their decision resumes the run with the outcome as data the next steps can branch on. Timeouts and reminders are part of the declaration, so a three-day-old approval nags its owner automatically.Use Case · ComplianceAudit log platformThe audit table is keyed by the audited record’s id with time as the sort key, so a record’s whole history is one ordered read. Write paths either emit entries explicitly — best for business meaning (“discount approved by”) — or lean on a table change stream that invokes a function with batched item changes. Retention windows and legal holds are fields the archiving worker respects.
Ship your stack on the Software Lifecycle Cloud.
Closed preview on dedicated European infrastructure. Bring a repository or start from a blueprint.