The challenge
Defense and public-sector organisations run enormous VMware estates. Broadcom’s acquisition of VMware turned that stable foundation into a live budget event — repricing, repackaging, and licensing changes imposed from outside, on infrastructure that is expensive and risky to move.
The instinct is to treat it as a procurement negotiation. The deeper problem is strategic: your core virtualization layer is a foreign-controlled dependency that can be repriced or relicensed at will. That is the opposite of sovereignty.
How we help
You do not have to choose between “keep paying” and “rewrite everything.” The platform runs your virtual machines on an open-source, Kubernetes-native stack:
- KubeVirt runs your VMs as first-class workloads on Kubernetes.
- Kube-OVN provides the networking fabric.
- The same platform schedules containers and GPU/AI workloads alongside those VMs.
Because it is all open source and self-hosted, the licence lever disappears — and you gain a single control plane for legacy and cloud-native workloads instead of two parallel worlds.
Migration, not a leap
VMs move without an application rewrite. Live migration and HA keep the operational model your teams already know, so the exit is an engineering project with a clear path — not a rip-and-replace gamble.
"Your Kubernetes strategy shouldn't be hostage to your hypervisor contract." The same logic applies to a defense budget: infrastructure you cannot control is infrastructure someone else can price.
Outcomes
- Keep running your VMs — on infrastructure you own and can audit.
- Consolidate VMs, containers and AI onto one sovereign stack.
- Remove the foreign licence dependency from your core virtualization layer.
- A staged migration with live migration and HA, not a big-bang cutover.
This is the sovereignty definition applied to virtualization: open, self-hosted, no foreign lever.