2025 was an impactful year for Bitbucket Cloud. As we enter 2026, Bitbucket will be continuing this momentum by making architectural improvements aimed at two goals: improving scalability and resiliency, and laying the foundation for Bitbucket Cloud data residency, starting with the European Union in December 2026 and India in June 2027.
What does this mean for you? We are bringing data residency to our EU and India-based customers so they can choose where their source code and other Bitbucket data resides. To do this, we’ll be making a number of behind-the-scenes changes. These changes will be largely invisible, but in some cases they will manifest in the Bitbucket Cloud in-app experience and our REST API. We want you to have a clear picture of what’s coming and why.
Moving to a multi-region platform
One of the clearest signals we’ve heard from regulated and public sector customers is that data residency matters. You need not only the the ability to control where your data lives, but also the confidence that it stays within a region for compliance and governance reasons.
Further, we know that some some Bitbucket customers have experienced unexpected outages during periods of high website or Git filesystem load. Those events underscored that we need a stronger foundation for the future of Bitbucket Cloud, and they have directly informed the changes we’re making now.
To prepare us for the future, we’re restructuring Bitbucket’s architecture so core services can run and scale independently in multiple regions. This will have a couple of key benefits:
- For all customers, the new architecture improves isolation between customers, reducing impact of a noisy neighbor, or issues impacting a single shard or region.
- For customers who need data residency, we will unlock the ability to choose to store Bitbucket data in specific regions outside of the United States, starting with EU (AWS eu-central-1), by the end of calendar 2026 and India by the end of June 2027.
Data in scope will include user generated artifacts (e.g. source code, pull requests, and repository metadata). We will be able to share additional details in the coming months so stay tuned.
The architectural changes described below are a key part of making this possible.
Customer data is scoped to a workspace
Bitbucket has historically allowed a number of operations across workspaces. To support our goals of customer isolation, resiliency, and data residency, we will be dropping support for all cross-workspace API requests. As a result, we’ll be able to:
- Keep each customer’s data clearly scoped to a single region.
- Reason about access patterns and compliance boundaries.
- Scale and isolate workspaces in the way we need for resiliency.
While the vast majority of our customers work in a single workspace, those that use multiple workspaces will notice this change in two key areas.
1. Cross-workspace forking won’t be possible
Historically, Bitbucket has supported forking a repository into another workspace. While the majority of our customers explicitly prohibit this via workspace controls and instead use branching, some customers do use this collaboration model.
To make multi-region support possible, we will be dropping support for cross-workspace forks effective July 1, 2026. If you currently rely on this workflow, you can read more about the details of these changes on the Community post here.
2. Re-scoping API endpoints to a single workspace
In keeping with the above changes, last year we announced the deprecation of cross-workspace REST API endpoints. Effective Mar 31, 2026 we will be permanently removing these endpoints.
If you’ve built applications or automations that rely on any cross-workspace endpoints, you should immediately to update your implementation. All of these endpoints have workspace-scoped equivalents that will remain supported in the future.
Where to learn more and get help
We’ll keep sharing updates on this journey through a few key places:
- Bitbucket Cloud documentation – for the latest details on workspace-scoped behavior, API changes, and platform deprecations (accessible from the Bitbucket “Help” menu).
- Atlassian Community – for announcements, FAQs, and to ask questions or share feedback with the Bitbucket team and other customers.
- In-product notices and emails – for change-specific updates that affect your workspaces, repositories, or apps.
Follow along on our journey to making Bitbucket Cloud better, more resilient, and available in more regions!