Billing and plans
Organization plans, usage limits, Stripe checkout, and metered overage.
Billing is scoped to your organization. Workspace owners and admins manage plans under Settings → Billing in the web app.
Plans
| Plan | Monthly (USD) | Cases / month | Workflows | API requests / month |
|---|---|---|---|---|
| Free | $0 | 100 | 3 | 5,000 |
| Starter | $29 | 1,000 | 20 | 50,000 |
| Professional | $99 | 10,000 | 100 | 500,000 |
| Enterprise | Custom | Unlimited | Unlimited | Unlimited |
Landing pricing labels (Team, Business) map to API plan IDs (starter, professional). Enterprise is sales-assisted.
Operational limits also apply to raw events ingested, scanner runs, reports generated, evidence storage, and anchor proofs retained. When a limit is exceeded the API returns 402 Payment Required with an upgrade hint.
Usage metrics
The billing usage API (GET /billing/usage) returns per-metric counts for the current calendar month:
cases.created— operational cases createdworkflows.created,workspaces.active,processes.activeraw_events.ingested,scanner_runs.created,reports.generatedevidence.storage_bytes,api.requests,ai.requests, and related assistive metrics
Usage alerts notify organization admins at 50%, 75%, 90%, and 100% of plan limits.
Stripe checkout
When Stripe is configured (STRIPE_SECRET_KEY, webhook secret, and price IDs), Upgrade on the billing page opens a Stripe Checkout session. Manage Subscription opens the Stripe Customer Portal for paid plans.
Without Stripe credentials the API returns informational messages instead of redirect URLs — useful for local development and self-hosted evaluators.
MCP and CLI
The MCP server and CLI do not expose billing or Stripe tools. Plan enforcement happens on the API; agents inherit the organization's limits on platform routes.
Self-hosted operators
Production Stripe meter names and dashboard setup: Stripe billing guide in the monorepo.