Pricing
Pay for compute (vCPU-hr), memory (GB-hr) and egress — metered per second, billed per hour. Identity, secrets, observability, CI/CD, admission and the audit chain are part of the platform, not separate line items.
Indicative — placeholder pricing for this scaffold. Real prices TBD.
Plans
Ship a real app on the sovereign platform at no cost.
Pay only for what runs. Metered per second, billed per hour.
Collaboration, SSO and higher quotas on top of usage pricing.
Sovereignty controls, dedicated regions and committed-use pricing.
Meters
Metering is done by SS-60 and billed by SS-10 — the same dogfooded self-serve path that runs the rest of the platform.
| Meter | Unit | Price | Notes |
|---|---|---|---|
| Compute | vCPU-hr | $0.024 | Metered per second while a replica runs; scale-to-zero apps cost nothing idle. |
| Memory | GB-hr | $0.008 | Billed alongside compute against the running replica set. |
| Egress | GB | $0.09 | After the free monthly allotment; intra-mesh traffic is not egress. |
| Database addon | SS-02 claim | at cost | Distributed SQL, cache, object or search — a DBaaS claim, priced at platform cost. |
| Build runner | self-hosted | $0 | Bring your own linux runners (ADR-0070); in-cluster build fallback included. |
Pricing FAQ
Per second against the applied replica set, billed per hour. Autoscale-to-zero apps accrue no compute while idle. SS-60 does the metering; SS-10 does the billing — the same dogfooded path that runs the platform.
Traffic leaving the platform boundary, after your free monthly allotment. Service-to-service calls over the mesh are not egress.
PR previews accrue usage while they exist, but their TTL lease and the sweeper reclaim them automatically, so an abandoned review app can't quietly run up a bill.
Identity, secrets, observability, CI/CD, admission and the audit chain are part of the platform — not separate line items. Database addons are priced at cost as SS-02 claims.
No. Every number here is an illustrative placeholder for this scaffold; committed prices are TBD.