Why teams replace assembled cloud services with KERNSTACK Functions
Teams otherwise run a Lambda, an API gateway, and a log group per route, wired by hand. On KERNSTACK the handler, its route, and its triggers are one declaration, so the public surface of a project can be read from a single file.
Where functions run
Anywhere a request-shaped event exists: an http route, a websocket route (websockets must target functions), a cron schedule on the function entry, a table’s change_stream delivering batched item changes, or a workflow step. The handler signature is one shape — func handler(ctx, req) (resp, error) — and change-stream records arrive with old and new items, so idempotent handlers are straightforward to write.
What functions deliberately are not
Functions are Go only. JavaScript, TypeScript, Python, and PHP handlers run as workers, and work that outlives a request belongs there too. The split is the platform’s central honesty: one runtime done properly for short-lived handlers, container processes for everything else, both declared side by side.
- Metered at 0.01 credits per GiB-second of execution; uncalled functions cost nothing
- Scoped deploys exist: kernstack deploy --only function:api ships one handler
- Local iteration is built in: kernstack serve --function api, kernstack logs --function api
SDKs & Language Integration
Every KERNSTACK environment vendors typed SDK packages into .kernstack/ so both engineers and coding agents in Agent Sandboxes can call Functions without external credentials:
- Go SDK:
github.com/coding-berlin/kernstack-sdk-go/sdk_functions - Node.js SDK:
kernstack-sdk - Python SDK:
kernstack_sdk - PHP SDK:
Kernstack\Functions
European alternatives to the hyperscaler equivalent
Implementation guides for Functions
Frequently asked questions
Go, compiled to WebAssembly. Other languages are not squeezed into the function runtime — Node.js, Python, and PHP run as workers with their own runtime field, which keeps both models clean.
No. Gateway routes are declared in the same stack.json and target the function by name. The route, its privacy, its API keys, and its domains are lines in the manifest a reviewer already reads.
Zero. Billing is execution at 0.01 credits per GiB-second; a declared but uncalled function contributes nothing but its name to the project.
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.