Public answers about plans, quotas, billing posture, and what is safe to assume before you put Stage0 in front of production actions.
| Plan | Price | Checks / Month | Checks / Day | API Keys | Best Fit | Support |
|---|---|---|---|---|---|---|
| Free | $0/month | 1,000 | 100 | 1 | Local prototypes | Docs |
| Starter | $9/month | 5,000 | 500 | 3 | Production pilots | |
| Pro | $19/month | 20,000 | 2,000 | 10 | Governed workflows | Priority email |
Yes. The public free tier includes 1,000 checks per month and is meant for local validation, early prototypes, and policy testing.
Choose based on operational risk and volume. Starter is for early production pilots, and Pro is for governed workflows with stronger evidence needs. If you need higher limits or custom terms, contact us.
Use the pricing shown on the site and in the shared tier configuration as the current public source of truth. If you need custom terms, contact us before purchase.
A call to the Stage0 decision endpoint counts as a check. The quota exists to bound runtime authorization usage, not to meter downstream execution.
Yes. Each plan has a per-minute limit in addition to the monthly quota: Free (20/min), Starter (30/min), Pro (60/min). Exceeding this limit returns HTTP 429 with a retry hint.
When the monthly quota is exhausted, the API returns HTTP 402. For per-minute rate limits, it returns HTTP 429 with a retry_after_seconds hint. Your runtime should be prepared to handle both cases and fail closed for missing authorization.
Yes. The higher tiers expose larger public quotas, and custom arrangements can be discussed when your runtime volume or operational constraints exceed those defaults.
No. This page does not claim a certification status. Public production behavior should be verified through the docs and contract fields.
Verify fail-closed behavior, request tracing fields such as `request_id` and `policy_version`, approval context requirements, and the fact that final enforcement remains in your own server-side runtime.
Start with `/docs#production` and `/docs#contract`. Those pages describe the public runtime contract more reliably than marketing copy or static FAQ language.
If you need annual billing, invoicing, or a procurement review, contact us before rollout to discuss custom terms.
Public plans differ in support depth. Use the plan table as the lightweight public guide, and confirm any stricter response expectations before treating them as contractual.
Contact support with your runtime shape, expected volume, and approval model. That is the fastest way to get a buyer-facing answer without relying on assumptions.
Share your runtime, risk profile, and expected check volume. We will point you to the right public docs or discuss a custom plan if the standard tiers are not enough.