Why we bill code review by pull request size, not per seat
Per-seat pricing charges a ten-person team the same whether they open two pull requests a month or two hundred. Here is why Pullora meters by the size of the diff instead, and what that costs us.
Almost every AI code review tool charges per developer per month. It is a familiar model and it is easy to forecast. It is also, for this particular product, close to arbitrary.
A one-line typo fix and a 4,000-line refactor cost wildly different amounts to review. The typo is a few thousand tokens; the refactor is hundreds of thousands, across multiple passes, with context assembled from files the diff touches. Charging the same for both means one of them subsidises the other.
What a unit is
A review unit is a fixed budget of AI spend. Quick reviews start at 0.5 units, Standard at 1 and Deep at 2, rising with the size of the diff up to a hard ceiling per mode — 10, 20 and 40 units respectively. Most pull requests cost the minimum.
That last sentence is the whole argument. If your team ships small, focused pull requests, a plan with 150 units covers far more than 150 reviews. If your team ships 3,000-line branches, it covers fewer, and it should — those reviews genuinely cost more to produce.
The part that is worse for us
Metered pricing is harder to sell than a flat number. It requires explanation, it makes forecasting less certain, and a customer can have an expensive month. Greptile moved to per-review pricing and took real community criticism for it.
We publish the ceilings on the pricing page for that reason. A model where a single pull request can consume a quarter of a monthly allowance is not something to discover after subscribing. You see an estimate before running a review, based on what comparable reviews in that repository actually cost, and the exact figure afterwards.
Pooled, not per-seat
Units belong to the workspace, not the engineer. A team of twenty on the Team plan pays the same as a team of five. The people who benefit most are teams where a few engineers open most of the pull requests — which is most teams.
The honest trade: if your organisation has many engineers each opening a couple of small PRs a month, per-seat pricing from a competitor may work out cheaper. We would rather say that than have you discover it in month three.
See a review before you install anything
Paste any public GitHub pull request URL and read the full review — no app installed, no repository access, nothing posted to the PR.
Review a public PR →