Compared with hosted reviewers
Each cell is what the vendor's own documentation or pricing page said on the date below. If something is out of date, open an issue and it gets fixed.
| Criterion | Mergerie | CodeRabbit | GitHub Copilot code review | GitLab Duo Code Review |
|---|---|---|---|---|
| Where the review runs | On your machine | CodeRabbit's cloud; self-hosted only on the Enterprise tier | GitHub's cloud | GitLab.com, Self-Managed or Dedicated, through GitLab's AI gateway; self-hosted models on some tiers |
| Does your code leave your machine for the review? | Only to the model behind your own Claude, Copilot, Codex or Gemini subscription, exactly as when you use their CLI | Yes, to the vendor | Yes, to GitHub | Yes, to GitLab and its model provider, unless you run a self-hosted model |
| Forges | GitLab and GitHub, side by side, repository by repository | GitHub and GitHub Enterprise Server, GitLab and self-managed GitLab, Bitbucket Cloud and Data Center, Azure DevOps | GitHub only | GitLab only |
| Cost | No Mergerie bill; each pass draws on the quota of the Claude Code, Copilot, Codex or Gemini plan you already have | $24 (Essentials), $48 (Team) or $72 (Advanced) per developer per month, billed annually; Enterprise on quote; free on public open-source repositories | Included in the paid Copilot plans, from $10 per user per month, not in Copilot Free. Since 1 June 2026 each review, on a pull request or in the IDE, draws 13 premium requests from the monthly allowance | Duo Pro or Duo Enterprise seats on Premium / Ultimate, price on request; or usage-based Credits for the Code Review Flow, available from the Free tier |
| API key or subscription to buy | No: it drives the vendor CLI you already pay for | A CodeRabbit account | A paid Copilot plan | A Duo add-on, or Credits |
| Scored report with findings at file:line | Yes, versioned, with incremental re-review | Yes | Yes (review comments) | Yes (review comments) |
| Convergence loop: review → AI fix → re-review until a threshold | Yes, with a score threshold and a cap on passes; your verifier's verdict is shown beside each pass, never used as the exit condition | No: suggestions and one-click fixes | No | No: Duo can change the code to resolve a discussion, but there is no scored loop |
| Objective verification (your own test commands, verdict on the MR) | Yes, including several MRs verified as one set; commands suggested from what the clone declares, containers through docker compose run in the line itself | No (relies on CI) | No (relies on Actions) | No (relies on CI) |
| Ask, outside any merge request, where a subject lives across your repositories | Yes: a domain agent maps the subject across the repositories you tick, keeps the map, and counts the commits that have aged it | Linked repositories (.coderabbit.yaml) let a review cross repository boundaries; no standalone cross-repository question documented | Not documented: the context is the pull request | Not documented: the context is the merge request |
| Coding sessions from a ticket, multi-repository | Yes (Jira ticket → branch, prompt, commit, MR), with an optional plan-then-approve pass | No | Copilot coding agent (GitHub issues) | Duo Agent Platform, tier- and add-on-dependent |
| Review rules that fire on a path and badge the MR | Yes | Path instructions in .coderabbit.yaml | Path-specific instruction files (.github/instructions/**/*.instructions.md) | Custom instructions; nothing path-specific documented |
| Publishes the report on the MR | On demand, or automatically if you tick the box: the report, or only its link when the team shares a data repository | Automatically | On request by default; automatically if you configure it | Automatically, on merge requests that are not drafts |
| Multi-user / team | Yes, without a server: a git repository the team owns holds rules, verifiers, agents, reviews and the pages you tick; tokens and drafts never travel (see teams) | Yes | Yes | Yes |
| Where the team's rules, reviews and knowledge are stored | As readable files in a git repository on your forge, with git log as the audit trail | On CodeRabbit's servers (learnings, reports) | On GitHub | On GitLab |
| License | AGPL-3.0, open source | Proprietary | Proprietary | Proprietary |
Sources
- CodeRabbit: pricing
- CodeRabbit: supported platforms
- CodeRabbit: knowledge base and linked repositories
- GitHub: using Copilot code review
- GitHub: Copilot plans
- GitHub: premium requests (13 per code review since 1 June 2026)
- GitLab: Duo in merge requests
- GitLab: Duo subscription add-ons
- Mergerie guide
The honest summary: if your code may live on a vendor's servers and your team is on GitHub, the hosted tools are excellent and need no install. Mergerie starts where that is not the case: your code may not leave, or you are on GitLab, or you already pay for Claude Code, Copilot, Codex or Gemini and refuse a second bill, or your team wants its rules, reviews and knowledge as files in a repository it owns.