XCP-ng vs. Proxmox: two open-source paths out of the VMware world

Timo Wevelsiep•Updated: 09.07.2026

Editorial note: Versions, commands and prices may change. Please verify critical steps independently before production use. This guide does not replace individual consulting.

Anyone looking for a VMware or Citrix alternative in 2026 almost always ends up with two candidates: XCP-ng and Proxmox VE. Both are open source, both production-ready - and yet fundamentally different. This comparison honestly lays out where each system is the better choice. For the view on VMware itself, see the Proxmox vs. VMware comparison.

Architecture: Xen versus KVM

XCP-ng comes from Vates and is based on the type-1 hypervisor Xen (currently Xen 4.17) with a CentOS-7-based dom0 as the control domain. Proxmox VE builds on a current Debian with KVM/QEMU for VMs and LXC for containers. Both approaches are mature; KVM benefits directly from the mainline kernel, Xen brings a long isolation track record. XCP-ng 8.3 has been the LTS release since June 2025 with support until November 30, 2028 (release notes), and is actively patched - this is by no means a dead project.

Management: separate XO versus integrated interface

The biggest day-to-day difference: XCP-ng is managed via Xen Orchestra (XO) - a separately operated web interface with backup features and a Terraform provider. "XO from sources" is free; the ready-made appliance (XOA) with support is commercial. Proxmox ships everything integrated: GUI, clustering, HA and backup integration are part of the product itself, with no extra component.

On support costs (as of July 2026): Vates bundles support in its VMS packages - Essential 2,000 US dollars/year (max. 3 hosts), Essential+ 4,000, Pro 1,000 per host/year (min. 3), Enterprise 1,800 per host/year (min. 4, 24/7). Proxmox subscriptions are optional and cost 120 to 1,100 euros per socket per year.

Storage: SR model versus native ZFS and Ceph

XCP-ng organizes storage in storage repositories (SRs): officially supported are EXT, LVM, NFS, iSCSI and HBA; ZFS and Ceph run only "as-is" without official support. Block SRs are thick-provisioned, and the VHD format historically capped virtual disks at 2 TiB - only with the QCOW2 GA in May 2026 did the limit rise to 16 TiB. Add the limit of 64 vCPUs per VM.

Proxmox integrates ZFS, Ceph and LVM-thin natively - including replication, snapshots and hyper-converged Ceph from its own GUI. If you want to build your storage concept around ZFS or Ceph, Proxmox is the much shorter path.

Backup: XO backup versus Proxmox Backup Server

Xen Orchestra ships backup jobs out of the box - solid and included in the bundle. Proxmox relies on the Proxmox Backup Server, a dedicated product with deduplication, incremental backups and verification. For larger environments with long retention periods, that is the weightier approach.

Migrating from XCP-ng to Proxmox

The cleanest documented path runs via OVA: export from Xen Orchestra, then import via Proxmox's OVA/OVF import (GUI since PVE 8.3, alternatively qm importovf - migration docs). The often-cited XVA export with conversion via xva-img works too, but it is pure community tooling with no official import path. Inside the guest, the Xen tools have to go and VirtIO drivers come in. The convenient PVE import wizard targets ESXi, not XCP-ng. The topic is getting extra momentum from Citrix: on April 15, 2026, file-based licensing ends, the License Activation Service becomes mandatory and requires XenServer 8.4 or newer - which is why many XenServer shops are revisiting the platform question right now.

The differences at a glance

	XCP-ng 8.3 LTS	Proxmox VE 9.x
Hypervisor	Xen 4.17 (type 1), LTS support until Nov 30, 2028	KVM (VMs) + LXC (containers) on a current Debian base
Management	Xen Orchestra as a separate appliance; XOA tiered by edition, "from sources" free but unsupported; XO Lite built in for basic tasks	Web GUI integrated on every host, no management server needed
Storage	SR concept (SMAPIv1): thin on EXT/NFS/ZFS, thick on LVM over iSCSI/HBA; QCOW2 disks up to ~16 TiB	ZFS, Ceph and LVM-thin natively; snapshot-capable types with thin provisioning
Backup	Xen Orchestra: full/incremental backup, incremental replication, mirror	Proxmox Backup Server: deduplication, incremental, verification, encryption
HA & live migration	Free; HA requires a shared SR as heartbeat, 3+ hosts recommended	Free and integrated, no feature gates
Support model	Vates VMS: Essential, Essential+, Pro, Enterprise	Proxmox subscription per CPU socket; identical software in all tiers

The honest verdict

XCP-ng is a solid, actively maintained Xen ecosystem - a natural harbor especially for teams with a XenServer past. Proxmox scores with its integrated storage ecosystem (Ceph, ZFS), the Proxmox Backup Server and the larger community momentum. Both are legitimate choices; Proxmox is our operational focus because integration and storage flexibility tip the scales in managed operations.

How WZ-IT does it

We run Proxmox environments as Managed Proxmox from €179.90 per node per month - and take over existing environments even when they still have to be migrated there from XCP-ng or XenServer first: health check, migration plan, the move itself, operational responsibility. Which platform fits your environment is something we assess neutrally in a free initial consultation.

You'd rather not run Proxmox yourself? WZ-IT handles setup, operations and maintenance – GDPR-compliant from Germany.

Managed Proxmox →

Frequently Asked Questions

Answers to the most important questions

Yes. XCP-ng itself is open source and usable without license costs, as is 'Xen Orchestra from sources' if you build it yourself. It gets commercial with the ready-made XOA appliance and with support: Vates bundles both in its paid VMS packages.

Vates VMS (as of July 2026): Essential 2,000 US dollars per year (max. 3 hosts), Essential+ 4,000, Pro 1,000 per host per year (min. 3 hosts), Enterprise 1,800 per host per year (min. 4 hosts, 24/7). Proxmox subscriptions are optional and cost 120 to 1,100 euros per socket per year - the software is identical either way.

Yes. The cleanest path is the OVA export from Xen Orchestra followed by Proxmox's OVA/OVF import (GUI since PVE 8.3, alternatively qm importovf). The XVA export with conversion via xva-img works too, but is community tooling. Inside the guest, the Xen tools have to go and VirtIO drivers come in - the path is more manual than from VMware, where PVE ships an import wizard.

Both are mature hypervisors; the question is not decided in the core. Xen (XCP-ng) is a classic type-1 hypervisor with a long isolation track record; KVM lives in the mainline Linux kernel and benefits directly from its development pace and hardware support. In practice, the surrounding ecosystem decides: storage, backup, tooling, community.

Citrix discontinues file-based licensing on April 15, 2026; after that, the License Activation Service (LAS) becomes mandatory and requires XenServer 8.4 or newer. For many existing XenServer customers this is the trigger to revisit the platform question - XCP-ng and Proxmox are the obvious open-source destinations.

Our operational focus is Proxmox, and we accompany the way there: health check of the existing XCP-ng or XenServer environment, migration plan, moving the VMs and then taking over operations of the new Proxmox platform - including monitoring, patching and backup responsibility.