Skip to content

Compare

Forseti vs Greptile

A fair, sourced comparison: where Forseti is stronger, where Greptile is stronger, and what carries over if you switch.

Connect GitHubFull comparison

Greptile details accessed 15 Oct 2026

At a glanceForsetiGreptile
Price before the run
On the PR
Not shown in its docs[GR2]
Budget caps
Degrade to Glance
Not shown in its docs[GR2]
Training on your code
Never
Anonymised, unless you opt out (cloud)[GR4]

Who Greptile suits

Greptile, in fairness.

Greptile suits teams that want deep, repository-wide context and fine-grained control over how hard each part of a codebase is reviewed. It builds a graph of the whole repo, runs parallel agents that each test one bug hypothesis, and lets you set review tiers down to a single directory. Teams that cannot send code to a cloud service can self-host it, air-gapped, with their own model.[GR2][GR4][GR6]

Competitor details from their public pages, accessed 15 Oct 2026. Products change; tell us if something is out of date.

Feature table

Code hosts live
ForsetiGitHub, live. GitLab, Bitbucket and Azure DevOps: adapters built, reviews switch on in a coming release.
GreptileGitHub (including Enterprise Server), GitLab, Bitbucket and Gitea; Perforce on-prem. Integrations with Jira and Linear.[GR1]
Pricing model and list price
ForsetiPer PR, priced by depth. 1 credit = £0.01. A medium PR (about 1,000 lines): Glance £0.03, Standard £0.79, Deep £4.64. Team plan £8 per active PR author per month with 800 credits included. Recommended pricing, final after our golden-set evaluation.
GreptileSeat plus credits, USD. Free: 1 developer, 50 credits. Pro: $30 per seat including 50 credits, then $1 per credit. A seat is any developer who had a review. Base, Plus and Apex reviews cost 1, 3 and 10 credits; Auto charges for the tier that ran.[GR1][GR2][GR5]
Price shown before a review runs
ForsetiYes. Depth and price are posted on the PR before anything is spent.
GreptileNot shown: its review-tier docs show no price before the run.[GR2]
When a spend limit is reached
ForsetiCaps per PR, per developer and per month. At a cap the review drops to Glance and says so on the PR; it never stops silently. No auto-refill.
GreptileIts review-tier docs show no budget caps.[GR2]
Depth control
ForsetiGlance, Standard or Deep (Molecular in early access), set by policy per repo, branch and path, or with an @forseti command on the PR.
GreptileReview Tiers Base, Plus, Apex and Auto, set at org, team, repo and directory level; tier rules match label, target branch, file path and files changed. Separate strictness 1–3.[GR2][GR3]
Finding lifecycle across pushes
ForsetiReview Ledger: every finding keeps its ID and state across pushes, with one verdict per head SHA. Re-reviews charge only for the new changes.
GreptileNot stated publicly.[GR3]
Verification step
ForsetiA verification pass checks each finding before it is posted. Molecular depth (early access) adds sandboxed proof.
GreptileTREX (beta) runs the PR in a sandbox, generates tests and attaches logs, screenshots and video. Since v5, parallel agents each test one bug hypothesis.[GR7][GR6]
Config file, and where rules are read from
Forseti.forseti.yaml and .forseti/rules.md, read from the base branch, so a PR cannot change its own review.
Greptile.greptile/ folders that cascade by directory: strictness, comment types, rules with glob scope and severity, ignore patterns and filters. Which branch is read: not stated publicly.[GR3]
Learning from feedback
ForsetiIn testing: built and being verified. Team memory: learns what your team dismisses, and shows its precision (findings accepted against findings dismissed).
GreptileLearns from thumbs reactions and replies; it says it stops commenting on unwanted topics after 2–3 weeks.[GR3]
Data retention and training
ForsetiNo repository or diff storage: patches are fetched live and held in memory for at most 2 minutes. Findings keep a short snippet unless you switch it off. We do not train on your code.
GreptileSOC 2 Type II. Code cached until access is revoked. May train on aggregated, anonymised customer data unless you opt out (cloud).[GR4]
Self-host or bring your own key
ForsetiNot yet. Bring-your-own key and self-hosting are on the roadmap.
GreptileSelf-host and air-gapped deployment with bring-your-own LLM.[GR4]
IDE and CLI
ForsetiNot yet. A CLI and MCP pre-push verdict is coming.
GreptileCLI and MCP.[GR1]

