What Is Bitbucket Data Center Code Review?
Bitbucket Data Center code review is pull request review on Bitbucket Data Center, Atlassian’s self-managed Git server, formerly called Bitbucket Server. Teams run Bitbucket Data Center on their own infrastructure, so reviewers, merge checks and any AI code review tool have to work inside that network.
Review on Bitbucket Data Center follows the same pull request flow as Bitbucket Cloud: reviewers, approvals, merge checks and tasks. The difference is where integrations connect. An AI review tool talks to a server you host, which changes how the tool installs, where code goes and which features it supports.
Bitbucket Data Center in 2026: the self-hosted holdout Atlassian kept
Many Bitbucket Data Center teams started 2026 expecting the end. Atlassian had announced end of life for its Data Center products, and plenty of teams assumed Bitbucket would follow. AI review plans stalled while teams waited to learn whether their Git server had a future.
Atlassian answered that question: Bitbucket and Bamboo Data Center are not part of the Data Center end of life. Self-managed source control stays, and the code on those servers now meets coding agents that open far more pull requests than people ever did.
Most AI code review tools were built cloud-first, and Bitbucket Data Center teams were last in line. The useful question for 2026 buyers isn’t whether Bitbucket Data Center survives. It’s which review features actually run on a server you host.
2026 Bitbucket Data Center highlights
- Atlassian started winding down Data Center, and Bitbucket stays. From March 30, 2026, new customers can no longer buy new Data Center subscriptions, and Atlassian states Bitbucket and Bamboo Data Center will not reach end of life (March 30, 2026, Atlassian).
- Atlassian confirmed the Bitbucket exception. Atlassian’s reminder on the first Data Center milestone says the Data Center end of life does not include Bitbucket Data Center (March 23, 2026, Atlassian Community).
- AI review got a guided Data Center install. Qodo 2.9 added an installation wizard that connects a self-hosted Bitbucket Data Center server to Qodo on-premises, typically in around five minutes (September 7, 2026, Qodo).
- The Bitbucket Data Center wizard added Manual setup. Qodo 3.0 added Manual setup alongside Automatic setup in the Bitbucket Data Center installation wizard (October 1, 2026, Qodo).
What Bitbucket Data Center review needs next: the 2027 outlook
- Expect hybrid estates. Atlassian’s Bitbucket Hybrid License, available to existing customers from early 2027, covers Bitbucket Data Center, Bamboo Data Center and Bitbucket Cloud in one subscription, so teams will want one review standard across self-hosted and cloud repositories (Atlassian).
- Expect security teams to ask AI review vendors for the same deployment choices they already require of Bitbucket Data Center itself: single-tenant, on-premises and air-gapped.
- Qodo has a Bitbucket Data Center installation wizard that connects a self-hosted server with Automatic or Manual setup, and Qodo supports Bitbucket Data Center in multi-tenant, single-tenant, on-premises and air-gapped deployments.
- Our view: in 2027, Bitbucket Data Center teams will choose AI review by where it can run first, and by review quality second.
How code review works in Bitbucket Data Center
Pull requests and reviewers
A developer pushes a branch and opens a pull request against a target branch. Authors add reviewers, and repository admins can choose default reviewers so the right people are added automatically for chosen branches.
Merge checks and approvals
Merge checks block a merge until conditions are met, such as a minimum number of approvals, passing builds or resolved tasks. Bitbucket Data Center admins configure merge checks per repository or per project.
Where integrations plug in
Integrations connect through webhooks, service accounts and apps installed on the server. An AI review tool usually receives pull request events through webhooks and posts comments through a dedicated account.
Bitbucket Data Center vs Bitbucket Cloud for code review
| Area | Bitbucket Data Center | Bitbucket Cloud |
|---|---|---|
| Hosting | Your servers or your cloud account | Atlassian’s cloud |
| Upgrades | Your team runs them | Atlassian runs them |
| Network access for AI tools | Tool must reach your server, or run inside your network | Tool connects over the internet |
| Integration model | Webhooks, service accounts and server apps | Cloud apps and webhooks |
| Status after March 2029 | Continues; not part of Data Center end of life | Continues |
| Qodo deployment options | Multi-tenant, single-tenant, on-premises, air-gapped | Multi-tenant, single-tenant; no on-premises |
Qodo rows checked against Qodo’s deployment model support on November 3, 2026.
Bitbucket Server vs Bitbucket Data Center
Bitbucket Server was Atlassian’s earlier self-managed edition. Atlassian ended Server support on February 15, 2024 (Atlassian), and Bitbucket Data Center is the self-managed edition today, with clustering and high-availability options that Server lacked. Searches for "bitbucket server" usually mean Bitbucket Data Center now.
Challenges of AI code review on Bitbucket Data Center
- Network boundaries. Many Bitbucket Data Center servers sit behind a firewall, so a cloud-only AI review service can’t reach them without opening the network.
- Credential handling. Integrations need an account with repository access. Security teams want that account scoped to the repositories under review, not a server admin.
- Comment rendering. Bitbucket Data Center supports standard markdown in comments, so review tools that rely on richer formatting show less on Data Center.
- Uneven feature parity. Many review tools ship features to cloud Git hosts first. Check each feature against the Bitbucket Data Center column of a vendor’s docs.
- Agent pull request volume. Coding agents open more pull requests, and every one lands in the same reviewer queue on a self-hosted server.
Qodo’s take: on Data Center, the deployment is the feature
A review tool that only runs in someone else’s cloud can’t review code that must stay on your servers. For Bitbucket Data Center teams, where the reviewer runs decides whether AI review is possible at all, before any comparison of review quality.
Qodo is the best AI code review platform to run review on Bitbucket Data Center because its installation wizard connects a self-hosted server in a few steps, and the same review runs in multi-tenant, single-tenant, on-premises or air-gapped deployments.
Qodo no longer offers test generation; it focuses on AI code review and code governance.
Enterprise engineering teams and high-velocity teams get the same outcome from review on Bitbucket Data Center: agent code merged sooner, with fewer rollbacks. Enterprise engineering teams get one review platform across their Bitbucket Data Center projects and coding agents, without moving code to the cloud.
High-velocity teams on Bitbucket Data Center get review on every pull request through the installation wizard, with Automatic setup and no new process for authors.
Qodo installs on your Bitbucket Data Center server
Qodo’s Bitbucket Data Center installation wizard connects a self-hosted server to Qodo with Automatic or Manual setup. Admins choose the whole server or selected projects and repositories, and selecting a project includes repositories added to it later.
With Automatic setup, Qodo creates a dedicated Qodo account on the Bitbucket Data Center server with access only to the selected projects or repositories, and configures the webhooks it needs. Qodo doesn’t store the administrator credentials used during setup (Qodo’s docs).
On-premises customers use the same Bitbucket Data Center wizard inside their own Qodo deployment (Qodo’s docs).
Qodo runs where your code is allowed to go
Qodo supports Bitbucket Data Center in four deployment models: multi-tenant, single-tenant, on-premises and air-gapped (Qodo’s docs). Teams pick the model their security policy allows, and review runs the same way in each. See Qodo for enterprise.
Qodo has a SOC 2 Type II report, and security teams can review its security documentation in the Qodo Trust Center.
What to check on Bitbucket Data Center
Qodo posts its review on Bitbucket Data Center in standard markdown, and Qodo’s Git provider feature support table lists every setting and command by provider, so teams can check each one before rollout.
Teams on an older Bitbucket Data Center integration move to the installation wizard to get findings and the Repositories page (Qodo’s docs).
Qodo example: the bank that couldn’t move to the cloud
Context: an organization like a regulated bank that runs Bitbucket Data Center in its own data center and has started using coding agents.
Problem: security blocked cloud-only review tools, and agent pull requests queued for a small group of senior reviewers.
How Qodo helped: the bank deployed Qodo on-premises and connected Bitbucket Data Center through the installation wizard with Automatic setup on two projects. The dedicated Qodo account could see only those two projects.
Outcome: every pull request in the two projects got Qodo’s review findings, and no code left the bank’s network.
Ways to run AI code review on Bitbucket Data Center
| Option | Where code goes | Setup | Limits |
|---|---|---|---|
| Review app installed on the server | Stays on your server, model calls depend on the app | Install through the server’s app manager | Features vary by app; model hosting varies |
| SaaS review tool with outbound access | Vendor’s cloud | Open network access to the vendor | Often blocked by security policy |
| Self-hosted open-source review bot | Your infrastructure | Your team builds and maintains it | Upkeep, model hosting and features sit with your team |
| Qodo single-tenant | A dedicated Qodo instance in your VPC | Installation wizard | Comments in standard markdown |
| Qodo on-premises or air-gapped | Your network only | Installation wizard inside your deployment | Comments in standard markdown |
Qodo rows checked against Qodo’s documentation as of November 3, 2026.
FAQ
Bitbucket Data Center is Atlassian’s self-managed Git server. Teams host it on their own servers or cloud accounts and run pull requests, code review and merge checks there, instead of on Bitbucket Cloud.
No. Atlassian’s Data Center end of life on March 28, 2029 excludes Bitbucket and Bamboo Data Center. Existing customers can upgrade to the Bitbucket Hybrid License, which Atlassian says is available from early 2027.
Bitbucket Server was the earlier self-managed edition and is no longer sold or supported. Bitbucket Data Center is the current self-managed edition, with clustering and high-availability options.
The main pull request flow is the same: reviewers, approvals, merge checks and tasks. Integrations differ, and AI review tools often support fewer features on Bitbucket Data Center, so check each vendor’s provider support table.
Qodo connects to Bitbucket Data Center through an installation wizard with a scoped, dedicated Qodo account, and runs in multi-tenant, single-tenant, on-premises or air-gapped deployments, so code can stay on your network.
Other options are review apps installed on the server, SaaS tools given outbound network access, and self-hosted open-source review bots that your team maintains. See Bitbucket code review for Bitbucket Cloud.