Sovereign Cloud Compass
Open standards / API portability

Open standards / API portability

Why important?

Reduces vendor lock-in and facilitates multi-provider setups.

How measured?

Scale 0–5 + N/A:
  • 0 = Highly proprietary, no meaningful portability (standards missing)
  • 1 = Limited APIs/export, strong lock-in signals
  • 2 = Some standards, but core services proprietary/without IaC
  • 3 = Kubernetes/standard APIs + IaC possible, portability only partial
  • 4 = Strong standards and IaC support + clear export/migration paths
  • 5 = High portability (standards + IaC + proven migration paths) broadly evidenced
  • N/A = no reliable evidence

Validation questions (RFP)

  • Are there standardized APIs/provider abstraction? What are exit costs and tooling dependencies?

Scores comparison

Providers Score
IONOS Cloud 5.0
SysEleven OpenStack Cloud 5.0
Cloud Temple Trusted Cloud 4.0 Terraform provider (cloudtemple) in Terraform Registry. OpenStack/OpenShift (Red Hat) as base. S3-compatible Object Storage. APIs for all services. Open-source focus (XEN fork). Gaia-X Label Level 3.
Infomaniak Public Cloud 5.0 OpenStack-based (OpenStack Powered Marketplace). Terraform/OpenTofu Provider (Infomaniak/infomaniak). OpenStack APIs + CLI. S3-compatible Object Storage. Infomaniak CLI. AWS/Azure-compatible migration emphasized.
noris Sovereign Cloud 5.0
Exoscale 4.0
Hetzner Cloud 4.0
Scaleway 4.0
T Cloud Public 4.0
UpCloud 4.0
pluscloud open 4.0
AWS European Sovereign Cloud 3.0
Delos Cloud 3.0
Microsoft Sovereign Cloud 2.0
OVHcloud Public Cloud (inkl. SecNumCloud) 2.0
STACKIT 2.0
Oracle EU Sovereign Cloud 1.0