Sovereign Cloud Compass
IaC & automation (Terraform/OpenTofu, SDKs, APIs)

IaC & automation (Terraform/OpenTofu, SDKs, APIs)

Why important?

Reproducibility, compliance as code and speed depend on stable APIs and providers. Missing IaC increases operating effort and error rates.

How measured?

Scale 0–5 + N/A:
  • 0 = Hardly any automation/IaC, missing APIs
  • 1 = Limited APIs, no IaC providers/modules
  • 2 = IaC/SDKs only partial, important services missing
  • 3 = Terraform/OpenTofu/SDKs available for the core scope
  • 4 = Broad IaC/automation support + good docs/modules
  • 5 = Very strong IaC/automation support + best practices/blueprints, broadly evidenced
  • N/A = no reliable evidence

Validation questions (RFP)

  • Which providers/SDKs are first-party, and what is the release/support policy? Are there provider feature gaps? Is there state/drift handling and policy-as-code (OPA/Conftest) integration?

Scores comparison

Providers Score
AWS European Sovereign Cloud 5.0
UpCloud 5.0
Microsoft Sovereign Cloud 5.0
SysEleven OpenStack Cloud 5.0
IONOS Cloud 4.0
STACKIT 4.0
OVHcloud Public Cloud (inkl. SecNumCloud) 4.0
T Cloud Public 4.0
Oracle EU Sovereign Cloud 4.0
pluscloud open 4.0
Exoscale 4.0
Hetzner Cloud 4.0
Scaleway 4.0
Cloud Temple Trusted Cloud 4.0 Terraform provider (Cloud-Temple/cloudtemple) in the Terraform Registry. Extensive API library (GraphQL). Python SDK. Console Shiva as IaC-oriented platform. VM templates.
Infomaniak Public Cloud 4.0 Terraform/OpenTofu provider (Infomaniak/infomaniak). OpenStack CLI/APIs. Infomaniak CLI. Python/Go SDKs via OpenStack. S3-compatible APIs. Infrastructure as code explicitly supported.
Delos Cloud 3.0
noris Sovereign Cloud 3.0