Plans and limits
Every plan has every feature: pools, credits, budgets, reservations, rolling and concurrent limits, webhooks, the SDK and the MCP server. Plans differ in how much you can use.
| Free | Pro | Growth | Enterprise | |
|---|---|---|---|---|
| Price | $0 | $39 / month | $299 / month | Talk to us |
| Allowed checks / month | 100,000 | 1 million | 25 million | Custom |
| Active subjects / month | 1,000 | 10,000 | 100,000 | Custom |
| Usage history | 7 days | 90 days | 13 months | Custom |
| Members | 3 | 10 | 25 | Custom |
What counts
Section titled “What counts”- Allowed checks. Denied checks never count, so a burst of abuse against your limits doesn’t use up your plan. A check that draws from a user and a team pool counts once.
- Active subjects: the different users, keys, agents or teams with at least one allowed check this month, each counted once.
You can see your usage in Settings → Billing, or with
GET /v1/workspace/usage. It’s about a minute behind live checks.
When you reach your plan’s limit
Section titled “When you reach your plan’s limit”Your product keeps working.
- At 80% and 100% of a monthly allowance, your workspace’s owners get an email and a notification, and the app shows a notice.
- You get 10% grace. Past that, checks answer
402 plan_limit_reachedinstead of a decision. The SDK treats that the same as Limitry being unreachable, so each limit’s fail mode applies. Withopen, the default, your product keeps working without metering. Withclosed, it refuses. - Upgrading lifts it within a minute. Otherwise it resets on the 1st of the month (UTC).
If you call the API directly, handle a 402 the way you’d handle a
timeout: apply your fail mode. The SDK’s guard and hold do this for
you.