$ git diff main -- platform/bitbucket.md
commit a1b2c3d - author: Oliver Wakefield-Smith - verified 21 Jun 2026
Only 12 of the 19 tracked tools support Bitbucket. Coverage is sparse because Bitbucket's API surface for AI review integrations has lagged GitHub for years. Atlassian Rovo (the in-platform optionsrc) is a credible default for Bitbucket-only shops. For multi-platform parity, third-party tools win.
@@ 12 tools that support Bitbucket @@cloud + data center
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+Bito - Team $12/seat/mo (annual; $15 monthly)src
6+Cursor BugBot - Usage-based on a Cursor plan, with no published BugBot ratesrc
7+DeepSource - Team $24 per user/month (billed yearly)src
8+SonarQube - SonarQube Team from $34/month for up to 100k LOCsrc
9+Snyk Code - Team $25/contributor/mo (annual, Snyk Code only)src
10+Git AutoReview - Team $12.49/mo for the whole team (annual; $14.99 monthly)src
11+Launchable - Quote-only (contact sales)src
12+Diffblue Cover - Quote-only (contact sales)src
@@ why coverage is sparse @@historical
1-Bitbucket's API surface for inline PR comments has historically required more bespoke vendor work than GitHub
2-Bitbucket installed base is concentrated in enterprises that buy through Atlassian Marketplace; vendor sales cycles are longer
3+CodeRabbit, Qodo, Codacy, DeepSource, SonarQube, Bito, Snyk Code - the vendors that did the work get the market
4+Two more arrived in 2026: Cursor BugBot publishes Bitbucket including Data Center, and Git AutoReview publishes Bitbucket Cloud, Server and Data Centersrc
5-Codacy is Bitbucket Cloud only, and its AI Reviewer is GitHub-only, so on Bitbucket you are buying the rule-based coresrc
@@ Atlassian Rovo @@the in-platform path
1Rovo is Atlassian's in-platform AI surface and includes PR-review capabilities. Pricing is per-Atlassian-user-month, bundled in Jira / Confluence / Bitbucket cloud. Solid for Atlassian-monoculture shops. Cannot follow you off-platform.
@@ mirror-to-GitHub workaround @@when it makes sense
1-Mirror Bitbucket to a private GitHub repo, point the AI reviewer at GitHub, push comments back. Real teams do this.
2-Worth it if your preferred tool does not yet support Bitbucket and switching tool is more painful than the mirror
3-Not worth it below ~50 devs - the operational drag exceeds the tool-choice gain
@@ cross-links @@related
1/tool/coderabbit
2/tool/qodo
3/tool/codacy