STAKATER STAKATER Sovereign Cloud
For telcos, national CSPs, and public sector organisations ready to become the sovereign cloud provider in their market.
Three converging forces are making sovereign cloud infrastructure a strategic imperative across Europe and beyond.
GDPR, NIS2, DORA, and sector-specific mandates in defence, healthcare, and finance increasingly require data to stay in-jurisdiction — and provably so.
National governments and large enterprises are re-evaluating strategic dependence on foreign-owned cloud infrastructure. The risk calculus has changed.
Public sector, defence, and financial institutions need provable sovereignty — not a policy document from a vendor. The ability to audit the stack end-to-end.
There's a meaningful difference between data staying in-country and you actually controlling the cloud.
Rented sovereignty
✓ Data stays in-country
✗ Platform owned by a foreign company
✗ Software updates controlled by the vendor
✗ Legal jurisdiction still unclear
✗ Commercial terms set by someone else
You're a tenant. A sovereign tenant — but still a tenant.
Owned sovereignty
✓ Data stays in-jurisdiction
✓ Platform owned and operated by you
✓ You control the update cycle
✓ Full legal and operational control
✓ You set the commercial terms
You are the cloud provider. Not a reseller.
A sovereign cloud product needs three layers. Most sovereign infrastructure initiatives only have one.
Layer 3 — What your customers buy
Self-service portal · Service catalog · SLA-backed plans · Your brand · In-jurisdiction
Layer 2 — What governs it
← Stakater Cloud Orchestrator
Multi-tenancy · Governance · Metering · White-label control plane · Air-gap ready
Layer 1 — What runs it
← Red Hat OpenShift ✓ Solved
OpenShift Container Platform · OpenShift Virtualization · Your hardware · Your datacentre
Your customers get the self-service experience of a hyperscaler — without their data ever leaving your infrastructure.
Self-service VMs on OpenShift Virtualization. Data stays in your datacentre.
Sovereign OpenShift clusters — provisioned in minutes, fully in-jurisdiction.
PostgreSQL, MySQL, Redis — self-service, in your infrastructure, auditable end-to-end.
Compliant storage, secure enclaves, classified environments — add to catalog same day.
One self-service platform. Every service in-jurisdiction. Your customers never notice the infrastructure underneath.
Cloud Orchestrator operates entirely within your infrastructure. It doesn't need the internet to function.
Deployed on your OpenShift cluster. No SaaS dependency. No call-home requirement. Fully offline capable.
No forced updates from a vendor. You decide when and what gets updated. Full change control in your hands.
Tenant data, usage data, audit logs — all stay within your infrastructure. Provable, auditable, compliant.
Architecture principle
Clusters pull their configuration from the control plane. They don't receive inbound connections. Compromise of one cluster cannot reach the others — or the control plane.
Security by architecture. Not by policy.
Stakater Cloud runs on this model. We built it for ourselves first — and we've productised it for service providers who want to do the same.
Stakater Cloud: managed OpenShift with Cloud Orchestrator as the commercial layer. Paying customers in production today.
The tenancy layer is certified, on the Red Hat Marketplace, and production-ready.
No external SaaS dependency. Runs air-gapped. Designed from day one for environments where data residency is non-negotiable.
Stakater
✓ Red Hat Certified Multi-Tenant Operator
✓ Master Services Agreement — Sweden
✓ Reloader — 24B+ downloads, 9.9k GitHub stars
✓ Global team across 8 countries
Air-gap ready. Jurisdiction-compliant. You're offering self-service to tenants within 90 days.
Architecture validated, scope locked
We
· Review your current stack
· Map tenant requirements
You
· Provide infra access
· Nominate platform lead
Cloud Orchestrator running, first tenant onboarded
We
· Deploy Cloud Orchestrator
· Configure tenancy model
You
· OpenShift cluster ready
· SSO credentials
10 tenants live, self-service working
We
· Build service catalog
· White-label the portal
You
· Select pilot tenants
· Validate billing output
Full tenant base migrated, cutover complete
We
· Run-book delivered
· Team trained
You
· Cutover comms
· Support escalation path
New services launched, metering live
We
· Quarterly reviews
· New catalog items
You
· Growth targets
· Feedback loops
The infrastructure is solved. The operating model is ready.
The only thing left is the decision to build it.
stakater.com