Skip to main content

​
Pricing

1 credit = 1 standard review.3 credits = 1 T-Rex review.
An active developer is anyone with at least one completed review charged to them in the billing period. Overages are per-author, not pooled across the team.

​
Additional credits

Each active developer gets 50 included credits per billing period, one credit per completed review. Usage beyond that appears as flex usage, billed at $1/credit: once a developer has used their 50 included credits, every further review they receive is flex, so their cost scales with actual review activity. It’s the same flex usage figure shown in your billing and usage dashboard. Flex is calculated per developer, not from a shared team pool. Each author works through their own 50 included credits first before any of their reviews count as flex. Discounts and promotional credits are shown in the billing dashboard.

​
How reviews are counted

Billing counts completed reviews, not PRs. Skipped reviews don’t count. Pull request reviews are charged to the PR author, not to the person who triggered the review. They run when a PR is opened, on a manual trigger from a comment or the web app, or when commits are pushed with triggerOnUpdates enabled. CLI reviews are either attributed or unattributed. An attributed CLI review is charged to the Greptile user who ran it and shares that user’s seat and included credits. To attribute CLI reviews, sign in with greptile login and connect your GitHub or GitLab account in Personal Settings → Account. An unattributed CLI review bills as flex usage and does not count as an active developer. API-key reviews are unattributed unless the key is bound to a user with a linked account.

​
Usage limits

Organizations can cap flex usage in Organization Settings → Billing → Flex Usage Limit to control spend. When projected spend hits the cap, Greptile skips reviews that would incur flex usage until the next billing period or until you raise the cap. Set the limit to $0 to disable flex usage. Authors still within their 50 included credits can continue to receive reviews even after the cap is reached.

​
Excluding bots

Excluded authors are not reviewed and don’t count as active developers.
In Code Review → Greptile Comments, set Authors / Exclude and add:
  • dependabot[bot]
  • renovate[bot]
  • Any service accounts

​
Dashboard

For billing questions or enterprise pricing, contact hello@greptile.com.