> ## Documentation Index
> Fetch the complete documentation index at: https://www.greptile.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Billing

> Understand Greptile's per-developer billing model, flex usage, credit limits, review counts, and subscription management.

## Pricing

| Unit                            | Price                               |
| ------------------------------- | ----------------------------------- |
| Active developer / month        | **\$30/seat** (includes 50 credits) |
| Additional credits (flex usage) | **\$1/credit**                      |

<Info>
  **1 credit = 1 standard review.**

  **3 credits = 1 [T-Rex](/docs/code-review/key-features#runtime-validation-with-t-rex-beta) review.**
</Info>

An **active developer** is any PR author with at least one completed review 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. Each finished review consumes one credit, charged to the PR author. Skipped reviews don't count.

Reviews run when you open a PR, comment [`@greptileai`](/docs/code-review-bot/trigger-code-review), or push commits with [`triggerOnUpdates`](/docs/code-review-bot/trigger-code-review#auto-review-on-every-commit) enabled.

## Usage limits

Organizations can cap flex usage in [**Organization Settings → Billing → Flex Usage Limit**](https://app.greptile.com/-/settings/billing) 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.

<Tabs>
  <Tab title="Dashboard">
    In [Code Review → Greptile Comments](https://app.greptile.com/review#greptile-comments), set **Authors** / **Exclude** and add:

    * `dependabot[bot]`
    * `renovate[bot]`
    * Any service accounts
  </Tab>

  <Tab title="greptile.json">
    ```json theme={}
    {
      "excludeAuthors": ["dependabot[bot]", "renovate[bot]"]
    }
    ```
  </Tab>
</Tabs>

## Dashboard

* [Settings → Usage](https://app.greptile.com/-/settings/usage): review counts and active developers
* [Settings → Billing](https://app.greptile.com/-/settings/billing): usage limits, payment methods, **Billing Portal** (plan status, invoices, cancellation)

<Note>
  For billing questions or enterprise pricing, contact [hello@greptile.com](mailto:hello@greptile.com).
</Note>