Atlassian closed fiscal 2026 on June 30 with $6.57 billion in revenue, 26% growth and an 85% GAAP gross margin. It also runs customer data residency in eleven separate geographies, on every paid cloud tier, at no extra charge. Those two facts sitting next to each other are the most useful thing a SaaS operator can stare at this quarter, because the old assumption that regional hosting wrecks your unit economics is about to be stress tested by every enterprise buyer in Europe.
Data residency stopped being a security questionnaire checkbox somewhere in the last eighteen months. It is now a gate on enterprise deals, a tier boundary in pricing pages, and in a few cases a genuine moat.
Europe’s sovereign cloud bill nearly doubled in a year
European organizations are on track to spend $12.6 billion on sovereign cloud infrastructure as a service in 2026, up from $6.9 billion in 2025. That 83% jump comes from a Gartner forecast published in February 2026, which puts worldwide sovereign cloud IaaS spending at $80.4 billion this year, a 35.6% increase over 2025, rising to $110 billion in 2027. Europe is the fastest-moving major region. Gartner expects European spending to hit $23.1 billion in 2027 and pass North America’s $21.1 billion for the first time.
The demand does not come from nowhere. Synergy Research put European cloud providers at 15% of their own home market as of mid-2025, down from 29% in 2017, with Amazon, Microsoft and Google holding roughly 70% between them. European buyers noticed. Forrester now forecasts European tech spending above 1.5 trillion euros in 2026, growing 6.3%, with software investment up 11% and sovereignty named as one of the defining themes of the year.
Two deadlines land before most 2027 renewal cycles close
The first is fixed. The EU Data Act became applicable on September 12, 2025, and its switching provisions apply to software as a service, not just infrastructure. From January 12, 2027, providers can no longer charge switching fees at all. In the interim, any charge is capped at the costs the provider directly incurs. Customers get a notice period of no more than two months and a transition window of up to 30 days.
Read that as a SaaS operator rather than a lawyer and the picture sharpens. Egress and migration charges disappear as a retention mechanism for anyone selling into the EU. That cuts both ways: it lowers the cost for your prospects to leave an incumbent, and it lowers the cost for your customers to leave you. Vendors whose renewal rates quietly depend on data extraction friction have about four months to find a better reason for customers to stay. Vendors who compete on switching ease just had a regulator hand them a wedge.
The second deadline is still moving. The European Commission tabled the Cloud and AI Development Act in June 2026, proposing at least a tripling of EU data centre capacity over five to seven years and a four-level sovereignty framework. Level 1 requires processing and storage in Union infrastructure. Level 3 adds EU ownership and control criteria including personnel citizenship. Level 4 demands full transparency over the software supply chain with no third-country interference. Reception has been mixed: CCIA Europe called the requirements discriminatory while German vendor Nextcloud argued the act is not ambitious enough. Either way, a four-level label is coming, and procurement teams will ask which level you clear long before the text is final. If your trust stack has no answer, that is a gap worth closing this year.
The hyperscalers already repriced their answer
AWS launched its European Sovereign Cloud on January 15, 2026, with an initial region in Brandenburg, Germany, and more than 90 services available at launch. The investment figure is over 7.8 billion euros, with sovereign Local Zones planned for Belgium, the Netherlands and Portugal. The governance structure matters more than the capex: a separate European parent company, three German subsidiaries, EU-citizen leadership, and an advisory board with two independent European members.
Microsoft has been building the same argument. In an April 2026 update on its European commitments, the company said it plans a 40% increase in European datacenter capacity, targeting 200 datacenters across 16 European countries by 2027, alongside new cloud regions in Austria, Denmark and Belgium.
For a SaaS company, this is the good news buried in the sovereignty story. The regional footprint your buyers want already exists as a managed primitive. Nobody is asking you to build a datacenter. They are asking you to deploy cleanly into one.
Two ways SaaS vendors are pricing residency right now
Notion took the tier-gate approach. It opened EU data residency in Frankfurt in 2025 and added Tokyo, Osaka and Seoul in May 2026. The feature is available to Enterprise plan customers only. Figma made the same call: EU hosting is Enterprise-only, primary in Frankfurt with backup in Dublin, and Volkswagen Group is the named reference customer. Figma has since extended localized hosting to Australia, India and Brazil, still on Enterprise.
Atlassian went the other direction. Data residency is available across eleven geographies, covering the US, EU, Germany, UK, Switzerland, Canada, Australia, Singapore, Japan, India and South Korea, and it is native to Standard and Premium as well as Enterprise. The company states plainly that it will not raise Standard or Premium prices as a result.
Both are defensible, and the choice says something about where your growth comes from. Gating residency to Enterprise converts a compliance requirement into an upgrade trigger, which is efficient when your ACV ladder has a steep top rung. Making it native to every paid tier removes an objection from mid-market deals you would otherwise lose to a local competitor, which matters more when your growth depends on volume rather than a handful of seven-figure contracts. The mistake is picking neither and shipping residency as an unpriced side project.
What a region actually costs
Start with the baseline. SaaS Capital surveyed more than 1,000 private B2B SaaS companies in March 2026 and found median hosting spend at 5% of ARR, DevOps at 4%, and total cost of revenue at 17% of ARR, with R&D at 22%. A second region does not double the 5%. Compute and storage scale with the workload you move, not with the number of regions on the map. What actually inflates is the fixed overhead layered on top: duplicate observability, duplicate CI and deploy pipelines, duplicate on-call rotations, and a second set of everything auditors want to see.
The engineering bill is where the real number sits. Notion’s platform team described building region-specific data lakes, per-region Elasticsearch clusters, regional vector databases and embedding pipelines, and region-aware event logging so that all processing and storage for a workspace stays inside one network boundary. The EU deployment took months, and the team’s stated goal is to get new regions down to days. That is the honest shape of the work. Your primary Postgres is the easy part. Your analytics warehouse, your search index, your AI features and your event pipeline are the parts that quietly assume one global namespace.
Atlassian’s 85% GAAP gross margin against eleven live regions is the counterweight. Regional hosting is a fixed-cost problem you amortize, not a variable-cost problem that compounds. It is a different animal from the inference costs currently compressing AI-heavy SaaS margins, which scale with every query.
Selective residency is the pattern that keeps the math workable
Most vendors shipping residency in 2026 are not replicating the whole application. They are splitting it. In a January 2026 breakdown, WorkOS described the split most teams land on: customer content, processing and inference stay in region, while authentication, account metadata, billing and telemetry route globally. Slack, Airtable, GitHub and OpenAI have all shipped versions of it, and WorkOS notes Slack’s team spent close to two years on the work.
Two caveats a vendor pitch will not give you. First, selective residency satisfies the pragmatic majority of buyers but not all of them. Financial institutions, government contractors and organizations operating under a strict post-Schrems II reading will insist that authentication stays local too, and you will lose those deals unless you build a full-stack regional deployment. Second, residency has a performance cost. Atlassian’s own documentation warns that enabling it “may lead to slower overall performance for users located outside of the designated geographic area.” A German multinational that pins to Frankfurt is making a latency decision for its Singapore office, and someone should say that during the sales cycle rather than after go-live. Teams with a mature internal platform absorb this far better than teams treating each region as a bespoke deployment.
The public sector is the leading indicator
Government buyers move first on sovereignty and enterprise buyers follow, so the migrations already on record are worth tracking. The Register catalogued several in December 2025: Austria’s Federal Ministry for Economy, Energy and Tourism moved 1,200 employees to Nextcloud in four months, the International Criminal Court in The Hague replaced Microsoft office software with the German open-source suite OpenDesk in November 2025, and Schleswig-Holstein has been migrating 30,000 civil servants to open-source tooling since 2024.
None of that means US SaaS is losing Europe. Forrester’s 2026 European predictions, published in October 2025, state flatly that no European enterprise will shift entirely away from US hyperscalers this year, and Gartner’s read is that roughly 20% of workloads move to local providers by 2029. That is a reallocation, not an exodus, and it rewards whichever vendors do the regional work first.
What to do before January 12
Four things belong on the roadmap this quarter. Audit your switching terms against the Data Act, because any egress or migration charge you bill an EU customer becomes unenforceable in January and you would rather reprice it deliberately than discover it mid-renewal. Instrument lost-deal reasons for residency specifically, since most CRMs bury it under a generic security objection and you cannot size what you do not count. Decide the tier boundary before engineering ships the feature, because retrofitting a price to a shipped capability is the hardest pricing change there is. And build the second region as a template, since the gap between Notion’s months and its target of days is entirely whether the first region was built to be copied.
Frequently asked questions
What is data residency in SaaS, and how is it different from data sovereignty?
Data residency is the physical location where customer data is stored and processed. Data sovereignty is the broader question of which legal jurisdiction can compel access to that data, regardless of location. A US vendor can store EU customer data in Frankfurt and still fall short of a sovereignty requirement, because the parent company remains subject to US law. That gap is exactly what the European Commission’s proposed Cloud and AI Development Act tries to codify, with residency sitting at Level 1 of its four-level framework and full supply-chain independence at Level 4.
Should we charge extra for data residency or include it in every paid plan?
It depends on where your revenue concentration sits. Notion and Figma restrict data residency to Enterprise, which turns a compliance requirement into a clean upgrade trigger and works well when large contracts drive most of your ARR. Atlassian made residency native across Standard, Premium and Enterprise in eleven geographies and publicly committed to no price increase, which removes an objection from mid-market deals. Volume-led businesses generally do better including it. What fails is shipping residency with no pricing decision attached at all.
How much does adding a second region cost a SaaS company?
Less in infrastructure than most teams expect, and more in engineering. SaaS Capital’s March 2026 survey of over 1,000 private B2B SaaS companies puts median hosting at 5% of ARR and total cost of revenue at 17%. Compute scales with workload, not with region count. The real spend is duplicating the systems that assume one global namespace: analytics pipelines, search indexes, vector databases, event logging and observability. Notion’s EU build took months. Atlassian holds an 85% GAAP gross margin while running eleven regions, so the amortized economics work.
Does the EU Data Act apply to SaaS or only to cloud infrastructure providers?
It applies to SaaS. The Data Act’s switching provisions cover providers of data processing services, a definition that explicitly includes infrastructure, platform and software as a service, plus newer variants like database as a service. The regulation became applicable on September 12, 2025. From January 12, 2027, switching charges are prohibited outright, and until then they cannot exceed directly incurred costs. Customers can give up to two months of notice and must be able to complete the transfer within a 30-day transition window.
Is sovereignty demand actually costing US SaaS vendors European revenue?
Not in aggregate, and the framing of an exodus does not survive the data. Forrester predicted in October 2025 that no European enterprise would move entirely off US hyperscalers during 2026, and Gartner’s estimate is that about 20% of workloads shift to local providers by 2029. Meanwhile European sovereign cloud IaaS spending grows 83% this year to $12.6 billion. The revenue is not leaving the category. It is moving toward whichever vendors can prove regional processing, and that includes US vendors who built the capability early.
The competitive read
Vendors treating residency as a cost centre will spend the same engineering months as vendors treating it as a product line, and only one group will price it. That is the whole argument. European sovereign cloud spending nearly doubled in twelve months, a switching-fee ban lands in January, and a four-level sovereignty label is moving through Brussels. Each of those becomes a question an enterprise buyer asks on a discovery call within two quarters.
The regional footprint already exists in AWS Brandenburg and Microsoft’s 200 planned European datacenters. The architecture is documented and in production at Slack, GitHub, Notion and Atlassian. What is left is a packaging decision and a roadmap slot, and the vendors who make both this quarter will be quoting a residency SKU while competitors are still writing security questionnaire responses.
