Pricing
Start free, then size it to what you ship
Free on install
3 reviews
No card, no plan to pick yet. Point it at one repo and watch.
Every plan is the whole product
- Cited findings with the fix written
- A prompt for your agent on every finding
- The learning loop into DESIGN.md
- JSON on every check for agent loops
- As many repos and people as you like
- Pushes on a reviewed PR, free
Run out and reviews pause with a neutral check. Never a charge for going over.
- Starter$19a monthFor a solo dev shipping UI a few times a week25 reviews a month
- Teammost teams$79a monthFor 5–15 engineers120 reviews a month
- Business$249a monthFor 15–50 engineers, heavy agent volume400 reviews a month
- Pack$25onceFor a busy month on any plan25 reviews, valid 12 months
Which plan fits
Count pull requests that touch UI, not people. Twenty engineers who ship UI on Tuesdays use fewer reviews than three engineers and their agents, so headcount is the wrong thing to measure.
If you can't tell yet, start free. The dashboard counts your reviews over 30 days, so the first month sizes the plan for you, and plans change whenever you want.
- Starter25 reviews a monthAbout 1 UI pull requests every working day
- Team120 reviews a monthAbout 6 UI pull requests every working day
- Business400 reviews a monthAbout 19 UI pull requests every working day
What counts as a review
One pull request, one review, and that review covers two AI reads: the first, and one more after you push new UI lines. Pushes never spend a review. A third read, asked for with @crocotaste review or Re-run, is one review; an ask with nothing new to read is free. Skipped PRs (drafts, no UI files, too large to review, or a repository with no design system to check against) and neutral results (our failure, an empty balance) cost you nothing.
Plan reviews reset monthly and don't roll over; pack reviews are valid for 12 months from purchase. Design partners get custom terms, case by case.
- Starter$0.76per review
- Team$0.66per review
- Business$0.62per review
- Pack$1.00per review
Questions teams ask before installing
The short answers, with the permissions and the numbers in them
Does Crocotaste write to my repository?
No, and it can't. The GitHub App gets read-only access to your code, and write access only to pull request comments, checks and issues. DESIGN.md is written and edited by you or your own coding agent; all Crocotaste does is ask for it.
What if we don't have a design system?
You have more of one than you think. Reviews run on what the repo already holds (Tailwind config, token files, component exports) and the check says so. The onboarding issue hands your coding agent instructions to write a DESIGN.md from that same code, which makes the next review sharper and your agents better at the same time. If there is nothing at all to check against, the review is skipped, free, and the check points you at DESIGN.md rather than passing a change against nothing.
Will it flood our PRs with comments?
No. One summary comment, edited in place instead of a new one every push. At most 3 AI findings per pull request and at most 12 findings posted per push; the rest wait their turn. Dismiss a finding and it won't come back on that PR. Fix one and, once the review can see the line is gone, its comment says which commit fixed it and collapses.
Which coding agents does it work with?
All of them. It reviews the pull request, not the editor, so whatever wrote the code is beside the point. Every finding carries a prompt you can paste, and the check run emits JSON so an agent loop can pick the findings up on its own.
What counts as a review?
One pull request, one review, and that review covers two AI reads: the first, and one more after you push new UI lines. Pushes never spend a review. Asking for a third read with @crocotaste review or Re-run is one review, and an ask with nothing new to read is free. Drafts, backend-only PRs and anything we couldn't review cost you nothing. When a plan runs out, reviews pause with a neutral check until the next month or a top-up, and we never charge you for going over.
What counts as a UI change?
A file glob, and you can read the whole list in the docs: components, styles, design tokens, Tailwind config, stories. A backend-only PR is skipped with a neutral check and costs you nothing.
Is our code used for training?
No. Your diff goes to the model for that one review and is not kept; the parsed references sit in the worker's memory for up to 30 minutes, never in storage. What we keep is each finding we posted (message, suggestion and fingerprint, the same text already on your pull request) plus the counts we bill from. No file contents, no copy of your repository.
How does the trial work?
3 reviews free on install, no card. Point it at one repo and watch: a green check on a clean PR, one cited finding on a drifted one.