# Greptile — AI code review agents that review and test every pull request with full codebase context. > Source: The Agents Index — https://theagentsindex.com/greptile (structured, researched, re-verified) > Facts last verified: 2026-10-24 Greptile is an AI code review platform that indexes a repository as a graph and runs parallel agents over every pull request. Its TREX agent additionally builds the branch in a sandbox and exercises the app to find runtime bugs. | Fact | Value | | --- | --- | | Website | https://greptile.com | | Price | free, then from $1/credit pay-as-you-go | | Free tier | Yes | Starter is free indefinitely for 1 active developer with 50 free credits per month and unlimited repositories; Pro additionally offers a 14-day free trial with no credit card required. Qualified OSI-licensed non-commercial projects are free, and pre-Series A startups under $2M revenue get 500 free credits a month for 6 months. ## What it does **Writes code** · Partly — It writes suggested code for its own findings and sends that patch to your coding agent to apply, rather than authoring features from a description itself. > Every review comment includes a **Fix with your Agent** button that sends the issue — with file paths, line numbers, and suggested code — directly to your coding agent. > — https://www.greptile.com/docs/code-review/key-features · Fix All with AI section **Debugs and fixes** · Partly — It diagnoses failures from review and from running the branch, then hands the fix to Claude Code, Codex, Cursor or Devin instead of landing it. > TREX runs your PR branch in a sandbox to find the bugs that only show up at runtime. > — https://www.greptile.com/trex · Hero paragraph **Writes tests** · Yes — It generates unit tests for new and changed code on every pull request, and the TREX agent writes and runs end-to-end flows in a sandbox. > Automatically generate unit tests for new and changed code in every PR > — https://www.greptile.com/agent · Anatomy of a Greptile PR review, Test generation card **Reviews code** · Yes — Reviewing someone else's diff is the whole product: parallel agents comment inline on every pull request with repository context. > AI agents that review and test pull requests with full context of the codebase. > — https://www.greptile.com/ · Homepage hero subheading **Whole-codebase work** · Partly — It indexes the whole repository as a graph and reads adjacent repos for context, but it reasons over a diff rather than carrying a migration across the codebase itself. > Greptile builds a graph of your repository (functions, classes, imports, dependencies) and uses it during reviews to reason about ripple effects beyond the diff. > — https://www.greptile.com/docs/code-review/key-features · Full codebase context section **Ships it** · Partly — It can approve a pull request itself when its own review is a clean 5/5 within your risk ceiling, but merging and deploying stay with your repository rules. > Greptile's approval reflects its own assessment. Human requested-changes reviews and unresolved discussions do not block it. Your repository's merge rules still enforce any required human approvals, checks > — https://www.greptile.com/docs/code-review/auto-approve-prs · What always blocks auto-approval section **Done-for-you service** · No — You run the software yourself: connect a code provider and enable repositories, with setup documented as a five-minute self-serve task rather than delivered by Greptile staff. > 5-minute quickstart Connect GitHub or GitLab → Enable repositories → Get your first review > — https://www.greptile.com/docs/introduction · Ready to get started? card ## How much it does unattended **Runs autonomously** · Yes — Reviews fire automatically on pull request events with no human prompting, and auto-approve lets it close the loop on low-risk changes unattended. > On every pull request, Greptile analyzes changes with full context. Posts findings in ~3 minutes as PR comments with suggested fixes. > — https://www.greptile.com/docs/introduction · How it works, step 2 **Multi-agent** · Yes — A swarm of parallel review agents works one pull request at once, and the separate TREX agent runs the branch alongside them. > Swarm of agents review the PR Parallel agents review changes, assess their impact beyond the diff, and flag issues. > — https://www.greptile.com/ · How Greptile reviews every PR, step 2 **Agent permissions** · Yes — Admins decide how far it may act: a risk ceiling for self-approval, path and label filters, and separate permissions for who it answers at all. > Turn on **Cap risk level**, then choose the highest risk level Greptile is allowed to approve. Greptile only auto-approves PRs at or below this level. > — https://www.greptile.com/docs/code-review/auto-approve-prs · Configure auto-approve, step 3 ## Which models it runs on **Claude** · Yes — Claude is one of the frontier models behind cloud reviews, and self-hosted deployments configure Anthropic as the reasoning provider. > Smart (reasoning) | Code review, agent tasks | Claude Sonnet 4.5+, GPT-5.x/6.x > — https://www.greptile.com/docs/deployment-options · LLM Providers table, Smart row **GPT** · Yes — GPT models run the reasoning and fast tiers, and self-hosted installs can switch the whole review workflow to a GPT routing policy. > If you use GPT for reviews, set the GPT routing policy instead. > — https://github.com/greptileai/akupara/blob/main/docs/configuration/llm-providers.md · GPT-based review routing section **Open models** · Partly — Self-hosted installs route through a LiteLLM proxy you can replace with your own, but the supported-provider list names only Anthropic, OpenAI, Azure AI Foundry and Bedrock, so open-weight models are not a documented option. > Supported providers - Anthropic (required unless you use Bedrock for the same models) - OpenAI - Azure AI Foundry - AWS Bedrock > — https://github.com/greptileai/akupara/blob/main/docs/configuration/llm-providers.md · Supported providers list **Model choice** · Partly — On the cloud Greptile picks the models itself; only self-hosted customers choose, by pointing the proxy at their own provider keys. > Greptile uses the best set of models at any time, so your reviews are always SOTA. > — https://www.greptile.com/independence · Ways Greptile plugs into your workflow, Model agnostic card ## Where you use it **In your editor** · Yes — Its MCP server puts review comments and fixes inside Cursor, Claude Code, VS Code and Codex, and a Claude Code plugin resolves comments in the editor. > Use Greptile's MCP server to access code review tools directly in Claude, Cursor, VS Code, or Codex CLI. > — https://www.greptile.com/docs/mcp-v2/overview · MCP Overview page description **On the command line** · Yes — A published CLI installs via Homebrew or npm and reviews the local branch before you push, with JSON and plain-text output for scripts. > Use the Greptile CLI to review local branches before you push. > — https://www.greptile.com/docs/code-review/greptile-cli · Greptile CLI intro **In your pipeline** · Yes — Reviews are driven by pull-request webhooks, and the CLI authenticates with an API key specifically for CI runs. > For CI or self-hosted deployments, use an API key: export GREPTILE_API_KEY=... greptile review > — https://www.greptile.com/docs/code-review/greptile-cli · Sign in section **In a browser** · Yes — There is a hosted dashboard for settings, repositories, billing and an analytics tab with exportable review metrics. > The Analytics dashboard gives you visibility into review activity, comment quality, and team performance. Access it from the **Analytics** tab. > — https://www.greptile.com/docs/analytics · Analytics Dashboard intro ## Whose machine it runs on **Self-hosted** · Partly — Self-hosting in your own infrastructure, including air-gapped, is real but sits on the Enterprise plan and needs a separate licence. > Everything in Pro, plus - Self-host in your own infrastructure > — https://www.greptile.com/pricing · Enterprise plan card **Open source** · No — The platform is closed: the public repository holds only deployment artefacts and helm charts, while the terms reserve all rights and forbid reverse engineering. > decompile, disassemble, or reverse engineer the Platform, in whole or in part > — https://www.greptile.com/terms-of-service · Section 1.4 Restrictions **Licence** · No — Proprietary: Greptile reserves all ownership of the platform and grants only non-exclusive, non-transferable access, so a company cannot ship it under its own licence. > Company owns and reserves all other rights, title, and interest in and to the Platform and Services > — https://www.greptile.com/terms-of-service · Section 1.5 Ownership **Open-source runtime** · No — Even self-hosted, you cannot run it without Greptile: the deployment needs a licence and credentials for Greptile's container registry. > Self-hosted requires a license. Contact sales@greptile.com. > — https://www.greptile.com/docs/deployment-options · Pricing section **Runs in your cloud** · Partly — It deploys into your own AWS, GCP, Azure or on-prem environment with Docker Compose or Kubernetes, but that path is Enterprise-only. > Self-hosted Greptile runs in your own infrastructure, on-premises or in your virtual private cloud (VPC), so your code never leaves your environment. > — https://www.greptile.com/security · Hosting, Self-hosted section ## Building with it **Tracing and evals** · Yes — Every review and every finding is inspectable: an analytics dashboard with export, a searchable table of all flagged bugs, and TREX recordings, logs and traces per run. > Stat cards break findings down by severity — **All bugs**, security issues, **P0**, **P1**, and **P2** — above a table of every finding. > — https://www.greptile.com/docs/analytics · Bugs Caught tab section ## What it costs to run **How it meters** · Yes — It bills per prepaid credit at one dollar, with no seat fee on Pro, so cost tracks review volume and depth rather than headcount. > Greptile uses prepaid credits. Credits cost **$1** each and are shared across your organization. > — https://www.greptile.com/docs/code-review-bot/billing-seats · Billing intro **Cost of one job** · Yes — One pull-request review costs 1 credit, so one dollar at Base; a deeper Plus review is 3 credits, Apex 10, and a TREX test run adds 3 on top. > | Base review | 1 | | Plus review | 3 | | Apex review | 10 | | TREX run | 3 | > — https://www.greptile.com/docs/code-review-bot/billing-seats · What credits pay for table **Price per 1,000 requests** · Yes — $1000 per 1,000 requests in Base review, 1 credit a request at $1 a credit, its cheapest mode. > $1/credit > — https://www.greptile.com/pricing · Plan table, Pro price cell **Free credit** · Yes — $50 of free usage (50 credits at $1 each), a month. > 50 free credits per month > — https://www.greptile.com/pricing · Starter card, How it works **Free tier** · Yes — A standing Starter plan is free for one active developer with 50 credits a month, and the Pro trial starts without a card or a sales call. > Starter is free for one developer and includes 50 credits per month. > — https://www.greptile.com/pricing · FAQ, How does pricing work? **API access** · Yes — The vendor confirms an API for use in your own product, and the CLI authenticates against it with a GREPTILE_API_KEY, though no public REST reference is published. > Can I use Greptile's API for my own product? Yes, we offer discounted bulk pricing for API use. > — https://www.greptile.com/ · Homepage FAQ **MCP server** · Yes — Greptile ships an MCP server another agent can call to fetch comments, apply fixes, read the repository knowledge base and pull review reports. > The Greptile MCP server lets AI coding assistants (Claude, Cursor, Copilot, Codex) access your code review data directly. > — https://www.greptile.com/docs/mcp-v2/overview · MCP Overview, What You Can Do intro **Bring your own key** · Partly — Bringing your own inference is a self-hosted capability: you configure provider base URLs and keys yourself, which puts it on the Enterprise plan. > Self-hosted customers bring their own LLM provider by configuring its base URL and keys. > — https://www.greptile.com/security · Hosting, Self-hosted section ## Buying it for a team **A company can buy it** · Yes — Pro and Enterprise are organisation purchases: credits are bought centrally and shared, and Enterprise adds custom invoicing and payment terms. > Credits are prepaid and shared across your whole org. > — https://www.greptile.com/pricing · Pro plan card, How it works **Seat model** · Yes — Pro charges nothing per seat and places no ceiling on developers or agents; the free Starter plan is the one with a floor, a single active developer. > Unlimited developers and agents, no seat fees > — https://www.greptile.com/pricing · Pro plan card, How it works **Pooled budget** · Yes — One prepaid credit balance serves the whole organisation rather than per-user allowances, and reviews pause for everyone when it empties. > Pro has no seat fees: you pay $1 per credit, and credits are shared across your whole organization. > — https://www.greptile.com/pricing · FAQ, How does pricing work? **Admin controls** · Yes — Admins set org-wide review configuration, who Greptile responds to, the auto-approve risk ceiling and protected paths, with stricter values winning over repo files. > Choose who Greptile responds to. **Who can use Greptile** sets all four at once > — https://www.greptile.com/docs/account/organization-settings · Permissions section **Audit log** · Partly — Audit logging is listed as part of the enterprise deployment tier rather than a documented feature of the self-serve plans, and no page describes the log itself. > Cloud (SOC2 Type II), self-hosted Docker/Kubernetes, air-gapped * SSO/SAML, audit logging, role-based access > — https://www.greptile.com/docs/code-review/key-features · Enterprise-grade deployment bullets **Single sign-on** · Partly — SAML 2.0 single sign-on with Okta, Entra ID and others is real but gated: the vendor states it is an Enterprise feature set up by support. > SSO & Identity is an Enterprise feature. Contact support@greptile.com to set it up for your organization. > — https://www.greptile.com/docs/security/sso-and-identity · Note callout at top ## What happens to your code **Opt out of training** · Yes — An organisation admin can switch training off in settings, and self-hosted deployments collect nothing for machine learning unless you configure it. > To opt your organization out of AI training, an organization admin can open Organization Settings, go to **Data & Privacy**, and turn off **Help us improve Greptile**. > — https://www.greptile.com/security · AI Training, Opting Out section **Data residency** · Partly — Cloud code sits on Greptile-provisioned AWS infrastructure with no published region choice; controlling the jurisdiction means the Enterprise path of self-hosting or GitHub Enterprise data residency. > GitHub Enterprise Server and Enterprise Cloud with data residency > — https://www.greptile.com/pricing · Enterprise plan card, Everything in Pro plus **Getting out** · Yes — You can delete all customer data from settings and request a copy within 30 days of termination; analytics can be exported, but nothing states whether prepaid credits expire. > Company will transfer a copy of Customer Data in Company's possession or control to Customer within thirty (30) days following any termination or expiration > — https://www.greptile.com/terms-of-service · Section 2.5 End of Term; Data Transfer **Certifications** · Yes — SOC 2 Type II is audited with the report available on request, and the vendor also claims HIPAA and GDPR compliance for enterprise deployments. > Greptile is also SOC 2 Type II, HIPAA and GDPR compliant. > — https://www.greptile.com/enterprise · FAQ, Can Greptile be deployed on-prem? ## What changed - 2026-10-24 — Free plan · Plan limits · Price · Usage terms · What it can do ## Keeping it current These facts are re-checked against Greptile's own pages and updated when they change. If you represent Greptile, sign in and update the listing from your dashboard at https://theagentsindex.com/dashboard. The operations this site accepts from an agent are listed at https://theagentsindex.com/.well-known/agents.json — that catalog needs no key to read, and each entry states its own auth.