Billing and reviews
Start free, then size it to what you ship. Every plan is the full product; they differ only in reviews a month. Never a charge for going over.
Unlimited repositories, unlimited people, every feature, on every plan. The only thing you buy is how many pull requests get reviewed in a month, because that is the only thing that costs us anything. Nobody has to count who is on the team, and no invoice is ever a surprise: when the balance runs out, reviews pause.
What counts as a review
One pull request, one review. The first completed review of a pull request spends one review, and that review covers two AI reads: the first, and one more after you push new UI lines. Every push gets the deterministic checks, and a push never spends a review, however many times, however long the pull request stays open.
A third read is one review. Past the two, the AI reads the pull request again only when a member asks, with @crocotaste review or Re-run in the dashboard, and that read spends one review. An ask with nothing new to read (the same UI lines against the same design system) is free and says so on the pull request, and so is one the model could not answer. The summary says when the AI review did not run, and a finding already posted keeps counting until its line changes or you dismiss it.
These cost nothing at all:
- pull requests that changed no UI file (
Skipped · no UI files changed), - pull requests too large to review (
Skipped · too large to review; the check names the numbers), - pull requests in a repository where nothing could be checked against yet, no DESIGN.md, no tokens, no components and no UI rules in an agent guide (
Skipped · no design system found; a repository whose only system is agent-guide UI rules is reviewed and uses a review), - pull requests from outside contributors, people who cannot push to the repository (
Skipped · ask a member for @crocotaste review; a member's command reviews it at once, and once that review has spent its credit it counts like any other, and members and bots are never held), - draft pull requests, until they are marked ready for review,
- any review that could not complete on our side,
- any review that stopped because the balance was empty.
A review that finds nothing costs the same as one that finds three things: a green check is a result, and charging only for bad news would be a reason to find bad news.
Plans
| Plan | Price | Reviews a month | Sized for |
|---|---|---|---|
| Starter | $19 | 25 | a solo dev shipping UI a few times a week |
| Team | $79 | 120 | 5–15 engineers |
| Business | $249 | 400 | 15–50 engineers, heavy agent volume |
| Pack | $25 one-time | +25, valid 12 months | a top-up on any plan, a dollar a review |
Three reviews are free on install, no card. The last one says so on the pull request, so nobody is surprised by the next check.
Balance belongs to the GitHub account, an organization or a user, so it is pooled across every repository and every person its installation covers, and it survives uninstalling and reinstalling. Two organizations means two accounts, two balances and two plans.
Credits are spent trial first, then the plan's, then packs: the free one first and the one you paid for once last.
How the month works
Plan reviews reset to the full allowance at the start of each billing cycle and do not roll over. Pack reviews are valid for 12 months from purchase and are only touched once the plan's are gone.
Changing plan mid-cycle keeps what you already used: upgrade from Starter to Team on the day you have spent 20 of 25, and you get 100 of 120, not a fresh 120. Cancelling leaves access running to the end of the period you paid for; at that point the plan allowance goes to zero and any pack reviews you own stay yours.
When a balance runs out
Reviews pause. The pull request gets a neutral check with the link to billing on it:
Review budget used · top up or upgrade
Nothing goes red, no model call is made, and nothing is charged. Top up or upgrade, then comment @crocotaste review and the pull request is reviewed.
You get warning before that. From 80% of a plan's monthly allowance used, the summary comment on every pull request and the dashboard both say how much of the allowance is used.
We never charge you for going over, and we never will. A bill that grows because your team shipped more UI is a bill nobody can approve in advance.
Billing
Checkout and the customer portal are hosted by Polar, the merchant of record, which means Polar handles VAT and sales tax and appears on your invoice.
The dashboard shows the balance bar, "Buy 25 reviews" and "Manage plan". Invoices, plan changes, payment methods and cancellation all live in the Polar portal, reachable from the dashboard by anyone who administers every repository the App is installed on.
The plan belongs to the GitHub account, not to the person who paid. Receipts and Polar's own portal emails go to the email used at the first checkout; if that person leaves the team, an admin changes the email and the payment method in the portal and nothing else moves.
Uninstalling the App cancels the plan at the end of the period you paid for, so nothing is charged for a product you removed. Reinstalling within 30 days brings the balance and the history back under the new installation. If the period you paid for is still running, the plan comes back with them and the cancellation is withdrawn; a plan you cancelled yourself in the portal stays cancelled. Suspending the App on GitHub pauses reviews but not the plan; uninstall if you want both stopped.
A refunded pack removes its 25 reviews from the balance, or whatever part of them was still unspent.
Working out what you need
Count the pull requests in a month that touch a UI file, not the total. For most teams that is a fraction of the whole: backend, config, test and dependency pull requests are skipped and free.
Then start on the three free reviews and read the ledger. The dashboard shows every review per repository, so after a week you are sizing against your own number rather than an estimate. Pricing has the per-review arithmetic side by side.