Plan allowances

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.

Prices are on the Pricing page.

	Free	Pro	Growth	Enterprise
Allowed checks a month	100,000	1 million	25 million	Agreed
Active subjects a month	1,000	10,000	100,000	Agreed
Test checks a month (not billed)	10,000	100,000	2.5 million	Agreed
Usage history	7 days	90 days	13 months	Agreed
Members	3	10	25	Agreed

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.
• Test checks. Checks made with a test key have their own allowance, 10% of the plan’s allowed checks, and aren’t billed. They never count toward your allowed checks or active subjects. See Test and live.

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

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 on allowed checks and active subjects. Past that, checks answer 402 plan_limit_reached instead of a decision. The SDK treats that the same as Limitry being unreachable, so each limit’s fail mode applies. With open, the default, your product keeps working, but its limits aren’t enforced until you upgrade or the next period starts. With closed, it refuses.
• Test checks have no grace: past their allowance, test checks answer 402 plan_limit_reached.
• Upgrading lifts it within a minute. Otherwise it resets on your billing date: the day your subscription started, or the day you created the workspace on Free. Annual plans reset every month, on that day.

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.