Ask your three biggest cloud vendors: “Is our customer data sovereign?” All three will say yes. All three mean something different.
Since January, “sovereign cloud” is the loudest word in European IT. AWS opened a separate cloud in Germany – run only by EU staff, physically and logically cut off from its US regions (GA since January 15, 2026, first region Brandenburg). Here is what the three big MarTech vendors actually offer on top of it.
Three vendors, three promises
- Adobe put its content platform (AEM Managed Services) on the new AWS European Sovereign Cloud, plus Microsoft Cloud for Sovereignty in the Netherlands. But the customer-profile platform behind it – AEP – runs multi-cloud in standard regions (six Azure regions plus one AWS, fixed at provisioning) with a global Edge Network. Profile data is resident; edge routing is not. Your data sits in Europe – it isn’t sealed there.
- Salesforce sells the Hyperforce EU Operating Zone: EU data boundary, EU-based 24/7 support, paid extra. Read the product list closely – it covers a vetted subset (Sales, Service, Analytics, Platform and others). Check whether your Marketing Cloud SKU made the list. Forrester calls the EU OZ a “sticking-plaster solution” for sovereignty.
- Veeva keeps pharma data in European data centers (Germany, Ireland/UK, on AWS) by default, pinned to region, no extra fee. But European hosting by a US company isn’t sovereignty – US law can still reach it.
The three words that get conflated
- Residency = where data sits.
- Operating zone = who runs and supports it.
- Sovereignty = whose law can touch it.
The legal core
The US CLOUD Act can compel US providers to produce data stored abroad; GDPR Article 48 says foreign judgments alone are not a lawful transfer basis. That collision is why “hosted in Frankfurt” answers the residency question – not the sovereignty question. For DACH banks this now shows up in DORA/BaFin outsourcing questionnaires; for pharma, in EMA data-location clauses.
Questions to settle
- When the board asks “are we sovereign?”, does your answer have three columns – residency, operations, jurisdiction – per vendor and per product?
- Which products in your stack are actually covered by the sovereign offering – and which (often the marketing platform) are not?
- Has “sovereignty” reached your vendor questionnaires and renewal checklists yet?
- In most stacks the marketing platform holds the most customer data and offers the least sovereignty – does yours?
Frequently asked questions
What is the difference between data residency, operating zone and sovereignty?
Three different questions. Residency is where the data sits. Operating zone is who runs and supports it. Sovereignty is whose law can touch it. Hosted in Frankfurt answers the residency question and says nothing about the other two, which is why a sovereignty answer needs three columns per vendor and per product.
Is Adobe Experience Platform covered by the sovereign cloud offering?
Only in part. Adobe put its content platform, AEM Managed Services, on the AWS European Sovereign Cloud plus Microsoft Cloud for Sovereignty in the Netherlands. The customer-profile platform behind it, Adobe Experience Platform, runs multi-cloud in standard regions – six Azure regions plus one AWS, fixed at provisioning – with a global Edge Network. Profile data is resident; edge routing is not.
Why does hosting in Europe not equal sovereignty?
Because of a legal collision. The US CLOUD Act can compel US providers to produce data stored abroad, while GDPR Article 48 states that foreign judgments alone are not a lawful transfer basis. European hosting by a US company therefore answers where the data sits, not which law can reach it.
Three vendors, three different promises behind one word. If you have to answer this in a procurement questionnaire or a DPIA, the differences matter more than the label – I help teams write that answer down.
Get in touch →Sources: AWS European Sovereign Cloud launch announcement; Adobe blog on AEM with the AWS European Sovereign Cloud; Adobe Experience Platform multi-cloud documentation; Salesforce Hyperforce EU Operating Zone product page; Veeva cloud infrastructure page – as of August 2026. All product names are trademarks of their respective owners. This is an independent analysis; no partnership with or endorsement by any vendor. First published as part of my LinkedIn series, August 2026.
