Use this page to build an internal business case for Stage0. The numbers below are a planning framework, not public proof claims or guaranteed savings.
Stage0 is easiest to justify when you tie it to concrete operational events: a blocked destructive action, a deferred production deploy, a stopped agent loop, or a review workflow that now has consistent audit fields.
Count how many deployment, payout, delete, or external-notification requests should be stopped or deferred each month.
Measure how often agents exceed expected iteration count, elapsed runtime, or cost budget before a human notices.
Track time spent manually checking tool calls, approvals, or environment scope that can be surfaced earlier by Stage0.
Estimate the value of having request IDs, policy versions, and structured denial reasons attached to every high-risk decision.
| Tier | Price | Checks / month | API keys |
|---|---|---|---|
| Free | $0/month | 1,000 | 1 |
| Starter | $9/month | 5,000 | 3 |
| Pro | $19/month | 20,000 | 10 |
Start with a monthly estimate for the items below, then compare the total operational exposure against the subscription tier you expect to run.
If you need buyer-facing proof, publish real blocked-run examples with request context and decision output instead of headline ROI multipliers.
Pair this worksheet with one real blocked run, one deferred run, and the exact fields your operators used to approve or reject it.
Read the docs