Greptile
Greptile
Greptile is a Greptile pull-request reviewer on GitHub, GitLab, billed as hybrid, last verified August 16, 2026. The full-codebase reviewer: it spends credits to keep a graph of the repo, which is the point when bugs live in call sites the diff does not show.
Catalog record checked August 16, 2026; vendor pricing and policies can change.
| Specification | Greptile |
|---|---|
| Vendor | Greptile |
| Git hosts | GitHub, GitLab |
| Surface | Full-repo context PR review |
| Billing model | Hybrid |
| Hourly / throughput | Credits, not hourly |
| Trial | 14-day Pro trial. |
| Config / rules | Custom rules (Pro) |
| Inline comment cap | Not verified |
| Self-hosted option | Yes |
| CI hosts | Not a separate CI product |
| Autofix | Not verified |
| Merge gate | Not verified |
| Free for qualifying OSS | Yes |
How a review works. Indexes the repository so reviews can reason about files outside the diff. TREX is a heavier review that costs three credits.
Pricing (verified). Starter: free, 1 active developer, 50 credits/month. Pro: $30/seat/month, 50 credits included per seat, then $1 per extra credit. 1 credit = 1 standard review; 3 credits = 1 TREX review. A seat is any developer who received a Greptile review in that billing period. 14-day Pro trial. Free for qualified MIT/Apache non-commercial OSS. 50% off for pre-Series A startups under $2M trailing-12-month revenue.
Hourly / throughput. No published hourly cap. Starter: 50 credits/month for one active developer. Pro: 50 credits included per seat/month, then $1 per extra credit. One standard review uses 1 credit; one TREX review uses 3.
Trial. 14-day Pro trial.
Watch out. Credits run out: 50 standard reviews per seat, then $1 each, and TREX burns three credits. GitHub and GitLab only on the public pricing page. Confirm TREX vs standard before comparing catch-rate anecdotes from third-party blogs.
Compare Greptile
Common questions
Questions about Greptile
Answered from the verified figures on this page rather than general guidance.
What is Greptile?
The full-codebase reviewer: it spends credits to keep a graph of the repo, which is the point when bugs live in call sites the diff does not show. It reviews on GitHub, GitLab as full-repo context pr review.
How does Greptile price reviews?
Starter: free, 1 active developer, 50 credits/month. Pro: $30/seat/month, 50 credits included per seat, then $1 per extra credit. 1 credit = 1 standard review; 3 credits = 1 TREX review. A seat is any developer who received a Greptile review in that billing period. 14-day Pro trial. Free for qualified MIT/Apache non-commercial OSS. 50% off for pre-Series A startups under $2M trailing-12-month revenue.
What is the hourly or throughput limit for Greptile?
No published hourly cap. Starter: 50 credits/month for one active developer. Pro: 50 credits included per seat/month, then $1 per extra credit. One standard review uses 1 credit; one TREX review uses 3.
Is there a trial for Greptile?
14-day Pro trial.
Does Greptile autofix or block merges?
Autofix: Not verified. Merge gate: Not verified. Indexes the repository so reviews can reason about files outside the diff. TREX is a heavier review that costs three credits.
What is the catch with Greptile?
Credits run out: 50 standard reviews per seat, then $1 each, and TREX burns three credits. GitHub and GitLab only on the public pricing page. Confirm TREX vs standard before comparing catch-rate anecdotes from third-party blogs.