Keep Bitbucket Data Center inside your boundary. iTmethods operates it.

Atlassian says Bitbucket Data Center will not reach end of life, but standalone licenses end on 28 March 2029. After that Atlassian sells it only through its Hybrid License. iTmethods runs it inside your authorization boundary as a single-tenant dedicated instance.

Available today Book a 30-minute operations briefing The hardening sheet →

The decision you are being forced to make

Atlassian set the dates. You still choose the posture.

Atlassian’s published Data Center lifecycle forces a near-term decision for every Atlassian customer. Bitbucket Data Center is the one product in the family Atlassian says will not reach end of life, but its standalone license still has a date, so the decision is about posture and licensing rather than survival. All dates below are Atlassian’s own.

Date	What happens	What it means
30 March 2026	New Data Center license cutoff	Atlassian stops selling new Data Center licenses to new customers. After this date, if you do not already hold a Bitbucket Data Center license, you cannot buy one as a new customer.
Early 2027 (date to follow)	Hybrid license	Atlassian has announced the Bitbucket Hybrid License, so existing Data Center customers can run Data Center and Cloud side by side. Atlassian’s Hybrid License page, re-read on 27 October 2026, says existing customers can upgrade to it in early 2027, with the exact date to follow. Confirm its availability with Atlassian before you plan against it.
30 March 2028	Expansion window closes	Existing customers can keep expanding their license footprint until this date. After it, expansions close too.
28 March 2029	Other Data Center products go read-only	Jira, Confluence and Jira Service Management Data Center go read-only. Bitbucket Data Center does not reach end of life, but standalone Bitbucket Data Center licenses end on this date. After it, Atlassian sells Bitbucket Data Center only through the Hybrid License. The full Atlassian timeline →

Dates as published by Atlassian. Confirm them against Atlassian’s own lifecycle documentation before you plan against them. They are that vendor’s to change, not ours.

Deployment

Bitbucket Data Center, single-tenant in every shape. Multi-node Data Center clustering is wired to your load balancer and storage whether iTmethods operates the infrastructure or you bring your own AWS or Azure account. Deployment options →

The hardening sheet

What Reign Ops applies on day one.

Identity boundary bound to your provider.

SAML or OIDC at the platform edge, single sign-on only, on the protocol you already run.

Allow-listing at both edges.

At the Bitbucket edge and at the edge of the Pipelines runners, so what can execute is bounded as tightly as who can sign in.

Pipelines runners isolated per environment.

Short-lived tokens, no long-lived registration secrets, and no shared execution surface between environments.

Audit log streamed to your SIEM.

Bitbucket audit logs go to the system your security team already watches rather than staying in a console.

AI coding tools governed at the call layer.

Atlassian Intelligence and the rest of the fleet route through Reign Gateway.

And six more.

Code scanningBranch protectionApproved-model registryData classificationEgress controlsBackup and disaster recovery

All twelve Bitbucket controls, with topology diagrams and sample policy excerpts. Bitbucket DC on Reign Ops hardening sheet →

The AI coding tools

Productivity multipliers, and the newest way code leaves.

Atlassian Intelligence, Copilot, Cursor, Claude Code and the rest of the coding-agent fleet read and write your Bitbucket code at machine pace. Reign Gateway governs them at the call layer.

The part worth being precise about. This governs the coding tools your own engineers run against Bitbucket, Atlassian Intelligence included, for calls sent through Reign Gateway. It is not a claim that those tools are safe, and it does not make an unapproved model approved. Beyond SOC 2 Type II for Reign Ops, no other certification or accreditation is claimed. What the boundary records → · How the boundary works → · Regulatory alignment →

Where Reign Factory fits

The same instance, with work arriving in it.

Reign Ops for Bitbucket Data Center is sold and operated on its own terms; a customer who never adopts Reign Factory loses nothing here. Reign Factory’s published integrations are GitHub, GitLab, Jira and Linear, with custom integrations available. What it is, and what it will not do →

Shared responsibility

What we run, what you run.

Scoped to Bitbucket Data Center and its Pipelines runners, and written down before anything is deployed, so the boundary is a document rather than a discovery.

Who	What they hold
Reign Ops (iTmethods engineers, 24×7)	Operate Bitbucket Data Center inside your authorization boundary. Enforce your identity provider at the platform edge. Run Bitbucket Pipelines runners isolated per environment with short-lived tokens and no long-lived registration. Stream the audit log to your SIEM. Patch Bitbucket Data Center and its Pipelines runners on a cadence matched to Atlassian’s releases.
Your team	Your Bitbucket repositories and the intellectual property in them. Code review, branch protection and push policy. The catalog of sanctioned AI coding tools, Atlassian Intelligence among them, and approval of new integrations and policy exceptions.
iTmethods onboarding and review team	Stand up the initial Bitbucket hardening configuration, operate the remediation path on what the review finds, and lead the periodic posture review with your risk, security and audit functions.

FAQ

Questions buyers ask

Is Bitbucket Data Center going away?

Not on Atlassian’s current plan: Atlassian says Bitbucket Data Center will not reach end of life. Its standalone license does have a date. Standalone Data Center licenses end on 28 March 2029, the day Jira, Confluence and Jira Service Management Data Center go read-only. After that date Atlassian sells Bitbucket Data Center only through the Bitbucket Hybrid License, and says an instance not moved to it switches to read-only and users can no longer push code. Atlassian says existing customers can upgrade to the Hybrid License in early 2027, with the exact date to follow. Confirm your position with Atlassian before you plan against it. The full Atlassian timeline →

What if we already run the rest of Atlassian?

Bitbucket Data Center runs under the same operating model as the rest of the estate we manage, so source control sits next to the tracker rather than away from it. What happens to the products that do have a read-only date is a separate conversation, and there is a page for it. The Atlassian Data Center path →

Does Atlassian Intelligence still work?

Yes, and it routes through Reign Gateway at the call layer along with every other coding agent your engineers use. You author the catalog of what is sanctioned; the boundary enforces it and records what each call asked for, what applied to it and what came back.