Simple, Transparent Pricing
Monthly plans with credits included. Add more anytime with credit packs. One meter for everything that runs on the Software Lifecycle Cloud.
Pay for what runs. Commit to a floor.
Every plan is a monthly credit floor, shared across compute, storage, network, search, training, inference, and agent runs. Free includes a one-time starter balance.
- Deploy a first stack
- Up to 10 environments
- Standard rate limits
- Best-effort support
- Extended rate limits
- Up to 25 environments
- Partner seats, agent runs and workflows
- Shared support channel
- Extended rate limits
- Up to 200 environments
- The whole product team and stakeholder seats
- Priority support, monthly architecture call
- Reserved capacity and SLA
- Up to 1,000 environments
- Dedicated zone option
- Compliance features
Enterprise
Custom credit volumes above Platform, dedicated concurrency, contractual SLAs, and on-premise User Nodes as they ship. For large-scale and regulated workloads.
All prices in EUR. Unused subscription credits roll over for one month. Upgrades apply immediately; downgrades and cancellations take effect at the end of the billing period.
Adjust monthly workload dimensions to estimate credit consumption across compute, storage, egress, and catalog inference.
Recommended tier: Builder (€200/mo · 20,000 credits)
Need More Credits?
Top up anytime on Builder and above. Purchased credits are added to your org pool alongside subscription credits and allocated to environments as needed.
One Credit Balance, All Services
Credits are the single unit across all Kernstack services. No per-service billing, no surprises.
Monthly Allocation
Your subscription credits are allocated at the start of each billing month and shared across all services — Functions, Workers, Tables, Buckets, Inference, Training, and Search.
One-Month Rollover
Unused subscription credits roll over for one billing period. This applies to your monthly allocation only — credit pack top-ups are valid for 6 months from purchase and are not subject to the rollover cap.
Automatic Deduction
Credits deduct automatically from each environment's balance as you use the platform. Usage maps to compute, storage, and network — see the Price Reference below for rates and how each dimension is measured.
Graceful Exhaustion
If your balance reaches zero, service continues for a tier-based grace period so you can upgrade, top up, or wait for the next billing cycle. After grace expires without credits, the environment is suspended. Your data is never deleted.
Price Reference
We map billable work across the stack to the same three primitives — compute, storage, and network — so usage is expressed in a single internal model that mirrors real resources instead of a separate fee per product surface. See full KERNSTACK documentation for resource quotas.
| Dimension | Rate (credits) |
|---|---|
| Compute | 0.01 / GB-second |
| Storage (Tables, Buckets, Search index storage, etc.) | 0.04 / GB-hour |
| Network egress | 9.00 / GiB |
For duration-metered usage, your bill is compute + storage + network at the rates above, summed and rounded up to a whole credit. Compute uses (RAM in mebibytes ÷ 1024) × wall-clock seconds — GiB-seconds — × the compute rate; the table label “GB-second” is shorthand. Network is billed per GiB of API payload and response traffic (bytes ÷ 1024³) × the network rate; Functions, Workers, and Inference also bill outbound egress from guest code.
| Model | Unit | Batch | Credits |
|---|---|---|---|
text-embed-v1 | Tokens | 1,000 | 3 |
sentiment-multilingual-v1 | Tokens | 1,000 | 2 |
face-detect-v1 | Images | 1 | 3 |
label-detect-v1 | Images | 1 | 3 |
text-detect-v1 | Images | 1 | 3 |
moderation-v1 | Images | 1 | 3 |
image-quality-v1 | Images | 1 | 3 |
Each catalog model charges in steps: count prompt_tokens in chunks of 1,000, or one step per images. Each step uses fixed compute and egress assumptions at the rates above (rounded up). Total = steps × the per-step credits in the table (e.g. 2,500 sentiment tokens → 3 steps × 2 = 6 credits).
Custom inference (non-catalog invoke) uses wall-clock time, endpoint memory, and response size as egress — same compute + egress formula as other metered APIs.
Credit Use Scenarios
Rounded monthly examples mixing compute, storage, egress, search, and some catalog model usage. Real usage varies. Explore service-level breakdowns below.
Default mobile app backend
Typical REST + auth, profiles and feeds, light background jobs and push hooks.
- Compute (~113k GiB-s APIs, workers, scheduled tasks)~1,130
- Storage (~10 GB average month)~292
- Egress (~15 GiB JSON and presigned media to clients)~135
- Search (read-lean index and queries)~293
Approx. total~1.9k cr
Mid-tier B2B SaaS
Predictable API and worker load, shared tables and search, with selective catalog models for text and vision.
- Compute (~480k GiB-s APIs, queues, cron)~4,800
- Storage (~38 GB average month)~1,110
- Egress (~48 GiB to browsers and partners)~430
- Search (reindex churn + query compute)~1,250
- Model API (mixed text + vision, unit usage from catalog)~472
Approx. total~8.1k cr
Popular mobile/web backend
Higher RPS, heavier search and recommendations, bursts of generative media — often a subscription plus top-up packs.
- Compute (~1.35M GiB-s edge + core services)~13,500
- Storage (~195 GB average month)~5,700
- Egress (~400 GiB CDN and client pulls)~3,600
- Search (large corpus, frequent queries)~3,100
- Model API (higher volume text + vision)~2,750
Approx. total~28.7k cr
Pricing FAQ
Every plan includes a monthly pool of credits shared across Functions, Workers, Tables, Buckets, Search, Inference, Training, Workflows, and Agent Sandboxes. Usage is metered against three base primitives — compute (0.01 credits/GiB-second), storage (0.04 credits/GB-hour), and network egress (9.00 credits/GiB).
Yes. Unused monthly subscription credits roll over for one billing period. On-demand credit pack top-ups remain valid for 6 months from purchase and are consumed oldest-expiry first.
Service continues during a tier-based grace period so your team can top up, reallocate credits, or upgrade. After the grace period expires without credits, the environment is suspended safely and your data is never deleted.
Preview Available Soon
KERNSTACK is currently in closed preview. Talk to us to estimate your stack's credit footprint.