XCP-ng vs Proxmox VE for Businesses

The last version of this post went up while Broadcom's overhaul of VMware licensing was still fresh news. It is not news any more. Perpetual vSphere licences stopped being sold in December 2023, the portfolio collapsed into the VMware Cloud Foundation and vSphere Foundation bundles, and the counting unit moved from the CPU socket to the physical core with a 16 core minimum per processor. Businesses that put the decision off are now renewing on Broadcom's terms, and a lot of them are looking at open source for the first time.

That makes the XCP-ng versus Proxmox question sharper than it was. It also means the old answer has aged badly. Both platforms shipped major changes in 2026, and one of them closed the support gap that used to decide the comparison. This refresh checks the current releases, prices and feature sets, and says which one I would put workloads on.

Where both platforms stand in 2026

Proxmox VE is on version 9.2, released on May 21, 2026, and built on Debian 13 "Trixie". It uses a rolling release model, with point releases landing roughly twice a year. Proxmox VE 8 reached end of life in August 2026, so a business still running 8.x is on an unsupported branch.

XCP-ng is on 8.3 LTS, released in October 2024 and supported until November 30, 2028. That long support window is deliberate: 8.3 is the last of the 8.x line before XCP-ng 9.0, which is in development for both x86 and ARM with no firm release date. The management layer moves faster. Xen Orchestra 6.x ships monthly, and 6.9 landed on September 30, 2026.

Proxmox VE: the support gap has closed

The old case against Proxmox in business was support. That was fair at the time: paid help ran during Austrian business hours, response times were not contractual, and there was no central management layer for a multi-site estate. The case is much weaker now.

Proxmox sells three production support tiers plus a cheap Community subscription, all priced per occupied CPU socket rather than per core. Every tier includes the full feature set and the Enterprise Repository. The tiers differ only in how much support you get.

Two details matter. Premium gets 24/7 ticket support from October 19, 2026, and Standard moves to 24/7 by the end of 2026, so the old "business hours only" line no longer holds for the upper tiers. Response times are now guaranteed first response times for Severity 1 incidents, which is a real commitment rather than a best-effort promise. Basic still runs on business-hours coverage.

The second change is Proxmox Datacenter Manager, which reached 1.0 in December 2025 and 1.1 in May 2026. It gives Proxmox a central view across clusters and sites, including Ceph monitoring, central subscription handling and guest management. The "less proven at scale" criticism was never really about the hypervisor, and it is now less true of the management story as well.

If you want the free path, it still exists. The no-subscription repository needs no key and receives the same packages eventually, but Proxmox labels it non-production because packages are not tested as heavily before release. Pointing a node at it is one file:

# /etc/apt/sources.list.d/proxmox.sources
Types: deb
URIs: http://download.proxmox.com/debian/pve
Suites: trixie
Components: pve-no-subscription
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg

For a business, the honest reading is that the free repository is fine for a test cluster and a poor idea for production. A Basic subscription is €370 per socket a year, which is a small line item next to the cost of an outage.

XCP-ng and Xen Orchestra: what you get

XCP-ng is a fork of Citrix XenServer (now just XenServer), kept fully open source by Vates. The architecture mirrors VMware more closely than Proxmox does: the hypervisor runs on the host, and management lives in a separate appliance, the Xen Orchestra Appliance (XOA). You can build Xen Orchestra from source for free, or take the supported appliance.

Vates sells XCP-ng and Xen Orchestra together as the Vates VMS bundle, priced per host with one Xen Orchestra Appliance included. Every tier carries XCP-ng support licences for all the hosts in the pool.

Note the shape of this pricing. The cheapest commercial tier covers up to three hosts for a flat annual fee, while Pro and Enterprise are per host. There is no per-core or per-socket charge, and the support contract is independent of the software, so cancelling it does not switch the platform off.

The platform itself is stable and slow-moving by design. XCP-ng 8.3 will still be supported into 2028, which suits teams that want to patch and forget. Xen Orchestra has absorbed the feature work instead: the 6.x line added distributed backups, a rewritten immutable backup engine, symmetrical and bidirectional replication, QCOW2 disks beyond the old 2 TiB limit, and official Veeam support for XCP-ng in 6.8.

Head to head

Backup, HA and migration

