Pricing
Free up to 250 vCPU. Priced per vCPU after that.
You pay for one number: the vCPU of the nodes SRE Orbit monitors, summed over every cluster and averaged over 30 days. Users, clusters, series, log lines and spans cost nothing extra.
Free
For a team up to 250 vCPU, on as many clusters as it runs.
Always free
No key, no card, no end date.
- Up to 250 vCPU across every cluster
- Unlimited clusters and users
- Metrics, logs, traces, APM, dashboards and alerts
- FinOps, Orbit SQL and the S3 archive
- MySQL monitoring: DB load by wait, calls, latency and errors, plus the SQL editor on your databases
- SSO with Google or any OIDC provider, and custom roles
- Documentation
Enterprise
Self-hostedFor larger estates you run in your own clusters, air-gapped ones included.
Priced per vCPU
Send us your vCPU count and a person replies with a quote within one business day.
Everything in Free, plus:
- As many vCPU as your key covers
- Nocturne AI: root cause with the evidence attached
- MySQL statement analysis: each top statement's SQL text, the sessions running now and EXPLAIN plans
- Rehydrate archived data from S3 on demand
- An offline key: no call home, no internet needed
- A named engineer and response times in the contract
Enterprise Cloud
For teams that want SRE Orbit without running it.
Priced per vCPU
Send us your vCPU count and a person replies with a quote within one business day.
Everything in Enterprise, plus:
- We install, upgrade and back up SRE Orbit for you
- A dedicated environment on your own domain
- Sign in through your identity provider
- Retention sized in the contract, storage scaled by us
What we count
Each node counts its CPU capacity, the status.capacity.cpu figure kubectl shows. orbit-api samples every cluster it monitors every five minutes, averages each day, and takes the average of the last 30 days. A burst of autoscaled nodes for one afternoon barely moves it.
Example: three clusters with 20 nodes of 4 vCPU each come to 240 vCPU. That fits in Free.
Count yours with kubectl before you install:
kubectl get nodes -o jsonpath='{range .items[*]}{.status.capacity.cpu}{"\n"}{end}' \ | awk '{s+=$1} END {print s " vCPU"}'After you install, Admin > License shows the same count per cluster, the 30-day average and the daily history.
Compare the plans
| Feature | Free | Enterprise | Enterprise Cloud |
|---|---|---|---|
| vCPU covered | 250 | Your key's limit | Your key's limit |
| Clusters | Unlimited | Unlimited | Unlimited |
| Users | Unlimited | Unlimited | Unlimited |
| Data retention | As long as your storage keeps it | As long as your storage keeps it | Set in your contract |
| Metrics, logs, traces, APM, dashboards, alerts | Included | Included | Included |
| FinOps and cost allocation | Included | Included | Included |
| Orbit SQL and the SQL editor on your databases | Included | Included | Included |
| MySQL monitoring: DB load, waits, calls, latency, errors | Included | Included | Included |
| SSO and custom roles | Included | Included | Included |
| S3 archive | Included | Included | Included |
| Rehydrate from the archive | Not included | Included | Included |
| Nocturne AI | Not included | Included | Included |
| MySQL statement texts, live sessions and EXPLAIN | Not included | Included | Included |
| Support | Documentation | Named engineer, contracted response times | Named engineer, contracted response times |
| Runs in | Your clusters | Your clusters | Our cloud, run by us |
What happens past a limit
SRE Orbit keeps collecting and keeps your data in every case below. Nobody gets signed out.
- The first 30 days
- A new install, and an existing one upgrading to this version, runs Enterprise as a trial with no vCPU cap. Admin > License shows the end date.
- Free, above 250 vCPU
- Everything on Free keeps working. Every Deck user sees a notice with the count until you apply a key or the 30-day average drops back under 250.
- Above your key's vCPU
- Nothing in the product changes. Admin > License shows the overage and we settle it at renewal.
- Your key expires
- Your plan keeps running for 30 more days with a notice. After that the install runs as Free: Nocturne AI, the MySQL statement views and new rehydrations turn off. They come back the moment a renewed key goes in.
Get a key and apply it
- 1Ask for a key through the contact form with your company name and vCPU count. We sign it offline and send it back. It carries your company name, plan, vCPU limit and expiry date.
- 2In the Deck, open Admin > License, paste the key and press Apply. orbit-api checks the Ed25519 signature on the spot, with no internet access.
- 3Or set it in Helm: license.key inline, or license.existingSecret pointing at a Secret you manage.
orbit-api refuses a key with a changed character, one we did not sign, one past its expiry date, and one for a plan it does not know.
Each key applied, removed or refused lands in the audit trail with its plan, limit and expiry. The trail never stores the key itself.
# license.existingSecret: a Secret you managekubectl -n sreorbit create secret generic sreorbit-license \ --from-literal=license-key='SO1....'helm upgrade sreorbit deploy/helm/sreorbit --reuse-values \ --set license.existingSecret=sreorbit-license # or inline: --set-string license.key='SO1....'Questions about pricing
Why vCPU and not hosts, series or gigabytes?
vCPU follows the size of what you run, and you can check it with kubectl. Series, log lines and spans grow with how much you instrument, and we want you to instrument everything.
Does checking the key need internet access?
No. orbit-api verifies the signature with a public key built into it, so air-gapped clusters work the same way.
What does Free leave out?
Three things: Nocturne AI, the MySQL statement views (each statement's SQL text, the sessions running now and EXPLAIN plans) and rehydration from the S3 archive. Free keeps your database connections and the SQL editor, keeps collecting MySQL monitoring data and shows DB load, calls, latency and errors, so a key opens the statement views on data you already have. SSO, custom roles, the archive and all telemetry stay on Free.
We already run SRE Orbit. Do we lose anything when we upgrade?
Not for 30 days: the upgrade starts the Enterprise trial. Apply a key before the date Admin > License shows and nothing changes at all.
See SRE Orbit on your own clusters
Tell us what you run. A person replies within one business day to book a demo of the console, and because SRE Orbit is early, the engineers who build it install it with you.
- Installed with you, next to the tools you run today.
- A copy of your remote-write, so you compare disk, memory and query latency on your own data.
- Direct work with the engineers who build it.