Greptile Pricing and Greptile Cost per Developer for Teams

Greptile meters completed reviews, not pull requests. A skipped review costs nothing. A review runs when someone triggers it from a comment or the web app, or automatically on the events listed in the repository's auto-review setting: the pull request opening, a push, or a rebase. Turn on review-on-push and a pull request that goes through four rounds of changes uses four reviews.

Each review runs at one of three tiers. Base costs 1 credit, Plus 3 and Apex 10. A fourth setting, Auto, lets Greptile pick the tier for each pull request from its size, risk and complexity, and you pay for the tier that ran. Greptile recommends Auto as the default, plus two rules: Apex on pull requests into the production branch, and Apex on pull requests that change more than 30 files.

• A comment can raise the tier but never lower it. "@greptileai review this at apex" upgrades that one review, and later pushes go back to the configured tier.
• In a monorepo the highest tier wins. When one pull request touches directories with different tiers, the whole review runs at the highest one.
• CLI reviews run at Base unless the developer passes a flag for Plus or Apex.

Those rules are why two teams on the same plan can pay very different amounts. Before you roll Greptile out, decide which repositories deserve Plus or Apex and write that into the configuration rather than leaving it to Auto everywhere.

No. Greptile credits are not pooled across the team. Each active developer gets their own 50 credits per billing period, and flex usage is calculated per developer. A developer who uses 120 credits pays for 70 flex credits even if four teammates used only 10 each.

Reviews are charged to the pull request author, not to the person who asked for the review. So a senior engineer who triggers Apex reviews on a junior developer's pull requests spends the junior developer's credits. That matters on teams where most code comes from two or three people: their flex charges dominate the bill, and the rest of the seats carry unused credit you cannot move.

Two kinds of review sit outside the seat model. A CLI review run by a signed-in user with a linked GitHub or GitLab account is attributed to that user and uses their credits. An unattributed CLI review, and any review made with an API key that is not bound to a user, is billed straight to flex usage and does not create an active developer.

Greptile lets an organization cap flex spend under Organization Settings, Billing, Flex Usage Limit. When projected spend reaches the cap, Greptile skips any review that would incur flex usage until the next billing period or until you raise the limit. Setting the limit to $0 turns flex off completely, which turns Pro into a flat $30 per active developer.

The cap does not stop developers who still have included credits. They keep receiving reviews after the cap is hit. Only reviews that would cost extra are skipped, so a cap protects the budget without switching review off for the whole team.

The second control is bot exclusion. Add dependabot, renovate and any service accounts to the excluded authors list in the dashboard or in greptile.json. Excluded authors are not reviewed and do not count as active developers, so a busy dependency bot never turns into a $30 seat plus flex.

Greptile is free on its Starter plan for one active developer, with 50 credits a month and unlimited repositories. That is enough for a solo developer or a trial on a single repository. A team needs Pro, which starts with a 14-day free trial.

Greptile is also free for qualified non-commercial open-source projects with an OSI-approved license, through an application. Commercial teams at pre-Series A startups with under $2 million in revenue over the last 12 months can apply for a 50% discount, which brings the seat to $15. Greptile's page does not say whether the discount also applies to flex credits, so ask before you budget heavy Apex use on it.

Greptile Enterprise is custom priced through sales. Greptile does not publish a rate. The plan includes everything in Pro plus self-hosting in your own infrastructure, SSO and SAML, GitHub Enterprise Server and GitHub Enterprise Cloud with data residency, GitLab Self-Managed, Bitbucket Data Center and Gitea, Perforce with P4 Code Review for on-premises deployments, security and compliance reviews, a dedicated Slack support channel, custom invoicing and payment terms, and a custom DPA and terms of service.

For US companies the deciding item is usually hosting. If your code cannot leave your own cloud or data center, Enterprise is the only Greptile plan that fits, and it is also the only route to Bitbucket Data Center and Perforce. If your repositories live on github.com and SSO is the only requirement, ask whether Pro with an annual contract meets the security review before you open an Enterprise negotiation.

Credit metering works well when each developer gets a predictable number of reviews at a predictable depth. It costs more than it needs to when review-on-push multiplies reviews, when a few authors produce most of the pull requests, or when you want deep reviews on automated pull requests from coding agents that do not map to a person.

The Code Reviewer agent in our catalog reviews every pull request on the repositories you connect, comments with concrete fixes and enforces your conventions for a flat monthly price from $49, with no credits and no per-author overage. It connects to GitHub with permissions you can revoke. Teams use it next to a seat-based reviewer or instead of one on internal repositories. Compare the pricing models side by side in our AI agent pricing guide.