Affiliate disclosure: Some links in this guide earn us a commission at no extra cost to you. We only recommend hardware we'd run ourselves. Read our full disclosure.
The one-table decision matrix
Nine rows, three hypervisors, no marketing copy. Scoring: ✓✓ best-in-class, ✓ good enough, ● workable with caveats, ✗ real gap.
| Capability | Proxmox VE 9.x | XCP-ng 8.3 | ESXi (subs. only) |
|---|---|---|---|
| Free-forever licence | ✓✓ AGPL, whole stack | ✓✓ GPL core | ✗ free tier removed 2025 |
| Web UI quality | ✓✓ one UI for everything | ✓ via Xen Orchestra | ● Host client trimmed, vCenter paid |
| Built-in software storage | ✓✓ ZFS, Ceph, LVM | ● local LVM/XFS; shared via XOSAN (paid) | ● vSAN licensed separately |
| Cluster + HA | ✓✓ corosync, quorum, HA | ✓ pool HA with XOA | ✓✓ mature, but $$$ |
| Backups included free | ✓ vzdump snapshots | ✓ XO CE schedulable | ● needs third-party tool |
| Open ecosystem/API | ✓✓ REST + community tooling | ✓✓ XAPI, mature SDKs | ● vSphere API strong but gated |
| VMware VM import | ✓✓ native import wizard (8.2+) | ✓ via Xen Orchestra / qemu-img | ✗ you are leaving anyway |
| GPU passthrough docs | ✓✓ mainstream, huge guides corpus | ✓ solid, smaller community | ✓✓ gold standard docs |
| 2026 community energy | ✓✓ the exodus default | ✓ growing fast | ● enterprise-only mindshare |
Scores reflect our homelab/small-fleet lens from the VMware exit analysis — enterprise DC requirements change several rows.
Licensing & cost: who charges what in 2026
- Proxmox VE: the hypervisor, web UI, clustering and ZFS/Ceph storage are all free and open source under AGPLv3. The only paid item is the optional subscription (from about $115/CPU-socket/year for community) that unlocks the enterprise package repository — worth it for production, skippable for a lab.
- XCP-ng: free and open source under GPLv2, backed by Vates which sells support tiers and the enterprise edition of Xen Orchestra. The classic homelab combo is free XCP-ng + free Xen Orchestra Community Edition (XO CE) deployed as its own VM.
- ESXi: the free tier Broadcom discontinued in early 2025 was the single most consequential event in home virtualization this decade. What remains are subscription SKUs through the (also restructured) VMware by Broadcom portfolio — the desktop-class Workstation/Fusion products went personal-use-free instead, which helps workstation experiments but not servers.
The honest framing: ESXi is no longer a competitor for free infrastructure — it competes for enterprises with budgets and compliance needs, where it remains excellent. If your cost floor is $0, the real comparison is Proxmox vs XCP-ng (and Hyper-V only if you already own Windows Server licences).
Backup tooling: the real tiebreaker
Migrations fail quietly in one place: backups running on day 90. This is where the two open-source platforms differ most in feel:
- Proxmox: vzdump is built in — snapshot-mode backups per VM/CT, scheduled from the web UI, retention policies included. It is not the most feature-rich cloud-native backup, but it always exists. For deduplicated, application-consistent backups, Proxmox Backup Server (also free) is the companion and does incremental + encryption well.
- XCP-ng: Xen Orchestra is the control plane — scheduled backups, CR (continuous replication), delta restore, file-level restore in paid tiers. The free XO CE covers scheduled backup/restore well enough for a lab. The mental model is closer to classic vCenter + Veeam than Proxmox's built-in approach.
- ESXi: nothing meaningful built in; the ecosystem expects Veeam/ Nakivo/ Rubrik. With subscriptions now costing more, the total stack price is the real number, not the hypervisor line item.
Rule of thumb from our migration playbook: pick the platform whose day-90 backup story you will actually configure before day 3.
Migration: how each platform imports your VMs
- Proxmox VE 8.2+ import wizard: point it at ESXi/vCenter, select VMs, it handles disk translation and creates the guests — the smoothest path we tested (details in the Proxmox Migration Playbook).
- XCP-ng: Xen Orchestra's import or OVF import handles VMware exports; qemu-img + a fresh VM definition works for straightforward cases. Slightly more manual than Proxmox's wizard for a like-for-like ESXi escape, and markedly better than everything else if you are escaping old XenServer — that is its home turf.
- Stay on ESXi: nothing to migrate, but you inherit the licence treadmill — and if you ever take VMs out, the OVF tooling remains the best-documented export path in the industry.
HA, clustering & storage architecture
Proxmox clustering uses corosync: odd quorum device counts matter, a QDevice on a Pi is a legitimate third vote for two-node clusters, and HA is a checkbox once shared storage (Ceph or shared ZFS/iSCSI) exists. It is the best-documented free HA story in the homelab world.
XCP-ng pools replicate the vSphere mental model — one pool, live migration inside it, HA optional. Its shared-storage story for free users is thinner: NFS/iSCSI work fine, the glossy software-defined storage (XOSAN) is a paid product. If your plan is a 3-node Ceph cluster, that tilts to Proxmox; if your plan is 2 hosts with NFS to a NAS, XCP-ng is equal-or-better.
ESXi remains the polish benchmark for vMotion/DRS, but at 2026 subscription pricing it only makes sense where those features are being paid for by the business.
The 60-second decision tree
- Do you already run XenServer/XenCenter fleets? → XCP-ng. Your skills transfer 1:1 and XO gives you the missing control plane on day one.
- Do you want a 3+ node cluster with shared, self-healing storage on a budget? → Proxmox + Ceph (fabric: see the 10GbE switch guide).
- One or two nodes, simple, biggest guide corpus, one web UI for everything? → Proxmox + ZFS.
- Already licensed for Windows Server and the lab is 2-3 VMs? → Hyper-V role is fine; no need to introduce new tooling. Revisit if you outgrow it.
- Enterprise with compliance needs, existing Veeam estate, deep pockets? → ESXi subscription (or Nutanix/RHEL-V) — this guide is not for you, and that is fine.
Still torn between Proxmox and XCP-ng after that? Flip a coin — both are correct technical answers, and the cost of switching later is one long evening and the playbook.
Hardware that runs all three happily
All three want the same box: a recent 6-16 core CPU with VT-x/AMD-V and IOMMU, 64GB+ RAM, NICs with real offloads, and SSD/NVMe for the storage tier. Deep-dive builds: the Best Proxmox Server Build covers three reference bill-of-materials, and the Best 10GbE NIC for Proxmox picks the connective tissue. Quick affiliate shortcuts:
FAQ
Is ESXi Free dead in 2026?
Practically, yes — see the FAQ schema above for the short version: the free tier was removed in 2025 and only subscription SKUs remain.
Which is better for a homelab: Proxmox VE or XCP-ng?
Proxmox for most; XCP-ng if you carry Xen muscle memory or existing XenServer fleets. Everything else in this list is nuance.
Can I convert VMware VMs to Proxmox without rebuilding them?
Yes for the overwhelming majority — the 8.2+ import wizard is the low-friction path; budget an evening per VM for validation.
Does XCP-ng cost money?
The hypervisor is free; paid tiers cover support and enterprise XOA features. A homelab can run 100% free.
What about Hyper-V?
Free standalone Hyper-V Server is gone (2019 last version); Windows Server licences make it viable only where those licences already exist.
How do I choose between ZFS and Ceph on Proxmox?
ZFS for 1-3 nodes without shared-storage needs; Ceph for 3+ nodes where VMs must survive node loss. Ceph wants 10GbE+ and lots of RAM.