Sovereign Cloud Compass
Customer-created metadata in the EU

Customer-created metadata in the EU

Why important?

Metadata can be sensitive (e.g. resource names, tags).

How measured?

Scale 0–5 + N/A:
  • 0 = Metadata/telemetry/billing clearly outside the EU
  • 1 = EU residency only claimed, categories (logs/tags/billing) unclear
  • 2 = Some metadata in the EU, but key categories outside/unclear
  • 3 = Most metadata in the EU, but important categories (e.g. billing/control plane) unclear
  • 4 = Metadata residency broadly documented (logs/tags/billing) with few exceptions
  • 5 = Metadata/logs/telemetry/billing EU-only + backed contractually/verifiably
  • N/A = no reliable evidence

Validation questions (RFP)

  • Which metadata (control plane, billing, support tickets) may leave the EU? Is audit evidence available?

Scores comparison

Providers Score
Cloud Temple Trusted Cloud 5.0 Console "Shiva" operated in FR; billing/monitoring/logs/support entirely in FR. No non-EU dependencies documented for metadata. SecNumCloud qualification covers the metadata scope.
AWS European Sovereign Cloud 4.0
T Cloud Public 4.0
Oracle EU Sovereign Cloud 4.0
Infomaniak Public Cloud 4.0 All systems (billing, support, monitoring, management console) operated in CH. No outsourcing. Staff entirely in CH (Geneva + Winterthur/Zurich).
IONOS Cloud 3.0
STACKIT 3.0
OVHcloud Public Cloud (inkl. SecNumCloud) 3.0
pluscloud open 3.0
UpCloud 3.0
Exoscale 3.0
Hetzner Cloud 3.0
Scaleway 3.0
Delos Cloud 3.0
noris Sovereign Cloud 3.0
SysEleven OpenStack Cloud 3.0
Microsoft Sovereign Cloud 2.0