The comparison is intended for buyers running a VCF estate who are evaluating OpenShift Virtualization as a candidate migration target, typically in combination with a wider container platform strategy. The table sets out the commercial and operational dimensions that the buyer's internal cost case has to address. OpenShift Virtualization runs virtual machines on the KubeVirt project inside the same OpenShift cluster that runs container workloads, which makes the comparison different in character to a like for like virtualisation platform comparison.
The table does not provide a recommendation. The right answer depends on the buyer's workload mix, the buyer's container strategy, the operational maturity of the buyer's platform team, and the commercial terms achievable on either side. The numbers are drawn from the Desk's verified contract data and from comparable signed migration cases inside the master plan.
| Dimension | VMware Cloud Foundation (stay) | OpenShift Virtualization (migrate) |
|---|---|---|
| Licensing unit | Per CPU core subscription. Annual minimum 16 cores per CPU. Bundled scope across vSphere, vSAN, NSX and Aria operations. | Per CPU core subscription on OpenShift Platform Plus. Container workloads and VM workloads share the same license. No additional license fee for the KubeVirt based virtualisation function. |
| Headline list pricing | $350 per core annual at retail enterprise list. Verified negotiated range observed at $145 to $260 per core annual on large enterprise contracts. | $3,200 to $4,800 per 2 core annual on OpenShift Platform Plus at retail enterprise list. Verified negotiated range observed at $1,400 to $2,600 per 2 core annual on large enterprise contracts. |
| Container support | Tanzu modules available for containerised workloads at additional subscription. Container workloads and VM workloads typically run on separate clusters. | Native to the platform. Container workloads and VM workloads run on the same OpenShift cluster under the same license. Standard Kubernetes APIs for both classes. |
| Hypervisor approach | Proprietary ESXi hypervisor on certified hardware. Mature operational tooling and broad ecosystem. | KVM based hypervisor managed through KubeVirt operators on OpenShift. Built on the same KVM technology that underpins major public cloud hypervisors. Operational tooling is the Kubernetes tooling. |
| Migration cost (one off) | Not applicable on a stay decision. | Typical migration cost observed on Desk engagements ranges from $280 to $640 per VM at large enterprise scale, dependent on workload class and degree of platform team uplift required. Migration Toolkit for Virtualization provided by the vendor for VMware source workloads. |
| Operational uplift | Existing VMware operational tooling and team skills retained. Renewal does not require platform team uplift. | Operational model is Kubernetes native. Platform teams need OpenShift and KubeVirt skills. Existing VMware tooling may not transfer without replacement. Operational uplift is the dominant non license cost on most migrations. |
| Workload class fit | Strong fit across all enterprise VM workload classes including legacy and stateful workloads. Mature tooling for backup, replication, disaster recovery. | Strong fit for workloads that are already cloud native or that can be containerised. Acceptable fit for stateful VM workloads using KubeVirt. Less mature operational tooling for legacy workload classes than the VMware ecosystem. |
| 5 year total cost (illustrative, 1,000 VM workload) | $4.8M to $7.6M at the negotiated VCF subscription range, depending on per core rate and bundled scope. | $3.6M to $5.8M at the negotiated OpenShift range on the equivalent core count. Migration cost adds $280,000 to $640,000 one off. Operational uplift cost adds $200,000 to $800,000 across the term. Combined five year total $4.1M to $7.2M. |
| Renewal trajectory profile | 2026 trajectory uplift observed at +25 to +51 percent against the prior period on like for like scope, before negotiation. | Renewal trajectory observed at +6 to +12 percent against the prior period on standing renewal models inside the Desk's verified data. Most favoured customer provisions more common in OpenShift contracts than in VCF. |
| Long term optionality | Single vendor relationship across virtualisation and bundled tooling. Tanzu adds container optionality at incremental cost. | Single platform across VM and container workloads. Open source foundation provides exit optionality at the platform layer that proprietary stacks do not. Vendor relationship still required for production grade support. |
The five year total cost comparison is illustrative and is highly sensitive to two variables that the table cannot resolve in general. The first is the buyer's container strategy. Buyers whose container platform is already on OpenShift or who are committed to OpenShift on the container side carry no incremental operational uplift cost for adding VM workloads to the same cluster, and the comparison shifts materially in favour of migration. Buyers whose container platform is on a different vendor or whose VM estate is run by a team without Kubernetes operational maturity carry the full operational uplift cost, and the comparison shifts toward staying.
The second variable is the workload class. The OpenShift Virtualization fit on legacy stateful workloads with complex operational dependencies is less mature than on cloud native workloads. Buyers with a high proportion of cloud native or already containerised workloads see migration costs at the lower end of the published range. Buyers with a high proportion of legacy stateful workloads see migration costs at the upper end or above.
The Desk publishes this comparison in its evenhanded form and does not recommend either platform. The buyer side workplan for either pathway is described in the relevant service and practice pages linked below.