UK’s trusted IT infrastructure partner since 2003
Servnet
FinanceToolsConfiguratorGet in Touch

XCP-ng vs VMware

The lean, no-lock-in Xen alternative for straightforward workloads — with the cost picture worked out live.

Since Broadcom reshaped VMware's subscription model, UK teams running steady, uncomplicated virtual estates are asking whether they still need vSphere at all. XCP-ng — the open-source Xen hypervisor from French vendor Vates, managed through Xen Orchestra — is the leanest credible answer. Use the calculator below to see how your host count and spend compare.

VMsHostsVMware VCF / yrXCP-ng / yr3-yr saving
503×£50,304£1,800£145,512
1004×£67,072£2,400£194,016
2508×£134,144£4,800£388,032
50015×£251,520£9,000£727,560
Annual licence: VMware VCF vs XCP-ngVMware VCFXCP-ng50 VMs£50k£2k100 VMs£67k£2k250 VMs£134k£5k500 VMs£252k£9k
Annual licence — VMware VCF vs XCP-ng — by estate size (indicative).
Replacement hosts by estate size50 VMs3 hosts100 VMs4 hosts250 VMs8 hosts500 VMs15 hosts
Replacement XCP-ng hosts by estate size (4 vCPU / 16 GB / 200 GB per VM).
3-year total cost: stay on VMware vs migrateStay (3yr)Migrate (3yr)50 VMs£151k£138k100 VMs£201k£170k250 VMs£402k£297k500 VMs£755k£519k
3-year total cost of staying on VMware vs migrating to XCP-ng (hardware, licence and migration).
Size your estate in the calculator →

All figures are indicative estimates for planning only and subject to change; licence prices vary by reseller and deal size, and any monthly finance figure is subject to credit approval — not a quotation.

Where XCP-ng beats VMware

The headline is licensing: XCP-ng is genuinely free and open-source, so you pay only for optional per-node Vates support if you want SLAs and phone cover. That turns a recurring vSphere subscription into a near-zero software line, which is why the savings on the calculator are so stark. There is no per-core metering, no bundle you did not ask for, and no vendor lock-in — the Xen codebase and Xen Orchestra are yours to run indefinitely, supported or not.

What you give up leaving vSphere

XCP-ng covers the fundamentals well — live migration, HA restart on host failure, snapshots and Xen Orchestra backup — but its ecosystem is narrower than VMware's. There is no mature equivalent to DRS automatic load-balancing, so workload placement stays more manual. Third-party tooling, monitoring integrations and installed-base knowledge are thinner than vSphere, and thinner than Proxmox too. For predictable, well-understood workloads that rarely tips the decision; for sprawling, dynamic estates it can.

Migrating from VMware to XCP-ng

Vates has invested heavily in the exit path. Xen Orchestra now ships a built-in V2V tool that streams ESXi VMs across agentlessly, with warm migration across ESXi versions including VMFS6 and vSAN, so cut-over downtime is minimal. Veeam's own XCP-ng support has landed for 2026, closing the backup gap that once held teams back. We scope the pool design, storage and network mapping, and a phased UK migration so nothing production-critical moves before it is proven.

FAQs

Is XCP-ng really free, or are there hidden VMware-style costs?

The hypervisor and Xen Orchestra are open-source with no licensing fee — that part is genuinely free forever. The only optional cost is a Vates support subscription, priced per node, if you want SLAs, phone support and managed backups. There is no per-core metering or mandatory bundle, so your software spend can legitimately fall to nearly nothing versus vSphere.

How does XCP-ng compare with Proxmox as a VMware alternative?

Both are free, open-source and capable of the core essentials. XCP-ng, built on Xen and backed by Vates, is arguably the leaner, more focused option and pairs neatly with Xen Orchestra. Proxmox has a broader ecosystem, integrated backup server and larger community. For simple, stable workloads XCP-ng is often the tidier fit; busier estates may prefer Proxmox's breadth.

Can I migrate my existing VMware VMs to XCP-ng without major downtime?

Yes. Xen Orchestra includes an agentless V2V tool that streams ESXi virtual machines directly into XCP-ng with warm migration, supporting VMFS6 and vSAN across ESXi versions, so cut-over downtime is short. We plan the pool, storage and networking first, then move workloads in phases so each is validated in XCP-ng before the old vSphere host is retired.

Plan the move