Glossary · Pricing

Credit

A credit is KERNSTACK’s single unit of metering: compute costs 0.01 credits per GiB-second, storage 0.04 credits per GB-hour, egress 9.00 credits per GiB, and catalogue inference is priced per token or image in credits. One balance pays for everything a project does.

Functions (WASM)NoSQL Tables
Talk to us Read Technical Documentation → Software Lifecycle Cloud →

Definition: Credit

A credit is KERNSTACK’s single unit of metering: compute costs 0.01 credits per GiB-second, storage 0.04 credits per GB-hour, egress 9.00 credits per GiB, and catalogue inference is priced per token or image in credits. One balance pays for everything a project does.

One meter instead of a meter per service

Hyperscaler bills price each service in its own units, so forecasting means translating between request counts, GB-months, read units, and provisioned throughput. A credit collapses the units: a function’s second of compute, a gigabyte-month of table storage, and an embedded document all spend the same currency, so a project’s whole appetite fits in one number that plans bundle (Builder includes 20,000 credits for €200 a month; Team 100,000 for €900; Platform 500,000 for €4,000).

What a credit makes visible

Because environments share the unit, costs compare honestly: a preview environment’s storage, an agent demo’s compute, and production’s inference all read in credits. Idle compute spends zero — a function that does not run and a worker scaled to zero burn nothing — so the balance mostly accrues storage at 0.04 credits per GB-hour while the team sleeps.

FAQ

Frequently asked questions

Plans set the practical scale: Builder is €200 a month including 20,000 credits (about a cent per credit), Team €900 for 100,000, Platform €4,000 for 500,000. A free tier starts with 200 credits.

Storage only: 0.04 credits per GB-hour across tables, buckets, and indexes. Functions that never run and workers scaled to zero instances spend no compute credits at all.

Yes. Agent demo environments and their compute spend from the same balance as everything else in the project, so the cost of agent work is one visible line rather than a separate surprise.

Connected in the Project Graph

Related capabilities, architectures, and comparisons

Category PillarThe Software Lifecycle CloudHow KERNSTACK unifies infrastructure, code, intelligence, and collaboration.Platform · ComputeFunctionsGo WebAssembly HTTP handlersPlatform · DataTablesServerless key-value and document tablesGlossary · DeliveryPlan diffA plan diff is the preview kernstack plan produces before any deploy: the creates, updates, and deletes the new stack.json would cause — with deletes listed under “Will delete” and refused until a person passes --confirm-destructive. It is also available as kernstack plan --json.Glossary · ArchitectureProject graphThe project graph is the whole system a KERNSTACK project declares in stack.json — gateway routes, functions, workers, tables, buckets, search indexes, workflows, and secrets — instantiated per environment target and changed only through reviewed plans.Glossary · PricingScale to zeroScale to zero means idle compute stops billing: functions charge 0.01 credits per GiB-second only while executing, and workers with min_instances: 0 stop after their idle_timeout_ms. An idle project spends on storage (0.04 credits per GB-hour), not on standing replicas.Glossary · SearchVector indexA vector index is a KERNSTACK search index with index_type "vector", declared over the tables and buckets that hold the source records. Retrieval runs inside the project, fed by embeddings from catalogue models such as text-embed-v1 (3 credits per 1,000 tokens) or a custom inference endpoint.

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 →