Digital sovereignty is not a property a cloud either has or lacks. It is a control boundary that an organisation draws for each workload, and its cost can only be stated control by control. You can keep data in Germany and still depend entirely on the provider to operate it; you can choose a European operator and still build on proprietary services that are expensive to replace.
This guide is the starting point for Costfluent's sovereignty articles. It breaks the label into five kinds of evidence, attaches the cost categories each one creates, separates legal duty from internal preference, and ends with a decision path for each workload. The linked articles go deeper into individual providers and rules; the section "Articles in this series" says when each one is worth reading.
Five kinds of evidence instead of one label
A procurement exercise that asks only for "sovereign" options returns offers that cannot be compared and may pay for measures unrelated to the actual risk. It is more useful to define sovereignty through evidence a supplier can produce and a buyer can check.
Company and jurisdiction
Which legal entity signs the contract, which group does it belong to, which law governs the contract, and which subprocessors take part in operations, support or billing? The answers determine which legal systems can reach the actual service. The US CLOUD Act of 2018 is the best-known example of the question whether a provider can be compelled to produce data it stores outside the United States. Whether that question matters for a given service, and which safeguards are enough, is for legal and privacy owners to decide; the data-centre location does not answer it.
Access and operations
Who administers the service, who holds the keys, and who can intervene during an incident? Is there support access from outside the chosen jurisdiction, and is it logged and approved? Could your own staff or another operator keep the service running? This level is about people, process and privileged access, not buildings.
Processing location
Where are content, backups, logs and telemetry, support cases and billing data stored and processed? Choosing a region usually answers only the first item. Microsoft's EU Data Boundary documentation, for example, states that Customer Data and pseudonymised personal data are stored and processed in EU and EFTA countries, and in the same place lists limited circumstances in which data continues to be transferred outside that boundary. Those exceptions belong in your review.
Portability and exit
Can data, configuration and workloads be exported in a usable form and run elsewhere? How many proprietary APIs, identity models and managed services would need replacing? A theoretical export without a tested recovery gives you little practical control.
Product boundary
What can the service reach at all? A tool with read access to billing data touches different data from a service that runs your databases. In the other direction, a provider's separate offering often does not carry the full service catalogue. The product boundary tells you which data a supplier cannot reach and which services are missing in the chosen model, and so where replacement work and extra cost appear.
The EU Cloud Sovereignty Framework as shared vocabulary
In October 2025 the European Commission published a Cloud Sovereignty Framework, version 1.2.1. It was written for a Commission procurement procedure and defines eight objectives: strategic sovereignty, legal and jurisdictional sovereignty, data and AI sovereignty, operational sovereignty, supply chain sovereignty, technology sovereignty, security and compliance sovereignty, and environmental sustainability.
For each objective, the tender sets a minimum Sovereignty Effectiveness Assurance Level (SEAL), from 0, "No Sovereignty", to 4, "Full Digital Sovereignty". A tender that does not reach the required minimum consistently across all objectives is rejected. The Commission also computes a weighted score: supply chain carries the most weight at 20 percent, while legal and security count 10 percent each, because the procedure already covers those areas through other safeguards.
For a small company the framework is not mandatory, but it is a practical checklist. It forces you to assess each objective separately rather than buying an overall verdict. Know its limits: no certificate exists for it, the buyer sets the level it needs, and a supplier's self-assessment is a statement you check against evidence.
The sovereignty matrix
This matrix links each control to what it buys, the costs it typically creates, and a question that demands evidence rather than assurance.
| Control | What it buys | Typical costs | Evidence question |
|---|---|---|---|
| jurisdiction and contract | clearer accountability, assessed access and transfer risk | contract review, transfer assessment, a narrower supplier pool, possibly a premium for a separate offering | Which entities, subprocessors and legal systems touch the actual service? |
| access and operations | control over administrators, keys and support paths | own key management, on-call capacity, approval processes, less automation | Can the designated operator resolve a critical incident without unapproved access? |
| processing location | control over storage and processing locations | regional price differences, separate backups, narrower service choice, classification work | Are primary data, backups, logs, telemetry and support paths all named? |
| portability and exit | a credible exit and negotiating position | portable architecture, duplicate skills, export tests, parallel running, forgoing proprietary advantages | Has a bounded workload actually been restored elsewhere with its data and identities? |
| product boundary | knowing which data a service reaches and which services are missing | replacement services, integration work, extra operations | Which services does the target model lack, and what does replacing them cost over three years? |
| cost sovereignty | your own cost history as the basis for decisions | billing export, retention, schema maintenance, reconciliation, access control | Can you analyse cost, price, allocation and commitments without the current portal? |
Not every workload needs every control. A public marketing site and a regulated core system can have different profiles. The decision becomes economic only once protection need, control objective and full cost are explicit for each workload.
Where the cost actually appears
Price and region. Prices, services and discounts differ by region and offering. Compare the same architecture, the same cost basis (list price or effective cost after discounts) and the same period, not one headline rate.
Separate partition, separate bill. The AWS European Sovereign Cloud has been generally available since 14 January 2026, with its first region in Brandenburg, Germany. AWS describes it as a separate partition with its own IAM and billing system, and accounts have to be created there from scratch. Beyond any price difference, that means new accounts, a second source of cost data, and open questions about existing commitments.
Capability gaps. A separate or locally operated model may offer fewer services, regions or integrations. Microsoft itself states that Azure Local and private clouds provide the strongest sovereignty controls but do not deliver the full cloud value in cost-effectiveness, scalability and pace of innovation, and it points to per-country service matrices for its National Partner Clouds. Every gap becomes a replacement service or in-house development.
Migration and parallel running. Data movement, replatforming, testing and a controlled transition consume time and duplicate infrastructure. An exit strategy with no time or capacity budget is only documentation.
Skills. Portability needs people who know the target platform, automation and recovery. A second platform nobody uses regularly decays.
Control evidence. Contract review, assurance reports, key processes and supplier oversight create recurring work. A BSI C5 attestation describes a cloud service's control system; the BSI stresses that customers must check whether that baseline is sufficient for their own use case.
Opportunity cost. Avoiding a managed service moves development, operations and risk to your team. Include that labour even though it never appears on a cloud bill.
Offering types and their cost questions
Offerings can be grouped by how they are built. The construction, not the label, decides which cost category dominates.
| Type | Example | Dominant cost question |
|---|---|---|
| EU region of a hyperscaler | a region in Frankfurt or Ireland, possibly with the EU Data Boundary | Which data and support paths still leave the region, and what do added controls such as customer-held keys cost? |
| separate EU partition | AWS European Sovereign Cloud | What do new accounts, identities, contracts and a second bill cost, and which services are missing? |
| hyperscaler controls and partner operation | Microsoft Sovereign Public Cloud, National Partner Clouds | Which controls can be added, which services does the partner offer, and who operates what? |
| European provider | a provider headquartered and operating in the EU | Which services are missing compared with your current stack, and what does migration cost? |
| private or on-premises | Azure Local in your own data centre | Who carries hardware, operations and outage risk, and which cloud advantages disappear? |
None of this produces a ranking. The same type can fit one workload and be too expensive for the next.
Duty or preference: what regulation actually requires
Regulation calls for an assessment within a defined scope, not a slogan. The table shows what each source contributes to the cost question.
| Source | Who it applies to | What it means for cost planning |
|---|---|---|
| GDPR, Chapter V | controllers and processors transferring personal data to third countries | transfers are lawful only under that chapter's conditions; this requires assessment and documentation, not a blanket rule to use a domestic provider |
| DORA, Article 28 | financial entities in scope, applicable since 17 January 2025 | exit strategies and documented exit plans are mandatory for ICT services that support critical or important functions |
| NIS2, Article 21; in Germany section 30 BSIG | essential and important entities | risk-management measures such as backup management, disaster recovery, supply chain security and cryptography become budget lines |
| EU Data Act, Articles 25, 29 and 34 | providers and customers of data processing services | notice to start switching at most two months, a transition of normally at most 30 calendar days (up to seven months where that is technically unfeasible, and the customer may extend it once), data retrieval for at least 30 calendar days; no switching charges for the switching process from 12 January 2027 |
| BSI C5 | cloud providers presenting an attestation and customers assessing it | an audit report on the provider's controls, not a verdict on your configuration |
Two details of the Data Act prevent expensive assumptions. Until 12 January 2027, reduced switching charges may not exceed the provider's costs directly linked to the switch. When services are used in parallel, providers may still charge for data egress, but only to pass on the egress costs they incur. Your own migration work, testing and parallel running remain your cost either way.
UK organisations. GDPR Chapter V, DORA, NIS2 and the Data Act are EU instruments. In the UK, transfers fall under UK GDPR and the ICO's guidance on restricted transfers, and network security duties under the Network and Information Systems Regulations 2018. For a group with EU and UK entities, its legal owners assess the workload under both regimes; a shared European architecture does not make the legal scope identical.
Ask legal, privacy, security and risk owners to decide which duty applies to the actual workload and what evidence is enough. FinOps then turns the chosen measure into a budget, a cost basis and an ongoing owner.
Cost sovereignty: the data about your cloud
Billing data records what the organisation paid for and the basis on which it committed spend. If it lives only in a provider portal, a contract change, an expiring retention period or a permission change removes part of the decision history, usually at exactly the moment a switch is on the table.
A durable cost record includes:
- raw billing exports and their schema information;
- price, discount and commitment context;
- billing and reporting currency, with the exchange-rate source;
- allocation rules with effective dates;
- reconciled reports and open differences;
- a tested export with clear retention and access controls.
The FOCUS specification is at version 1.4, and AWS, Microsoft and Google Cloud are among the providers that document FOCUS datasets. FOCUS standardises cost fields across sources; it does not make different products, contracts or levels of detail identical. Keep the provider-specific fields you need for reconciliation or migration as well. The FOCUS glossary entry separates the standard from the source data.
A decision path for each workload
- State the protection need. Data categories, criticality, users and the operational impact of an outage. Output: one row in a workload register.
- Separate duty from preference. What follows from law, contract or customer requirement, and what is an internal risk choice? Output: a list of duties confirmed by legal.
- Choose the control objective. Jurisdiction, access, processing location, portability or a combination, optionally mapped to the eight objectives of the EU framework.
- Scope options equally. Same workload, availability, cost basis and period, with today's setup as one of the options.
- Capture full cost. Provider charges plus migration, operations, skills, evidence, replacement services and exit readiness, at least over the contract term.
- Define proof. Document, technical control, recovery test or independent report, for each control.
- Assign owner and budget. Who owns cost and control in operation, and in which cost report do they appear?
- Set a review date. Offerings, law and architecture change; the Data Act date of 12 January 2027 is an obvious trigger.
Common mistakes
- Equating a region with sovereignty. A region settles where primary data is stored, not support, telemetry, keys or the contracting entity.
- Buying an overall verdict. An offering can be strong on processing location and weak on portability; the EU framework scores each objective separately.
- Comparing list prices and missing gaps. Missing services and extra operations easily outweigh any per-instance price difference.
- Never rehearsing the exit. Without a recovery test, nobody knows whether export and identities actually work.
- Forgetting the cost data. Without comparable history after a move, you can show neither success nor additional cost.
- Reading an attestation as approval. C5 or any other report describes the provider, not your configuration or your regulatory scope.
Limits of this framework
The matrix organises costs; it does not quantify them. Prices, service catalogues and contract terms change, and a real comparison needs your own architecture and billing data. It replaces neither a legal assessment, a data protection impact assessment nor a procurement review. Statements about providers reflect their own documentation on the date checked.
Further reading
- Sovereignty cost criteria for German offerings: useful once concrete offers are on the table and you need seven cost criteria with a way to check each.
- DORA cloud costs: for financial entities and their ICT suppliers who have to budget the register, exit plans and tests.
- NIS2 cloud cost: for entities in NIS2 scope that need to plan each required measure as a budget line.
- AWS data transfer costs: when parallel running or data repatriation is planned and you need to read transfer lines on the bill.
What Costfluent covers
Costfluent is cloud cost management software, not a cloud offering, and it does not change where your workloads run. It covers the cost-sovereignty side: AWS, Azure and Google Cloud connect through native billing connectors with read-only access that you can revoke in the provider at any time, and Kubernetes through an agent in the cluster. Costs are presented in euros or another presentation currency, with the original currency retained. Cost reports export as CSV, and on every plan, Free included, the Public API reads the same data from your own tools. File imports for further billing formats are Planned. How Costfluent evidences sovereignty for itself, covering the company, core services in Germany, access, portability, the exceptions, and a self-assessment against the EU framework, is on the digital sovereignty page; controls and data access are on the security page.
Sources and method
Checked on 2026-10-10. European Commission Cloud Sovereignty Framework, version 1.2.1; EU Data Act, Regulation (EU) 2023/2854; DORA, Regulation (EU) 2022/2554; NIS2, Directive (EU) 2022/2555; GDPR, Regulation (EU) 2016/679; section 30 BSIG; Network and Information Systems Regulations 2018; ICO International transfers; BSI C5 criteria catalogue; Bitkom Cloud-Souveränität praktisch umsetzen; AWS Opening the AWS European Sovereign Cloud; Microsoft What is Microsoft Sovereign Cloud? and What is the EU Data Boundary?; U.S. Department of Justice CLOUD Act Resources and The Purpose and Impact of the CLOUD Act; FinOps Foundation™ FOCUS Specification. The evidence types, matrix, offering-type table and decision path are Costfluent recommendations, not legal advice.