Greptile prices are in US dollars as published. Forseti prices are our recommended pricing, final after our golden-set evaluation. “Not stated publicly” means we found no public statement on 15 Oct 2026.

Strengths

Where Forseti is stronger

Cost you can see, depth you choose.

  • The price is on the PR before it runsGreptile has shipped depth tiers too, but its docs show no price before the run. Forseti posts depth and price on the PR first.[GR2]
  • Caps that degrade, never stopCaps per PR, developer and month drop the review to Glance and say so on the PR. Greptile’s tier docs show no budget caps.[GR2]
  • No training on your codeForseti does not train on your code. Greptile’s cloud may train on aggregated, anonymised customer data unless you opt out.[GR4]
  • Re-reviews charge only what changedA push is reviewed as the interdiff, and only the new changes are charged.
  • One record per PRThe Review Ledger keeps every finding’s ID and state across pushes, with one verdict per head SHA.
  • Rules from the base branch only.forseti.yaml and team rules are read from the base branch, so a PR cannot weaken its own review.

Where Greptile is stronger

Credit where it is due.

  • More code hosts liveGitHub and Enterprise Server, GitLab, Bitbucket, Gitea and Perforce on-prem. Forseti is live on GitHub today; support for the other hosts is coming.[GR1]
  • Self-host, air-gapped, your own modelRuns inside your network with your own LLM. Forseti’s bring-your-own key and self-host are on the roadmap.[GR4]
  • A SOC 2 Type II reportGreptile has one today. Forseti does not yet.[GR4]
  • Directory-level controlConfig folders cascade by directory, and review tiers can be set per directory.[GR2][GR3]
  • Sandboxed test runsTREX (beta) runs the PR, generates tests and attaches logs, screenshots and video. Forseti’s sandboxed proof is in early access.[GR7]
  • Cross-repo contextOther repositories can be pulled into a review’s context through context.repos.[GR3]

Switching

Switching from Greptile.

Forseti imports your Greptile config, shows you what maps and what does not, and applies it when you say so. Paste the files, or let Forseti read them from your default branch.

Connect GitHubImport guide
Reads.greptile/config.json.greptile/rules.md

What carries over

  • strictness 1, 2 and 3 become Forseti’s thorough, balanced and quiet profiles
  • rules with a glob scope become path-scoped team rules; instructions becomes a team rule
  • .greptile/rules.md sections become team rules
  • ignorePatterns become ignored paths; includeBranches sets which branches are reviewed

What does not

  • commentTypes, labels, fileChangeLimit, excludeBranches, excludeAuthors and triggerOnUpdates
  • files.json context files

The preview lists every unmapped key, so nothing is dropped silently. Import is audited, and you can export everything back as .forseti.yaml and .forseti/rules.md.

See the price on your next PR.

Install the GitHub App, pick a repo, and Forseti reviews a real PR with the price on it before it runs.

Connect GitHubPricing

Sources

Greptile sources

  1. GR1Greptile pricing, accessed 15 Oct 2026
  2. GR2Greptile docs: Review Tiers, accessed 15 Oct 2026
  3. GR3Greptile docs: config reference, accessed 15 Oct 2026
  4. GR4Greptile security, accessed 15 Oct 2026
  5. GR5Greptile blog: introducing Plus and Apex, published 25 Sep 2026, accessed 15 Oct 2026
  6. GR6Greptile blog: Greptile v5, published 5 Aug 2026, accessed 15 Oct 2026
  7. GR7Greptile blog: TREX, published 15 Jun 2026, accessed 15 Oct 2026