Start here
Plans, quotas and limits
The numbers a reader needs before an evaluation, in one place. Pricing itself lives on the pricing page and is the source for everything in the first table.
Review quotas
| Plan | Repositories | Reviews |
|---|---|---|
| Starter | 1 | 50 / month |
| Individual | 2 | 300 / repo / month |
| Team | 10 | 1,000 / repo / month |
| Enterprise | negotiated | negotiated |
A review is one pull request evaluated once. Pushing five more commits to the same pull request does not spend five more: the comment is upserted, and the quota counts pull requests reviewed, not webhooks received.
Which plan has what
| Capability | Plan |
|---|---|
| The deterministic gate — conventions, built-in rules, findings | Every plan. No API key needed on any of them. |
| Per-organisation SSO | Team and above |
| Self-hosted install | Enterprise |
The first row is the one worth reading twice. The gate is the product, and it does not require an API key on any plan — including the free one. A language model is only involved in prose and fixes.
Rate limits
| Limit | Value |
|---|---|
| Personal access token requests | 120 per minute, per token |
| Webhook to comment | budgeted at p95 under 60 seconds |
| Scan | budgeted at under 2 minutes per 500 resources |
Personal access tokens are for scripts: they are read-only and rate-limited per token. Interactive sessions are not subject to that limit.
The two budgets are not SLAs. They are performance tests in the build — if a change makes reviews slower than that, the build fails. We publish them because they tell you what shape the system is, not because we are promising them contractually.
What is not metered
Conventions derived, evidence stored, findings recorded, receipts written, and rules in the catalog. None of these are counted or charged. The quota is on reviews.