$ git diff main -- platform/github.md
commit a1b2c3d - author: Oliver Wakefield-Smith - verified 21 Jun 2026
Every tracked tool supports GitHub: 19 of 19 have first-class GitHub integration with PR comments, Checks API and branch-protection awareness. For GitHub Enterprise Server, the set narrows to the self-host-capable subset.
@@ 19 tools with GitHub support @@all first-class
1+CodeRabbit - Pro $24/dev/mo (annual)src
2+Qodo - Teams $30/user/mo (annual)src
3+Greptile - Pro $30/seat/mo (50 reviews included)src
4+Codacy - Team $18/dev/mo (yearly; $21 monthly)src
5+Sourcery - Pro $12/dev/mo (annual)src
6+Graphite Reviewer - Team $40 per user/month (billed annually, unlimited AI Reviews)src
7+GitHub Copilot Code Review - Bundled in Copilot Business $19/user/mosrc
8+Bito - Team $12/seat/mo (annual; $15 monthly)src
9+Claude Code Review - Team standard seat $20/mo annual ($25 monthly), 2-seat minimumsrc
10+Cursor BugBot - Usage-based on a Cursor plan, with no published BugBot ratesrc
11+DeepSource - Team $24 per user/month (billed yearly)src
12+SonarQube - SonarQube Team from $34/month for up to 100k LOCsrc
13+Snyk Code - Team $25/contributor/mo (annual, Snyk Code only)src
14+Macroscope - Team $22/dev/mo (annual, Macroscope v3)src
15+Qlty - Pro $20/contributor/mo (annual; $24 monthly)src
16+Augment Code Review - Standard $20/mo flat for the team (up to 50 seats, $20 usage included)src
17+Git AutoReview - Team $12.49/mo for the whole team (annual; $14.99 monthly)src
18+Launchable - Quote-only (contact sales)src
19+Diffblue Cover - Quote-only (contact sales)src
@@ GHES (Enterprise Server) support @@self-host required
1+CodeRabbit Enterprise, Qodo, SonarQube Server, DeepSource Enterprise, Snyk Code, Bito Enterprise - all serve GHES via their self-host product
2+Graphite Enterprise and Cursor BugBot both publish GHES support without self-hosting: they connect a SaaS control plane to your GitHub Enterprise Server
3-Sourcery and Augment Code publish no GHES path at all
@@ GitHub Actions integration @@ci
1All 19 GitHub-supporting tools have published Action templates. The difference is whether they comment via the Actions identity or via a dedicated GitHub App. Apps are cleaner for branch-protection - they appear as a named reviewer.
@@ branch-protection / CODEOWNERS pitfalls @@watch out
1-If your protection requires "1 approved review" AND a CODEOWNERS sign-off, an AI bot cannot satisfy CODEOWNERS. AI is augmentation, not the human reviewer.
2-Bots that comment as the Actions user can trip "dismiss stale reviews on push". Use a GitHub App identity instead.
@@ cross-links @@related