Both platforms cover the basics, and the differences are more about packaging than raw capability.

Proxmox handles backup through Proxmox Backup Server, a separate product with incremental, deduplicated and encrypted backups, live restore, file-level recovery, and backup fleecing to cut production I/O. ZFS replication gives a built-in disaster recovery option. High availability uses multi-master clustering with no management single point of failure, dynamic HA balancing, and live migration with no downtime. Migrating off VMware is supported through an ESXi import path.

XCP-ng leans on Xen Orchestra for backup and recovery. The feature list covers full, incremental and chained backups, backup encryption, S3 targets, automated recovery checks that verify backups on a schedule, file-level restore, continuous block tracking and RAM-enabled backups. Replication is incremental and symmetrical. Live storage migration and warm migration move VMs without downtime, and a conversion tool in Xen Orchestra handles VMware migrations.

On capability this is close. Proxmox's backup tooling is a separate product you can run on its own, which some teams prefer for isolation. XCP-ng's scheduled recovery checks and immutable backup engine are strong, and the Xen Orchestra appliance puts management and backup in one place.

Licensing and total cost of ownership

Both platforms are free to run. XCP-ng is open source, Proxmox VE is AGPLv3, and neither limits features behind a paywall. The real cost question is support.

For a three-host cluster, XCP-ng's Essential tier is about $2,000 (€2,000) a year with business-day support, or $4,000 (€4,000) for unlimited tickets. Proxmox at the same size is charged per socket. A three-host cluster with two sockets each is six subscriptions: €2,220 a year on Basic, or €6,600 on Premium with 24/7 cover and a two-hour response. Proxmox is cheaper at the entry point and comparable once you buy top-tier coverage.

At larger scale the maths shifts. XCP-ng Enterprise is $1,800 (€1,800) per host per year with a one-hour critical response, and that is per host rather than per socket, so a dense four-socket server costs the same as a single-socket one. Proxmox Premium is €1,100 per socket, so that same four-socket box costs €4,400. High-core, multi-socket hosts favour XCP-ng's per-host model; many small two-socket hosts favour Proxmox. Add storage and add-ons, such as XOSTOR for hyperconvergence on the XCP-ng side, and the totals move again.

Alternative options

Hyper-V: Microsoft's free standalone Hyper-V Server product ended with the 2019 release, which remains downloadable in extended support until January 2029. Hyper-V itself is alive as a role in Windows Server 2022 and 2025, so it is not discontinued, but there is no longer a genuinely free standalone version. For a business without existing Windows Server licensing, that makes it a weaker candidate than either open source option.

KVM: the hypervisor under Proxmox. Managing bare KVM means giving up the tooling that makes Proxmox usable, so there is little reason to choose it over a full distribution.

Docker and LXD: excellent for containers, but they do not replace hypervisor-based virtual machines for workloads that need their own kernel, a different operating system, or hardware-level isolation.

What I would pick

For most businesses, I would pick Proxmox VE. The reasons that used to favour XCP-ng for serious deployments have largely been closed: Proxmox now has guaranteed response times, 24/7 support on the upper tiers, and a central management product in Datacenter Manager. Meanwhile it keeps per-socket pricing, ships new releases roughly twice a year, and offers a usable free path.

I would pick XCP-ng instead in three cases: you want the VMware-like split between hypervisor and management appliance; you need a fixed per-host support contract with a one-hour critical SLA and 24/7 cover at a predictable price; or you want XOSTOR hyperconvergence and an air-gapped deployment. The per-host pricing also wins on dense multi-socket hardware.

So the old verdict only partly survives. "Small businesses pick Proxmox, enterprises pick XCP-ng" is too clean now. Proxmox is a credible enterprise choice in 2026, and XCP-ng's edge is narrower and more specific than the last version of this post suggested.

Conclusion

VMware's move to subscription-only, per-core licensing has pushed a lot of businesses to look elsewhere, and both of these platforms can carry that workload. The choice is less about capability than about the support contract, the pricing unit, and how much you value a slow, stable release cadence against a fast one. Check your host count and socket count against the two pricing tables above before you decide, because that is where the cost difference actually lands.

If you are bringing up new servers for the first time, the first 24 hours on a new VPS checklist is a reasonable baseline to run through before anything goes into production.