How IT leaders can reduce hyperscaler dependency, build a sovereign cloud strategy and keep their freedom to move.
Why digital sovereignty is back on the boardroom agenda
Many IT leaders are rethinking their cloud strategy. Given the current geopolitical pressure, relying on just a few hyperscalers for all digital operations is increasingly seen as the weak point it has always been. As with all weak points, responsible leaders put controls in place to manage the risks, whether or not they are pushed to do so by increasingly strict legislation.
Risks are typically measured by chance and impact. In most cases, the impact of a cloud disruption is rising because organisations keep becoming more dependent on digital capabilities. These dependencies continue to grow across digital enterprises, robotic factories and digitally connected value chains. When the AI hype starts bearing its promised fruits, those dependencies will only increase.
On the flip side, the chance of disruption is certainly not decreasing. As a result, the sense of urgency around digital sovereignty, cloud sovereignty and operational independence is growing at a rapid pace.
Unchaining yourself from the squeezing ties of big tech can be as daring as it is indispensable.
The real challenge: moving beyond cloud ready
Given the scale of your digital operation, it is far from easy to define a sensible control for this weak point. If you consider a vendor risk, say AWS, transferring your digital operations to, say, Google Cloud may look quite straightforward. But if the United States puts a ban on your organisation, your sector or your country, such a transfer would be of little help.
In other words, a cloud exit strategy is not the same as a sovereign cloud strategy. A dozen years ago, getting “cloud ready” was a significant challenge. Today, the struggle is all about getting beyond cloud ready. Cloud wary, if you want. A potential future state of your operations that does not rely on vendors that you, and your government, have no control over.
Here is our recommended approach and practical roadmap to tackle that challenge carefully.
Core cloud technology: the basis of sovereignty
Kubernetes has changed the way we operate digital workloads. As an open source workload controller, it has become the de facto standard cloud controller. Similarly, Docker made it easier to virtualise computer workloads and gave rise to a number of alternative container runtimes.
Together, Kubernetes and container technology have laid the basis for strong cloud native architectures, with major benefits such as:
- Lower operating costs through better resource usage.
- Higher reliability through autoscaling and self healing techniques.
- More resilience by stretching networks and workloads over multiple availability zones.
- Better governance through automated build and delivery workflows.
- Faster software delivery through microservice deployments, high bandwidth and strong interoperability.
In short, cloud native architectures that follow Kubernetes design principles have become the new gold standard for organisations that want resilience, portability and digital sovereignty.
The downside of Kubernetes complexity
On the downside, Kubernetes has undeniably introduced new complexities. Its open architecture and narrow focus gave rise to many different solution components for extra capabilities. This created a fast changing marketplace with lots of solution components to choose from, integrate and maintain.
Just keeping up has become a daily struggle, let alone moving ahead. You are not alone in that struggle. Rest assured that solutions are appearing to tackle exactly this pain point.
Kubernetes through the lens of Linux history
In many ways, today’s Kubernetes landscape resembles the early days of Linux. Linux changed operating systems, its open source model gave rise to new business models, and it could run on SUN, HP and Intel hardware alike, before long also on IBM mainframes.
True, there were similar complexities. Portability was never easy, and choice paralysis was real. In fact, many user organisations created their own mix of tools and utilities that together shaped their operating landscape.
Creating your own landscape of components from the cloud native computing arena has a clear parallel in computer history. Unsurprisingly, the Cloud Native Computing Foundation (CNCF), which oversees the cloud native ecosystem, is part of the Linux Foundation. Although there is no technical need to run Kubernetes and all its tools and utilities on top of a Linux OS, I have yet to come across an organisation that seriously considered running its Kubernetes platform on top of Windows. Nowadays, even Microsoft relies heavily on Linux to power Azure. At the same time, you can still run Windows workloads inside your container runtime if you choose to do so. Kubernetes, like Linux, is open by nature.
With Linux, we already know how the complexity of its early days was overcome. As Linux matured, selected tools and utilities were bundled into a range of distributions, each with its own support model and each one aligned with a specific use case or industry. That made adopting Linux much easier.
Although there are hundreds of Linux distributions on the market today, I have not heard anyone complain about the problem of too much choice lately. Linux is even conquering the desktop space, being considered easier to use and more reliable than alternatives. Why not? If it is excellent at powering your phone and most of the internet, it is only a matter of time before Linux’s role in personal computing keeps expanding too.
Meet OpenChoreo: an open source platform for sovereign cloud operations
You do not have to be clairvoyant to predict that Kubernetes will move in the same direction as Linux did before. Moreover, the first fully featured Kubernetes distributions are entering the market already. At Yenlo, we are invested in a WSO2 distribution called OpenChoreo, which recently got accepted to CNCF.
OpenChoreo includes tooling such as Cilium, Envoy Gateway, Linkerd, KEDA and OpenSearchDB to create a rich cloud platform out of the box. You have the option to stretch the platform over multiple availability zones, and it allows you to run and manage basically any containerised workload, including AI agents.
OpenChoreo takes just a couple of minutes to download, install and launch on your own laptop. If that is not already amazing enough, it is also designed as a platform for developers, giving them the convenience of managing their workloads simply from inside their VS Code IDE. WSO2 also offers professional 24×7 support, keeping the platform secure, up to date and resolving reported bugs at a fair cost.
Adopting OpenChoreo is your best shot at achieving full digital sovereignty anytime soon.
WSO2 has always made a big point of its open source culture. Everything WSO2 produces is 100% out in the open: code, documentation and all. OpenChoreo is no exception. You read that correctly. OpenChoreo is 100% open source, batteries included, zero commercial traps.
That makes adopting OpenChoreo on top of your favourite Linux distribution a very attractive combination for organisations that want to regain digital sovereignty. You can take ownership of the software anytime you feel the need to. It is always just a fork away. Is that not reassuring?
A practical digital sovereignty roadmap
Having control over your cloud operating platform is an important part of your digital sovereignty strategy. On paper at least, you gain the freedom to run your cloud operating platform anywhere: at a hyperscaler, at a local hosting provider, on your own premises or in an in between hybrid state.
All the platform needs is compute, storage and network functionality, all of which have basically become commodities. Strategically, you should aim for running all your workloads on OpenChoreo, thereby becoming free to move anywhere that suits you best, anytime.
After all, your workloads will never need to know on what infrastructure the cloud platform that hosts them is deployed. Freedom to move quickly is the best investment in digital sovereignty you can possibly make.
The best investment in digital sovereignty you can possibly make is the one in your freedom to move quickly and decisively.
Step 1: deploy OpenChoreo on your current infrastructure
Obviously, you need to manage your migration risk carefully. With OpenChoreo, you can separate the risk of moving workloads to the cloud platform from the risk of moving the cloud platform to a target infrastructure platform, whether that target is provided as a service, fully on premises or somewhere in between.
The smallest first step you can take is deploying OpenChoreo on top of your current digital infrastructure. This allows you to gradually start moving existing workloads to your new cloud platform.
Step 2: increase your share of containerised workloads
In parallel, you can work on increasing your share of containerised workloads and, where needed, fully apply cloud native principles and practices such as deployment automation, immutable runtimes and remote observability.
That is a widely proven recipe for reducing operational and security risks, and would therefore certainly be a no regret investment.
Step 3: replace hyperscaler specific dependencies
Additionally, you can work on sovereign alternatives to serverless features you may be using today. There is plenty of choice in the CNCF catalogue on this front. You can also rebuild your operations capability where needed. Since AI copilots for platform operations are maturing quickly, the latter should be a relatively easy step to take.
By the way, it is a highly recommended practice to make your external dependencies clear and measurable, and to report regularly on your progress towards independence. It will motivate your team and help keep your auditors happy as well.
Setting a clear sovereignty goal gives direction. Reporting on progress builds momentum.
Step 4: build the target sovereign cloud platform
Next, build the cloud platform on top of your target infrastructure platform. At first, migrate your test environment only. This should be just a matter of updating your CI/CD pipelines, right?
Then, after thorough testing, move preproduction. When that works out fine, create a disaster recovery environment. At this point, it is essential to minimise data loss whenever recovery is needed. Consider using Debezium, or a similar alternative. And do not forget to test your recovery plan carefully and regularly.
Step 5: decide how far to move
You can stop here and keep using your trusted infrastructure until disaster strikes. But do make sure that you have the necessary resource capacity available when this happens, potentially to millions of companies at once. If needed, you can temporarily sacrifice the hardware resources set aside for testing. Human resources, however, must be on standby.
Alternatively, you can opt to move only your business critical workloads to your sovereign cloud platform. But remember that operational risks never go away entirely. So you still need alternative infrastructure available to recover from disaster. This might be at your current provider, or at yet another facility. Fortunately, by now you can fully benefit from your fresh ability to move quickly.
How to set a measurable sovereignty goal
Although the strategy outlined here is high level, we hope it inspires you and helps you get a better grip on the challenge ahead. Obviously, you will need much more detail to turn this strategy into action and create a realistic roadmap tuned to your particular situation.
The European Union has defined five levels of sovereignty, from SEAL-0 up to SEAL-4. In its Cloud Sovereignty Framework, eight categories are defined, ranging from strategic sovereignty to supply chain sovereignty. This framework may help you set a goal.
For technology sovereignty specifically, having a proven strategy that allows you to move wherever and whenever will help you score high, provided you can prove that moving your digital operations to a true European sovereign cloud is feasible over a short span of time and without significant business disruption. Having full data sovereignty would be an important requirement.
Build the right digital sovereignty team
When you are ready to establish your strategy and take charge of its implementation, it is a good idea to appoint a multidisciplinary taskforce. This team should oversee your entire digital ecosystem and understand the risks involved with changing it. It should also deeply understand modern cloud technologies and how to benefit from them.
A good mix of internal subject matter experts and highly skilled external consultants often works best.
How Yenlo can help you regain digital sovereignty
As a cloud service provider, Yenlo has the capability and ability to bring together the right resources to advise and assist you in regaining your digital sovereignty. Yenlo does business around the world and proudly cherishes close ties with WSO2.
Why not simply reach out and start a conversation?
FAQ: digital sovereignty, sovereign cloud and OpenChoreo
What is digital sovereignty?
Digital sovereignty is the ability to control your digital operations, data, software stack and infrastructure choices without being locked into suppliers, legal regions or dependencies that you cannot influence.
Why does cloud sovereignty matter now?
Cloud sovereignty matters because digital dependencies are increasing while geopolitical, regulatory and operational risks are becoming harder to ignore. The more critical your digital operations become, the more important it is to keep practical freedom of movement.
How can Kubernetes support digital sovereignty?
Kubernetes supports digital sovereignty by making workloads more portable across infrastructure environments. When combined with the right open source tooling, governance and operating model, it helps organisations avoid deep dependency on one infrastructure provider.
What makes OpenChoreo relevant for a sovereign cloud strategy?
OpenChoreo brings a rich cloud platform together as an open source Kubernetes distribution. It gives organisations a practical way to run and manage containerised workloads while keeping control, portability and the ability to move.
What is the first step towards regaining digital sovereignty?
A sensible first step is to deploy a sovereign cloud platform such as OpenChoreo on top of your current infrastructure, then gradually migrate workloads while measuring and reducing external dependencies.
