Common usage calls a hyperscaler a cloud provider on a global scale, which operates regions on several continents and offers an extensive catalogue of services, and a sovereign cloud an offering that highlights guarantees on where the data reside, on the law to which the provider is subject and on control of operations. The question “sovereign cloud or hyperscaler” therefore sets two words of common usage against each other: “sovereign” has no single definition, and very different offerings claim it.
The label is not enough to choose. The choice is made by data class, on four criteria the buyer can check: the law applicable to the data, the qualification of the service, the breadth of the catalogue and reversibility. It is not binary: an organisation can place its most sensitive data on a qualified service and the rest with a global provider, and some offerings themselves combine the two worlds. No provider is named in this article: an offering is judged at the date of the decision, with the documents in hand.
The grid for comparing sovereign cloud or hyperscaler
| Criterion | Qualified or so-called sovereign offering | Global provider’s offering | What is authoritative |
|---|---|---|---|
| Law applicable to the data | It may highlight a provider subject to European law alone: a claim to be checked | The provider or its parent company may fall under the law of a third country; the reach of that law over data stored in Europe is to be analysed | The lawyers’ analysis, based on the contract and the provider’s structure |
| Qualification | Qualified if the service appears on the ANSSI list; the word “sovereign” alone establishes no qualification | Same rule, service by service | The list published by ANSSI, at the date of the decision |
| Service catalogue | The qualified scope may cover only part of the services offered | Extensive catalogue; a provider-specific service, once adopted, can increase dependency | The inventory of services the application uses |
| Reversibility | Depending on formats, provider-specific services and clauses | Depending on the same elements | A data return test |
The two central columns describe families and do not apply to any offering in particular.
The grid is read together with the data classification. When a text, a doctrine or the organisation’s security policy requires a qualification, the class concerned goes on a qualified service. For the other classes, the catalogue and geographical presence may decide.
Applicable law is not read from the data centre’s address
Storage location and applicable law are two separate questions. Our entry on the Cloud Act gives an example. This United States federal law, enacted on 23 March 2018, covers data that a provider has in its possession, custody or control, whether or not they are located in the United States. The United States Department of Justice specifies that the provider must be subject to US jurisdiction. Whether a given provider, or a given European subsidiary of a group, is subject to it is a legal analysis: it is a matter for the organisation and its lawyers, and this article does not carry it out for any offering.
For an offering that calls itself sovereign, the question is turned around: what does the claim rest on? The company that signs the contract, its shareholders, its subcontractors, the vendor of the technologies it operates and the staff who administer the platform are checked one by one. The same elements are requested in writing from a global provider.
French State bodies have their own framework: the “cloud au centre” doctrine, set by circulars of the Prime Minister, governs their use of commercial offerings according to the sensitivity of the data. Our entry on the “cloud au centre” doctrine cites its rules, presents Article 31 of Law No. 2024-449 of 21 May 2024 and flags what remains to be reread in the versions in force.
Checking the qualification and the catalogue for each service used
SecNumCloud is ANSSI’s qualification framework for cloud service providers. Qualification is granted service by service, for a given scope, and can only be checked on the list published by ANSSI. “Sovereign” and “trusted”, used alone in sales documentation, establish no qualification; our entry on trusted cloud traces the history of the expression. A service announced as “undergoing qualification” is not qualified. Finally, the question arises in the same terms for any provider, whatever its size: does the service under consideration, with the components actually used, appear on the list?
The European cybersecurity certification scheme for cloud services falls under another framework: our entry on the EUCS follows its adoption status.
The catalogue is compared on the basis of what the application uses. The team draws up the list of services it consumes or plans to consume: compute, storage, managed database, message queues, analytics or artificial intelligence tools, monitoring. It then checks, for each candidate offering, that the service exists and, if a qualification is required, that it falls within the qualified scope. With the same provider, the qualified scope may stop at the infrastructure and leave the managed database outside.
A missing service does not rule out the offering: it shifts the installation and operation of the component onto the team.
Reversibility to be tested, whatever the label
A label does not make an offering reversible. Dependency comes from provider-specific services, data formats and exit clauses, with a global provider as with a provider that calls itself sovereign. An extensive catalogue multiplies the opportunities to adopt a service with no equivalent elsewhere. A narrow catalogue can lead you to build components yourself that will also have to be moved.
Do the data come out in a usable format, and how long does it take? Which services used have no equivalent at another provider? What does the contract provide for exit assistance? Switching between data processing service providers is the subject of a chapter of Regulation (EU) 2023/2854: our entry on the Data Act presents it and flags the version to be reread. The proof remains a data return test, carried out while nothing forces you to leave.
Mixed arrangements, in the information system and in the offering itself
The first arrangement is a split. The most demanding data classes go on a qualified service or an internal infrastructure, the others with a global provider. An industrial equipment manufacturer would, for example, place its design plans on one side, its corporate website and test environments on the other. This arrangement requires a reliable classification and controlled flows between the two sides, and it means operating two platforms. Our page on sovereign and hybrid cloud describes the grid of requirements by data class and compares the corresponding architecture models.
The second plays out in the offering itself: a company under French law operates technologies that a global provider licenses to it. The questions to ask shift: who delivers the updates and through which channel, who provides support, what happens to the service if the licence ends, and does the service appear on the ANSSI list at the date of the decision?
The third leaves the data with a global provider and places the encryption keys out of its reach. It reduces the provider’s technical access to the data without removing it: to be processed, the data must be decrypted. It is reserved for the data classes that the grid allows.
Whatever the arrangement, the comparison carries a date. The ANSSI list, a provider’s structure, its catalogue and the texts change: a chosen offering is checked again at each contract renewal, against the same documents.