Pricing

Start free, then size it to what you ship

3reviews

Free on install, with no card and no plan to pick yet. Point it at one repo and watch.

Install on GitHub

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 most daysAbout 1 UI PR a working day25 reviews · $0.76 each
  • TeamMost teams$79a monthFor 5–15 engineersAbout 6 UI PRs a working day120 reviews · $0.66 each
  • Business$249a monthFor 15–50 engineers, heavy agent volumeAbout 19 UI PRs a working day400 reviews · $0.62 each
  • Pack$25onceFor a busy month on any planValid 12 months from purchase25 reviews · $1.00 each

Public repositories: 50 free reviews a month

Every GitHub account gets 50 free reviews a month on its public repositories, through December 31, 2026. They are spent before your trial or your plan, and they come back on the 1st of each month.

They come from a shared monthly pool. If the pool runs out, or your 50 do, a public pull request uses your trial, plan or pack reviews, and with none left, public reviews pause until the 1st. Private repositories work as always: 3 free reviews, then a plan.

50reviews a month

Per GitHub account, on its public repositories

What counts as a review

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.

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.

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. 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.

One pull request, one dayBalance
  1. 10:02OpenedAI read 1−1 review
  2. 10:40Pushed 3 UI linesAI read 2free
  3. 11:15Pushed new UI lines againChecks only, no AI readfree
  4. 14:31@crocotaste review after new linesAI read 3−1 review
  5. 14:36@crocotaste review, nothing newChecks only, no AI readfree

A draft pull requestSkipped until it's ready for reviewfree

Questions, answered

The ones teams ask before they install

Everything else is in the docs, or one email away

Does Crocotaste write to my repository?

No, and it can't. The GitHub App reads your code and can write only pull request comments, approvals, checks and issues. DESIGN.md is written by you or your coding agent; Crocotaste only asks 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 asks your coding agent to write a DESIGN.md from that code, which sharpens the next review and your agents too. With nothing at all to check against, the review is skipped for free, and the check points you to DESIGN.md instead of passing a change against nothing.

Does Crocotaste work with a DESIGN.md from Stitch or the awesome-design-md gallery?

Yes. Any DESIGN.md in Google's format is read as it is: the tokens and components in its front matter, the rules under its sections, and the entries under Decisions. We read all 84 files in the awesome-design-md gallery: 71 parse in full, and the rest still give their rules.

Will it flood our PRs with comments?

No. One summary comment, edited in place on every push. Dismiss a finding and it stays gone on that PR. Fix one, and its comment names the commit that fixed it and collapses.

Which coding agents does it work with?

All of them. It reviews the pull request, so it doesn't matter what wrote the code. Every finding carries a prompt you can paste, and the check run emits JSON an agent loop can pick up on its own.

What counts as a UI change?

Any file that matches the UI glob: components, styles, design tokens, Tailwind config, stories. The full list is in the docs. A backend-only PR is skipped with a neutral check and costs nothing.

Is our code used for training?

No. Your diff goes to the model for that one review and isn't kept. Parsed references are reused for at most 30 minutes, held only in the worker's memory, never on disk. We keep the findings we posted (message, suggestion, fingerprint: the same text already on your pull request) and the counts we bill from. No file contents, no copy of your repo.

How does the trial work?

3 reviews free on install, no card. Point it at one repo and open a pull request: a green check if it's clean, a cited finding if it drifted.

Is it free for open source?

Public repositories get 50 free reviews a month per GitHub account through December 31, 2026, from a shared monthly pool. They are spent first; past them a public pull request uses your trial, plan or pack reviews, and with none left it pauses with a neutral check until the 1st.

Install on one repo, open a pull request

Your first review in about a minute, 3 free and no card

  1. 00:00 PR #1 opened by your agent
  2. 00:04 queued · UI files detected
  3. 00:19 read tokens.css, Button.tsx at base
  4. 00:41 checks done · AI read running
  5. 00:58 On-system · approved