Plan tiers
Compare Starter, Team, Business, and Enterprise plans, and find the tier that matches your team's review volume.
Last updated
ADO Pilot has four tiers: Starter, Team, Business, and Enterprise. Each tier sets a monthly review credit (RC) allocation, a default behavior when you exceed it, and a per-RC overage rate. Pick a tier based on how many PRs your team reviews each month and how much variability you want to absorb.
The four plans
| Plan | Monthly price | Annual price (per month) | Included review credits (RCs) | Default overage policy | Overage rate per RC |
|---|---|---|---|---|---|
| Starter | $20 | $17 | 150 | Auto-overage | $0.22 |
| Team | $50 | $42 | 400 | Auto-overage | $0.20 |
| Business | $150 | $125 | 1,300 | Auto-overage | $0.18 |
| Enterprise | Custom | Custom | Custom | Negotiated | Negotiated |
Annual subscriptions discount the subscription fee; included RCs are unchanged.
The "Default overage policy" shown above applies to both monthly and annual billing. Annual plans bill overage monthly, via a metered add-on alongside the annual base subscription, rather than pooling overage into the annual charge.
All plans are billed in US dollars (USD) through Stripe. Annual subscriptions reduce the subscription fee but include the same number of RCs per month as the monthly plan.
Included RCs per month
Each plan ships with a fixed monthly RC allocation:
- Starter — 150 RCs/month, sized for a single developer or small team running a handful of small-to-medium PRs.
- Team — 400 RCs/month, sized for a multi-person team with steady PR throughput.
- Business — 1,300 RCs/month, sized for an engineering org with continuous integration of large changes.
- Enterprise — Custom RC allocation, negotiated per contract.
The "RCs per month" is a use-it-or-lose-it allocation: see Billing periods for how and when it resets.
Overage rates
If you exceed the included RCs in a billing period, your plan's default overage policy decides what happens:
- Starter, Team, and Business default to auto-overage on both monthly and annual billing. Reviews keep running once you pass your included RCs, and each extra RC is billed at the per-RC overage rate at the end of the period. By default there is no cap; set an overage cap if you want a known ceiling (a cap of zero behaves like hard-block).
- Enterprise policy is negotiated per contract and set explicitly by an admin — it is not defaulted to auto-overage.
You can change the policy and set a cap. See Overage behavior for details.
Annual billing
Annual plans charge the subscription fee once per year. The included RC count is per month, not per year — your included RCs reset each month rather than pooling into a single annual allocation. Annual plans support the same auto-overage billing as monthly plans: if you exceed your included RCs in a month, each extra RC is billed at your plan's per-RC overage rate at the end of that monthly period.
Choosing a tier
A useful first cut: for each PR, estimate its diff size and round up to the nearest 500 lines, with a minimum of 1 RC per PR — then sum across your monthly PR volume. Diff size divided by 500 alone only works as an estimate if your PRs are large; teams that open many small PRs (each under 500 lines) use closer to 1 RC per PR, since every review costs at least 1 RC regardless of size. If your estimated total sits comfortably below a plan's included RCs, that plan is your starting point. If it is close to the next tier's allocation, upgrade — the included RCs in the higher tier are usually cheaper than paying the lower tier's overage rate.