Starter
Try AI PR review.
- 2 reviewers
- Code Review
- Security Review
- 3 seats included
- 15,000 credits to start, then 5,000/mo
- About 70 reviews to start, then about 25 a month
- Unlimited repos
Greptile Pro has no seat fee: you buy credits at $1 each, shared by the whole organization, for any number of developers.[1] A credit is not always one review: a Base review costs 1 credit, a Plus review 3 and an Apex review 10, and in Auto mode Greptile picks the tier for each pull request.[2]
HighKnown issue in the Code Review benchmark · caught by DeepSeek V4.1 FlashSee the graded case
On our 50-PR code review benchmark Greptile found 81 of 158 known issues for an F1 of 51.1%, ahead of the 49.2% of DeepSeek V4.1 Flash, the model IonWarp's Code Review runs.[3] Greptile alternatives ranks the others, and Greptile vs CodeRabbit compares the two. A five-person team pays IonWarp $49/mo on Pro.
Free for one active developer, with unlimited repositories and 50 credits a month.[1] It does not include CLI reviews.[4]
No seat fee, after a 14-day trial: credits cost $1 each and are shared across the organization.[1] They are prepaid; when they run out, new reviews pause until you buy more or automatic recharge does.[4]
Self-hosting, SSO/SAML and a custom DPA, priced by sales.[1]
Only completed reviews, by tier; a TREX run, which tests the UI, adds 3. CLI reviews cost the same as pull request reviews, and authors you exclude, such as common bots, spend nothing.[4]
Qualified non-commercial open-source projects are free, and annual or multi-year contracts get custom pricing.[1]
At 20 reviews per developer a month, every one at the same tier; in Auto mode Greptile mixes tiers, so a real month falls between the columns.[2] IonWarp's column is its cheaper paid plan for that many developers.
| Criterion | IonWarp | Greptile Pro, Base reviews | Greptile Pro, Plus reviews | Greptile Pro, Apex reviews |
|---|---|---|---|---|
| 5 developers | $49/mo on Pro, 5 seats included | $100/mo[1] | $300/mo[1] | $1,000/mo[1] |
| 10 developers | $149/mo on Max, 10 seats included | $200/mo[1] | $600/mo[1] | $2,000/mo[1] |
| 25 developers | $584/mo on Max, 10 seats included, plus 15 at $29 | $500/mo[1] | $1,500/mo[1] | $5,000/mo[1] |
One workspace price with seats included. Credits pool across your team. Unlimited repos on every plan.
Try AI PR review.
Get AI PR review right from day 1.
Scale AI PR review.
Custom reviewers + credits · GitHub Enterprise · SSO/SAML + audit logs · Custom security review + SLA
Pro has no seat fee: credits cost $1 each and a Base review uses 1, so 5 developers running 100 Base reviews a month pay $100 (Greptile pricing page, Nov 2026). The same month costs 3 times as much at Plus and 10 times at Apex.
Starter is free for one active developer with 50 credits a month, and qualified non-commercial open-source projects are free. A team needs Pro, which starts with a 14-day trial.
The unit Greptile bills reviews in, $1 each on Pro and shared by the team (Greptile pricing page, Nov 2026). A Base review uses 1 credit, a Plus review 3 and an Apex review 10; in Auto mode Greptile picks the tier for each pull request, and you pay for the tier that ran.
On our benchmark it scored higher than IonWarp's Code Review on code review, an F1 of 51.1% to 49.2%, and led API performance review. It also fits teams on GitLab or Bitbucket, or that need self-hosting, which IonWarp does not offer.
CodeRabbit Essentials is $24 per developer a month billed annually; Greptile Pro has no seat fee and charges $1 a credit (CodeRabbit and Greptile pricing pages, Nov 2026). Below 24 Base reviews per developer a month Greptile costs less, and CodeRabbit limits reviews per developer an hour.
Starter is free for 3 seats with 15,000 credits on signup. Pro is $49/mo for the whole workspace with 5 seats included, and Max is $149/mo with 10.
isinstance check at line 254 tests against multiprocessing.Process which is the default context's ForkProcess class, not the SpawnProcess class created by multiprocessing.get_context('spawn'), causing the check to always be False on Linux and preventing process.kill() from being called on unhealthy workers · Code Review