Sovereign cloud is usually sold as a question of place. Put the data centre in the country, keep the data inside it, and call the result sovereign.
Place matters. But a cloud can sit entirely inside your borders and still depend on one company’s roadmap, one company’s licence terms and one company’s decision about what the software will do next year. When that company changes its prices, its products or its priorities, the sovereign cloud changes with it.
That is why so many national programmes, regulated enterprises and regional providers are building on open technology. Not because it is cheaper, although it often is. Because you cannot claim independence while depending on something you are not allowed to inspect, adapt or continue without permission.
Sovereignty has a technology layer
Sovereignty is not one question. It is seven: data, infrastructure, operations, identity, security, governance and technology. The first six get most of the attention. The seventh is the one that decides whether the others last.
The technology layer is the right to run, inspect and continue the platform without a foreign dependency. If the software beneath your cloud can be withdrawn, repriced or redirected by someone outside your jurisdiction, every other layer of control sits on a foundation you do not own.
You cannot claim independence on software you are not allowed to continue.
The dependency you do not see on day one
Proprietary platforms are often impressive, and nothing here pretends otherwise. The integrated stack, the single support contract and the polished roadmap are real advantages.
The cost shows up later. A platform built entirely on one vendor’s technology ties you to that vendor’s roadmap, its licensing structure, its pricing changes and its product decisions. Migrating workloads becomes a project. Introducing new technology needs the vendor’s blessing. Negotiating becomes difficult, because both sides know how hard it would be to leave.
For an ordinary IT estate, that is an inconvenience. For a sovereign cloud, it undermines the reason the programme exists.
What open actually gives you
Open technology lines up with sovereignty for reasons that are practical rather than ideological:
- Transparency — you can see how the technology works, rather than trusting a description of it.
- Adaptability — you can shape it to local requirements instead of waiting for a vendor to prioritise them.
- Continuity — no single company controls its future, so no single decision can end it.
- Portability — workloads move between environments more easily, which keeps every relationship honest.
Open-source infrastructure has matured into production-grade compute, storage, networking, containers, databases, automation and monitoring. Much of modern cloud already runs on it. It is no longer the alternative. For many sovereign programmes, it is the starting point.
Security through visibility
A common assumption is that closed software is safer because fewer people can see inside it. Security does not work that way. It depends on process, governance and the ability to verify.
Open technology lets an organisation review code, validate security controls, run independent assessments and find vulnerabilities rather than wait to be told about them. For governments and regulated industries, which have to show how their technology behaves rather than assert it, that visibility is worth a great deal. Security should never rely on secrecy.
The honest trade-off
Open source has a cost too, and a credible argument says so. It needs expertise. It needs operational maturity. It needs governance that nobody hands you in a box.
Above all, open components are not a cloud. A hypervisor, a container orchestrator and a storage system do not add up to a service anyone can buy. Between them and a working cloud sit a self-service portal, a catalogue, multi-tenancy, metering and billing, identity, policy, audit and a marketplace. That layer is where many open-source cloud programmes stall, and it is why the industry kept offering the same trade: you can have a cloud that works, or a cloud that is yours. An integrated proprietary platform, or open parts you assemble and carry yourself.
It should not have to be one or the other.
AI runs on open frameworks
The same logic now applies to artificial intelligence. National AI strategies, research programmes and enterprise AI all depend on GPU infrastructure, training environments and the frameworks that sit on top of them, and the frameworks that matter most, such as PyTorch, TensorFlow and JAX, are open.
For sovereign AI, that is a gift. Training data, models and intellectual property can stay under local governance, on frameworks no single vendor can withdraw or reprice. What has to be owned is the infrastructure beneath them.
Open ground grows local ecosystems
Open technology also changes who can take part. Skills built on it are portable and they stay in the country. Cloud providers can launch services under their own brand rather than reselling someone else’s. Managed service providers, integrators, software vendors and universities can build on the same foundation, and the expertise compounds locally instead of flowing to one vendor’s partner programme.
Open underneath. Owned above.
This is where Oasis Stack fits. It runs above infrastructure you already own and publishes it as services: OpenStack, CloudStack and Kubernetes, as well as existing VMware estates, bare metal and GPU, on x86 or ARM, on-premises or in a colocation facility you choose. It adds the layer open components do not provide on their own, from tenancy and billing to governance and a marketplace, with no lock-in to any infrastructure vendor underneath. Its Wellness Dashboard is built on open tools, Grafana, Prometheus and Wazuh, and its AI infrastructure supports PyTorch, TensorFlow, JAX and Triton.
The point is not the licence on any single component. It is that the operator keeps the right to run, inspect and continue the cloud, and can still offer the breadth customers expect. Through the federation, an independent cloud can offer and consume services with other clouds by explicit agreement, while its data, operations and keys stay home. Sovereignty should not cost you scale.
The race is not for the largest cloud
The sovereign cloud race will not be won by whoever builds the biggest platform. It will be won by whoever builds the one a country or an organisation can trust, inspect and keep running on its own terms. That is why the foundations are increasingly open. And it is why the layer above them has to be owned.