Every homelab thread eventually turns into a hypervisor argument. Here’s the practical version, based on what actually matters when it’s your own gear and your own time on the line.

The short answer

If you’re starting fresh in 2026, run Proxmox VE. It’s free, actively developed, has a real community, and does everything most home labs need — VMs, LXC containers, clustering, ZFS, and a web UI that doesn’t feel like an afterthought. The rest of this post is for the “but why” crowd.

Proxmox VE

Proxmox is a Debian-based hypervisor with KVM for VMs and LXC for containers side by side — that combination alone is a big reason it’s become the default homelab choice. Containers are lighter than VMs for anything Linux-native, and you’re not stuck picking one virtualization model for your whole cluster.

Strengths:

  • No licensing tier that suddenly starts asking for money (there’s a paid support subscription, but the software itself is fully functional without one)
  • Native ZFS support, including boot-drive ZFS mirrors
  • Clustering is built in and doesn’t require a separate management VM
  • LXC containers for anything that doesn’t need full VM isolation — dramatically lower overhead for things like Gitea, Pi-hole, or a reverse proxy

Weaknesses:

  • Hardware compatibility list is less exhaustive than VMware’s — check your NIC and storage controller before committing
  • The web UI, while functional, is not going to win design awards

VMware ESXi

ESXi used to be the default recommendation, largely because so many admins learned virtualization on it professionally. That’s changed. Broadcom’s acquisition of VMware reshaped licensing hard, and the free ESXi tier that homelabbers relied on for years is effectively gone. You can still find hardware compatibility and vMotion-style live migration that’s genuinely more polished than the alternatives — but you’re now evaluating whether that polish is worth what it costs, in money or in workaround effort, for a home environment.

Where it still makes sense: if your day job is VMware administration and you want your homelab to mirror production, or you already have valid licensing through work.

XCP-ng

XCP-ng (built on Xen) is the option most people haven’t tried and probably should look at more. It’s fully open source, backed by Vates, and pairs with Xen Orchestra for management — which, notably, is also free if you’re willing to build it from source instead of paying for the pre-built appliance.

Strengths:

  • Genuinely open source top to bottom, no asterisks
  • Live migration and other “enterprise” features aren’t locked behind a paywall
  • Solid track record for stability

Weaknesses:

  • Smaller community than Proxmox means fewer guides for oddball problems
  • Xen Orchestra’s free tier requires you to build from source and self-update — the paid appliance is otherwise the easy path

What actually matters for a home cluster

Three things separate a good choice from a regret six months in:

  1. Hardware support. Check your specific NIC, storage controller, and any passthrough devices (GPUs especially) against each platform’s compatibility notes before you commit, not after.
  2. Container vs. VM mix. If most of what you’re running is Linux services, Proxmox’s LXC support saves real RAM and disk over VM-only platforms.
  3. What happens when it breaks. Proxmox and XCP-ng both have active forums where real answers show up fast. That matters more than any single feature when you’re debugging a broken cluster at 11pm.

For most home setups in 2026, Proxmox remains the pragmatic default — free, well-documented, and flexible enough to grow with a cluster instead of forcing you into a redesign later.