Plans
Prices below are the ones stated in the Terms of Service and in the app. Limits and retention are what GET /public/plans returns. Re-fetch that endpoint if you need the live numbers.
| Plan | Price | Agents | Events per month | Event retention |
|---|---|---|---|---|
| Developer | $0 | 2 | 10,000 | 7 days |
| Team | $99 per month | 10 | 250,000 | 30 days |
| Business | $499 per month | 50 | 2,000,000 | 365 days |
| Enterprise | Quoted | Not published as a fixed number | Not published as a fixed number | Not published as a fixed number |
Team and Business are billed monthly in advance, in US dollars, through Stripe. There is no annual plan and no overage charge. Prices exclude taxes. The terms say Stripe Tax is not enabled.
Enterprise is quoted separately. The public plans payload uses null for its agent, event, and retention fields, which means those limits are not published on the endpoint.
What the limits do
Section titled “What the limits do”Event quotas are soft. quotaExceeded can be true on a decision, and the decision is still made. The app warns as usage reaches the plan. It does not add an overage fee.
The agent limit is enforced. Creating agents past the plan’s agent count is refused. That is separate from the event quota.
Decision events are deleted automatically after your plan’s retention window (Developer 7 days, Team 30 days, Business 365 days). The deletion job runs regularly. Enterprise retention follows your contract; there is no automatic deletion unless agreed. When an event is deleted, its audit-log entry (the decision, risk score and related metadata) is kept for as long as the organization exists, because the audit log is append-only. Deleted data can remain in encrypted backups for up to 30 days. The table above is that window. The audit log is not deleted on it.
Changing plan
Section titled “Changing plan”GET /public/config includes billingEnabled and planChangeEnabled. Those flags describe the deployment. When these docs were written, billing was enabled and changing plan in the app was not. Read the endpoint rather than assuming a checkout button is available.
Sandbox events from TEST keys are kept out of usage.