Atlassian Kept One Product Self-Managed. It's Not Jira or Confluence.
Every other Data Center product goes read-only on March 28, 2029. Bitbucket Data Center doesn't. Atlassian's own Hybrid License page says why: enough customers refused to move source code off-premises that Atlassian built around it. So what does that say about the Jira, Confluence, and Jira Service Management data you keep in the same building?
What Atlassian Actually Wrote
Straight from Atlassian's Bitbucket Hybrid License page, word for word:
“Bitbucket Data Center will not end of life.”
“Access to both Bitbucket Data Center and Bitbucket Cloud.”
“Offered to existing Bitbucket Data Center and Bitbucket Server customers only.”
“After March 28, 2029, Bitbucket Data Center will be sold exclusively through the Bitbucket Hybrid License.”
Atlassian's Marketplace ecosystem post (September 8, 2025) makes the same carve-out on the app side: Bitbucket Data Center apps “will continue to be available and supported in the Atlassian Marketplace.”
The Hybrid License, Fact by Fact
Check these against the source page yourself. We'd rather you catch us wrong than take our word for it.
| What | Status |
|---|---|
| Every other Data Center product | Goes read-only 28 Mar 2029 |
| Bitbucket Data Center | “Will not end of life” — no date set |
| Bitbucket Hybrid License availability | Mid-2026 (per Atlassian) |
| Eligibility | Existing Bitbucket Data Center / Server customers only |
| Pricing | Not published |
Source Code Got an Exception. Nothing Else Did.
Atlassian's whole cloud pitch assumes self-managed hosting is a relic nobody serious still needs. Then it turned around and built a permanent self-managed product, in Atlassian's own words, because a chunk of its customer base wouldn't put source code on somebody else's servers.
If source code is sensitive enough to earn a permanent exception, what makes the incident data sitting in your service desk, the customer records in your issue tracker, or the contents of your wiki any different?
Where This Argument Runs Out
Three caveats worth knowing before you use this argument yourself:
Atlassian hasn't reversed its cloud strategy. This is one narrow exception, carved out for one product, for one stated reason.
The Hybrid License is open to existing Bitbucket Data Center and Server customers only. If you've already migrated off, it isn't a way back.
There's no published price. The license opens mid-2026 by Atlassian's own timeline, and it could easily cost more than a Data Center subscription does now.
Bitbucket Got the Exception. Now Price the Rest.
See what a self-managed alternative actually costs against your real Jira, Confluence, and Data Center footprint.
Size My InstanceRelated Reading
- Your code can stay on-prem. Your build can't — the Bitbucket/Bamboo CI gap →
- The Data Center end-of-life countdown, and what it means depending on your status →
- How to opt out of Atlassian training AI on your Jira and Confluence data →
- The migration gotchas that lock teams into Jira — and a 2-minute lock-in audit →
- What Jira, Confluence, and Data Center actually cost a 100-person team →
Sources
- Bitbucket Hybrid License — Atlassian
- From Data Center to Cloud: the next chapter for Marketplace apps — Atlassian
Compiled August 2026 from Atlassian's own Bitbucket Hybrid License and Marketplace ecosystem pages. No Hybrid License pricing has been published as of this writing; re-check when it does, and verify current terms at atlassian.com before making decisions based on this page.