You Need to Leave Proprietary Infrastructure. But How Do You Actually Do It?

Infrastructure & AI

SUSE just revealed how proprietary lock-in becomes a regulatory liability, and why enterprises will need orchestrated partners to escape it.

By Shashi Bellamkonda · April 21, 2026

98%
prioritize digital sovereignty
51%
report breach by foreign entity
43%
have formal sovereignty strategy
94%
rate open source critical to resilience

SUSE isn't building a hyperscaler alternative. It's building the infrastructure layer for enterprises that must leave proprietary stacks because their regulators now demand it. The Sovereignty Specialization, AI Factory, and Coriolis migration tool form the complete ecosystem.

At SUSECON 2026 last week, SUSE announced four things that individually look like tactical product moves. Together, they reveal a complete go-to-market system for a market that doesn't yet know it needs orchestrated solutions: infrastructure for enterprises under regulatory constraint.

The announcements were a SUSE AI Factory with NVIDIA, built for zero-trust security and data sovereignty. A partnership with Cloudbase Solutions for zero-downtime VMware migration. A new Sovereignty Specialization for SUSE One Partners. And supporting all of it, research from 309 IT leaders across five countries showing that 98 percent of enterprises now prioritize sovereignty—but only 43 percent have formal strategies to actually implement it.

That gap is not a product opportunity. It's a market reorganization.

Sovereignty became mandatory when regulators rewrote the rules

Three years ago, digital sovereignty was a European concern. NIS2 and DORA were on the way. The EU AI Act was being debated. Today, all three are law. Japan is writing its own framework. India has data residency mandates. The U.S., which historically resisted sovereignty requirements, is now writing executive orders about data protection and critical infrastructure control.

When I was at Network Solutions managing analytics, we thought of software categories as customer problems: analytics, email, hosting. But I learned then that customers don't think in categories. They think in constraints. A financial services CIO doesn't care about the "cloud" category. They care about: Where does my data live? Who can access it? Can I audit every line? Will regulators accept this architecture at inspection?

Proprietary vendors built their entire economics on avoiding those questions. VMware (now Broadcom) works when you're inside Broadcom's data center. AWS and Azure work when you trust American jurisdiction. Neither answers the question: "What if I need my infrastructure to be auditable to a specific government?"

That's why the SUSE announcements matter. Not because each one is novel. Because together they address the constraint.

The ecosystem was built to scale where hyperscalers can't

SUSE's Sovereignty Specialization doesn't ask SUSE to become a managed service provider, a system integrator, or a regional support operation. Instead, it certifies partners in those roles to deliver sovereign infrastructure on a standardized SUSE stack.

The structure: SUSE Rancher Prime and SUSE Linux Enterprise Server as the foundation (100 percent open source, auditable). Managed service providers deliver the infrastructure. Global system integrators handle customer transformation. SUSE provides Sovereign Premium Support from EU-based personnel. All of it connects through a Sovereign Reference Implementation that partners can use to accelerate deployment and reduce architectural variance.

True digital resilience is an active transformation, achieved when foundational ingredients are integrated: the foundation, the infrastructure, and the transformation.

This is how open source becomes structural. Not as a feature list or a cost reduction. But as the layer that allows regional partners to build customer trust, because the code is auditable by anyone who needs to audit it.

The research backs this. From SUSE's Digital Resilience 2026 survey (unaudited), 94 percent of IT leaders rate open source as very or extremely important to ensuring digital resilience. Forty-six percent are actively increasing investment in enterprise support for open source. These aren't ideological positions. They're risk mitigation strategies. When regulators require auditability, open source is the only option that doesn't require trusting a vendor's promise that they'll comply.

The migration path becomes the product differentiator

The Cloudbase Coriolis partnership solves a specific operational problem: zero-downtime migration from VMware to KVM-based infrastructure. But the real story is what it signals about SUSE's market understanding.

Most enterprises still run VMware because it works. After Broadcom's acquisition, many are asking whether it still makes business sense. Licensing costs have risen. Roadmap visibility has become opaque. For regulated industries, the question shifted: Can we legally certify that our virtualization layer meets our sovereignty requirements?

Coriolis doesn't force a costly forklift. It lets you move workloads one machine at a time, with zero downtime. For mission-critical SAP environments, this matters. SUSE had to certify specific migration paths for SAP workloads on KVM to make this credible. They did.

The constraint—data residency, regulatory control—is what makes the VMware exit inevitable. But the removal of operational friction is what makes it doable.

The research shows the gap, not the market

SUSE's Digital Resilience survey found that 98 percent of IT leaders prioritize digital sovereignty today. But only 43 percent have a formal strategy in place. The gap varies by region: Germany leads at 43 percent. India is highest at 58 percent (likely due to data residency mandates starting earlier). France lags at 25 percent (likely still developing frameworks). The U.S. sits at 41 percent.

This is not confidence in the status quo. Fifty-one percent of respondents report that a foreign entity has breached their company's privacy or data regulations.

The survey data is unaudited and sourced from SUSE, not an independent analyst firm. So treat the percentages as directional, not definitive. But the direction is clear: enterprises know they need to move. They don't yet have clear paths.

That's where SUSE positioned itself at SUSECON.

The question for your organization is different

If you run a regulated workload and you're still on proprietary infrastructure, the economics have shifted against you. Migration costs are no longer a blocker—zero-downtime tooling exists. Regulatory risk has become a liability—auditable stacks are now required.

The announcement that matters for your team is the Sovereignty Specialization. Not because SUSE invented something new. But because it codified how to evaluate partners who claim they can deliver sovereign infrastructure at scale.

CIO/CTO Viability Question

If you're evaluating a vendor or partner for sovereignty-constrained workloads, ask: Can they execute a Sovereign Reference Implementation for your industry? Can they certify that their infrastructure meets your regulatory audit requirements without requiring you to rely on vendor compliance attestations alone? Can they show you how they handle the operational hand-off between MSP, GSI, and your internal team when something breaks across multiple layers? That last question—who owns the incident—will tell you more about readiness than any partnership announcement.

Sources

SUSE. "SUSE Launches SUSE AI Factory with NVIDIA." News, April 21, 2026, suse.com.

SUSE. "SUSE and Cloudbase Solutions Partner to Automate Virtualization Migrations for Hybrid Cloud Workloads." News, April 21, 2026, suse.com.

Wienszczak, Hayley. "SUSE Strengthens Sovereign Service Offering with New Partner Program Specialization." SUSE Communities, April 21, 2026, suse.com.

SUSE. "Navigating Digital Resilience 2026." Research, April 2026, suse.com.

Disclaimer: This blog reflects my personal views only. Content does not represent the views of my employer, Info-Tech Research Group. AI tools may have been used for brevity, structure, or research support. Please independently verify any information before relying on it.