Sovereign Cloud Compass
Limits/quotas (transparency & increase)

Limits/quotas (transparency & increase)

Why important?

Hidden limits are a common go-live blocker. Transparent quotas and a process for raising them are critical for scaling and planning.

How measured?

Scale 0–5 + N/A:
  • 0 = Limits/quotas not transparent, adjustment unclear/impossible
  • 1 = Little information, adjustment only ad hoc
  • 2 = Documented, but processes/SLAs unclear
  • 3 = Transparent quotas + defined process for increases
  • 4 = Self-service/automation + clear SLAs/docs
  • 5 = Very transparent + API/automated + auditable processes, evidenced
  • N/A = no reliable evidence

Validation questions (RFP)

  • Are limits public and queryable via API? How fast is a quota increase? Are there hard account limits (e.g. VPC, load balancers, IPs)?

Scores comparison

Providers Score
AWS European Sovereign Cloud 4.0
IONOS Cloud 4.0
Microsoft Sovereign Cloud 4.0
STACKIT 3.0
OVHcloud Public Cloud (inkl. SecNumCloud) 3.0
T Cloud Public 3.0
Oracle EU Sovereign Cloud 3.0
pluscloud open 3.0
UpCloud 3.0
SysEleven OpenStack Cloud 3.0
Exoscale 2.0
Hetzner Cloud 2.0
Scaleway 2.0
Delos Cloud 2.0
noris Sovereign Cloud 2.0
Cloud Temple Trusted Cloud 2.0 Quotas controllable via the console. Increase process via support/order. Transparency in documentation available, but not publicly detailed.
Infomaniak Public Cloud 2.0 3 limit tiers documented (per organisation). Increase via support request. Transparency available in the FAQ.