GUIDE · DEFINITION

What sovereign cloud is (and what it is not)

“Sovereign cloud” is the phrase of the moment, and like all phrases of the moment it gets misused. Here is the operational definition: the three requirements without which it is just marketing, why the giants' ”European cloud” is not enough, and who really needs it.

Updated September 2026
6 min read
Altovar Technical Editorial Team

The operational definition: three requirements

A cloud is sovereign when, simultaneously:

  1. The data sits in EU data centres — not ”European replicas” of a system born elsewhere, but the complete path: processing, backups, replication.
  2. The provider is subject to European law — European company, European contracts, European jurisdiction. If an extra-European parent company sits above the provider, the chain breaks.
  3. There are no extra-EU transfers — not for backups, not for support, not for ”technical reasons” buried in the terms.

Missing one of the three and you are not talking about sovereignty: you are talking about hosting with a European flag. The difference is not aesthetic — it is the difference between being able to prove it at an audit and only being able to say it on the site.

Why the giants' ”European region” is not enough

The point is the CLOUD Act: US law lets American authorities request data held by US providers, even when the servers are physically in Europe. In practice, who controls the provider matters more than where the server sits. It is why Europe has launched sovereign projects and why NIS2 and DORA insist on supply chain and jurisdiction: the audit's question is not ”where is your data” but ”who can reach it, holding which law”.

Who really needs it

  • NIS2 and DORA entities — by obligation, with evidence to show instead of reconstructing.
  • Public administration and its suppliers — where the EU perimeter is often a tender requirement.
  • Companies with sensitive customer data — professional firms, healthcare, finance: the reputational damage of leaked data is not covered by any contract.
  • Anyone simply removing risk — you do not need to be regulated to prefer that your contracts do not travel under a law you cannot read.

The checklist when a provider says ”sovereign”

  1. Where are all the data centres, including backup and disaster recovery?
  2. Is the company invoicing you European? And the parent company?
  3. Where are the support teams that can access your systems?
  4. What does the contract say about transfers and sub-processors?
  5. Which logs and evidence does it provide for the audit?

If the provider answers vaguely to any of these, you have your answer. We answer all of them on the Altovar sovereign cloud page — machines, storage and backup in the EU, with evidence ready.

Frequently asked

Is it the same as private cloud?

No. Private cloud is yours (on-premise or dedicated); sovereign cloud can be public and shared — what counts is the legal perimeter. The two combine: our cloud also offers single-tenant options for those wanting both.

If we are already GDPR-compliant, do we need this?

GDPR governs personal data; NIS2 and DORA look at infrastructure and the supply chain. They overlap but do not coincide: you can be GDPR-compliant on a cloud that an NIS2 audit calls into question.

Does it cost more?

Not per se: machine prices are comparable. You pay for the same compute with a different legal perimeter — and in some cases (lean sovereign providers) you even pay less than the giants.

About this content

General informational guide. Regulations and technical requirements change over time: always check the official sources and assess your specific case with a qualified technical or legal advisor.

GET IN TOUCH

Talk to our team.

We'll show how Altovar integrates into your infrastructure. No commitment, no sales pitch. Just a technical conversation.

BOOK A DEMO →