Open Sovereign Cloud Day Proved It: The Industry Needs a Sovereign App Store

On March 23, 2026, the cloud native community gathered for Open Sovereign Cloud Day in Amsterdam, a co-located half-day event at KubeCon + CloudNativeCon Europe. We attended the full afternoon. Here is what we took away, and why it matters for Servala.

Sovereignty Requires Ecosystems, Not Monoliths

If there was one overarching theme, it was this: no single vendor can deliver sovereignty alone. Talk after talk reinforced that digital sovereignty is not just about where your data sits. It is about control, portability, skills, interoperability, and collaboration.

This is exactly the premise Servala was built on. A marketplace that connects cloud providers, software vendors, managed service providers, and implementation partners. The ecosystem approach that speaker after speaker called for.

Kubernetes as the Lingua Franca

A thread running through nearly every session was the role of Kubernetes and the Kubernetes Resource Model (KRM) as the shared language of sovereign cloud. Michael Schmidt from SAP SE presented how the ApeiroRA reference architecture, part of the EU's IPCEI-CIS initiative, places KRM at the center of every layer, from bare metal to managed services. Every layer speaks the same API.

Vasu Chandrasekhara and Christian Hüning from BWI GmbH echoed this: certified Kubernetes is the answer to cross-provider interoperability, and "almost every use-case works with Kubernetes."

Servala implements and relies on the Kubernetes API to deliver managed services across multiple cloud providers. When the entire European sovereign cloud community rallies behind KRM as the standard, it confirms that our architectural bet is the right one.

Portability Is Not a Feature, It Is a Requirement

Alireza Rahmani from Red Hat delivered one of the day's sharpest messages: sovereignty cannot exist without portability, and portability cannot exist without designing for exit from day one. Sovereignty requires control. Control requires portability. Portability requires a deliberate exit strategy.

Services on Servala run across multiple sovereign cloud providers. If an organization wants to switch infrastructure, the open standards underneath make that possible. Not as an afterthought, but by design.

The DBaaS Trap

Floor Drees and Gabriele Bartolini from EDB gave a compelling talk on how proprietary Database-as-a-Service offerings create what they called the "DBaaS Trap." Once your data reaches serious volume, exporting it from a proprietary service becomes so painful that it effectively locks you in.

Their proposed solution: a cloud-neutral stack combining Kubernetes and CloudNativePG, replacing the proprietary black box of hyperscaler database services with an open, portable alternative.

Servala already offers PostgreSQL as a managed service on sovereign infrastructure. This is what breaking free from the DBaaS trap looks like in practice: a fully managed database experience without the lock-in.

Real Sovereign Infrastructure, Running in Production

Martin Pilka from dNation and Karsten Samaschke from VanillaCore brought sovereignty down to earth with a concrete case study: running Sovereign Cloud Stack clusters for the International Telecommunication Union (ITU). Their requirements were strict. True open source (not open core), fully documented installation, GitOps-driven operations, and complete vendor independence. They even use Keycloak for identity, a service also available on Servala.

When a United Nations agency runs production workloads on this model, sovereign cloud is clearly no longer theoretical. The building blocks exist. What is needed now is an ecosystem layer that makes them accessible and consumable.

The EU Sets the Bar with SEAL Levels

Emiel Brok from SUSE and DOSBA opened the afternoon by explaining the EU Cloud Sovereignty Framework, a scoring model with eight dimensions and SEAL levels (Sovereign Effective Assurance Levels) from 0 to 4. The audience questions were revealing: Can I use GitHub and still reach SEAL-4? Can I use hyperscalers at all? The answers were nuanced, but the direction is clear.

This graduated approach maps well to Servala, where organizations choose their cloud provider based on their specific sovereignty requirements, from Swiss to broader European infrastructure.

Minimum Viable Sovereignty

Antoine Tielbeke from Team Rockstars IT brought a refreshing take: do not wait for perfect sovereignty. Know your crown jewels, close the tap for new applications and data, and build team trust step by step.

This matches how organizations adopt Servala. You do not need to migrate everything at once. Start with one critical service, maybe PostgreSQL or Keycloak. Prove it works. Then expand.

The Kill Switch Panel

The closing panel, "Kill the Kill Switch," was the most politically charged session. Panelists discussed the real risks of dependency on US-controlled infrastructure, from the US Cloud Act to services being shut off for geopolitical reasons.

One panelist shared a sobering story: a cyberattack where attackers had been in the system for nine months, compromising even the backups. The entire infrastructure had to be rebuilt from scratch. Another pointed out that with proprietary US cloud services, you cannot even audit whether a kill switch exists.

BWI, the IT service provider for the German Bundeswehr, shared their move from VMware and Google air-gapped cloud to the Open Defense Cloud built on NeoNephos and Platform Mesh. Their message: they do not want a single vendor. They want an ecosystem based on standardization.

The panel converged on a crucial distinction: fragmentation in the market is not the same as fragmentation in the community. Open source enables collaboration across organizations and countries, even when the commercial offerings are diverse. The challenge is governance.

What This Means for Servala

Every major theme of the afternoon maps to a core Servala principle. The industry agrees that Kubernetes is the standard for sovereign cloud, and Servala builds on the Kubernetes API. Speakers demanded portability and freedom from lock-in, and Servala enables multi-cloud, multi-provider architectures. The DBaaS trap was called out as a sovereignty risk, and Servala offers managed open source databases on sovereign infrastructure. The panels called for ecosystem collaboration over isolated solutions, and that is exactly how Servala connects cloud providers, software vendors, MSPs, and partners.

Digital sovereignty is no longer a policy discussion. It is an engineering challenge, a business model question, and an ecosystem design problem, all at once. Open Sovereign Cloud Day 2026 showed that the community is ready for what Servala is building.

Explore sovereign managed services at servala.com, or learn about joining the ecosystem.