Definition: Blueprint
A blueprint is a starter scaffold for a KERNSTACK workload — for example func-go-minimal for a Go function or work-nodejs-minimal for a Node.js worker — copied into the project by kernstack add and published in the template gallery.
What a blueprint contains
A blueprint is the smallest honest version of a workload: the function or worker source in its conventional directory (functions/{name}, workers/{name}), the stack.json entry that declares it, and any route needed to call it. It is code you own from the moment it lands — no generator lock-in, no hidden layer — so the second commit is already yours, not the scaffold’s.
Where blueprints come from
Starters are declared in blueprint.json files and synchronised into the template gallery at build time, which keeps the gallery and the scaffolds the same objects. A full-stack demonstration (platform-full-stack-demo) shows the pieces composed; minimal blueprints show one piece at a time, which is the order people actually learn a stack in.
Frequently asked questions
No. kernstack add copies the starter once; from then on the files are ordinary project source under your version control. Updating them is editing, not re-scaffolding.
That is the normal path: the scaffold writes the first declaration, and every later resource is added by editing the file and reviewing the plan. Blueprints start projects; they do not govern them.
Yes — platform-full-stack-demo composes functions, data, and an app into one runnable project. Most teams learn more by starting minimal and adding resources as the plan teaches them the model.
Related capabilities, architectures, and comparisons
Ship your stack on the Software Lifecycle Cloud.
Closed preview on dedicated European infrastructure. Bring a repository or start from a blueprint.