Proxmox vs ESXi in 2026: Free ESXi Is Back, But Does It Matter?

Free ESXi exists again, and it is capped. VMware listed the free edition of vSphere Hypervisor as End of Availability in January 2024, brought it back with ESXi 8.0 Update 3e on April 10, 2025, and has not moved it since. Broadcom's KB 399823, last modified May 18, 2026, still names 8.0 Update 3e, build 24677879 as the free build: at most two physical CPUs per host, at most 8 vCPUs per VM, no vCenter, and no API management of the host. Broadcom's vSphere 9 FAQ says the free version is not made available for 9.0. Proxmox VE 9.2, released May 21, 2026, has none of those limits.

For a new host I pick Proxmox. The harder question is whether to move hosts you already run on ESXi. The migration table below answers it one VMware component at a time.

The 2026 Reality: Licensing Changed Everything

VMware announced the move from perpetual licences to subscriptions on December 11, 2023. Its End of Availability post of January 22, 2024 lists the standalone vSphere editions, including the free vSphere Hypervisor, as no longer sold.

VMware vSphere Foundation (VVF) and VMware Cloud Foundation (VCF) are priced per physical core with a 16-core minimum per CPU. Broadcom's "Counting Cores" KB 313548 states it plainly: "You must license a minimum of 16 physical cores for each CPU (physical processor) in your ESXi hosts, even if a CPU has fewer than 16 cores." Its own example is three hosts with one 8-core CPU each. They license 48 cores. They have 24. VCF includes 1 TiB of vSAN per core and VVF 0.25 TiB.

What that did to renewals shows up in court filings more than in list prices. AT&T's filing claimed Broadcom offered it a 1,050 percent increase (The Register, October 1, 2024). In a March 2024 Hacker News thread, one commenter reported a customer's $8 million renewal becoming $100 million; another self-reported $66 becoming $3,600.

General support for ESXi 7.x and vCenter 7.x ended on October 2, 2025, per Broadcom's KB 415405.

Proxmox licenses the other way. The software is AGPLv3 and every feature works without a subscription; the optional subscription is per CPU socket, each node in a cluster needs its own at the same level, and it buys the enterprise repository and support. The pricing page lists Community EUR120, Basic EUR370, Standard EUR550 and Premium EUR1,100 per socket per year (read September 26, 2026).

What Free ESXi Actually Gives You (and What It Doesn't)

Free ESXi 8.0 Update 3e is the same production build Broadcom licenses commercially; the licence key is embedded in the free download. Unlimited VMs, no licence fee. The release notes add the terms: no Broadcom support, and "it is for non-production use".

The caps, per KB 399823: a maximum of 2 physical CPUs per host and 8 vCPUs per virtual machine. It cannot be managed by vCenter Server. There is no vMotion, DRS, HA or VADP-based backup, and "usage of APIs to manage hosts is not supported", which rules out Terraform and most Ansible work against the host.

Patches stop at the free build. Broadcom's download KB 372545 names ESXi 8.0 Update 3j (build 25429389) as a later patch and says a version shows up for download only when the account "has an active license for the specific version". With no free ESXi 9, the free path ends at 8.0U3e.

The 8-vCPU ceiling is the cap I would hit first. A domain-controller test VM is fine on 8 vCPUs. A build server that wants 16 threads is not. The free tier will not bend on it. Proxmox VE has no VM, vCPU or feature limits on the free install.

What You Get With Current Proxmox VE 9.2

The current release is Proxmox VE 9.2, dated May 21, 2026, per the official roadmap. It is built on Debian 13.5 "Trixie" with Linux kernel 7.0 as the stable default, QEMU 11.0, LXC 7.0 and ZFS 2.4, and ships Ceph Squid 19.2.3, with Ceph Tentacle 20.2.1 available as a stable option.

Three releases since August 2025 carry the features a VMware migrant asks about. 9.0 (August 5, 2025) added HA affinity rules for keeping guests on, or apart across, chosen nodes, and VM snapshots on shared thick LVM through "snapshots as volume chains", as a technology preview. 9.1 (November 19, 2025) stores a VM's TPM state in qcow2, so VMs with a vTPM can be snapshotted on NFS or CIFS, and added a vCPU flag for nested virtualization. 9.2 added dynamic load balancing in the Cluster Resource Scheduler, which migrates HA-managed guests to even out node load and is the nearest thing Proxmox has to DRS, plus WireGuard and BGP fabrics in the SDN stack and a way to disarm HA cluster-wide for planned maintenance.

None of that sits behind a paywall. Clustering, live migration, HA, the REST API, and LXC containers next to KVM VMs are all in the free install, the set free ESXi lacks. (New to running both? The LXC vs VM in Proxmox guide has the decision tree for picking one per workload.)

Does Proxmox Actually Run Faster Than ESXi?

For most homelab workloads, no. The hypervisor is not what limits a Jellyfin VM and a stack of Docker containers on a mini PC. Disk and RAM are.

Where a gap shows up is storage throughput on the Linux stack. Storage vendor Blockbridge's NVMe/TCP technote, run on Proxmox VE 7.2 against ESXi 7.0 Update 3c, had Proxmox beat ESXi in 56 of 57 tests with IOPS gains of nearly 50 percent. The storage under both was Blockbridge's own product, and the test is two major versions old on both sides; I read it as a signal about Linux NVMe/TCP rather than a verdict on the hypervisors. It matters if you are building a storage-focused node serving fast NFS over a 2.5GbE or 10GbE network.

After an import, Proxmox's migration guide tells you to choose the CPU type and disk bus, then install the QEMU guest agent. That setup work is covered in the Proxmox setup guide.

Moving From ESXi to Proxmox: What Maps, What Breaks, What It Costs

Read September 26, 2026 from Proxmox's migration guide, roadmap, qm manual and admin guide and Broadcom's KBs; a dash means no source I read prices it.

Before the first import. Proxmox's migration guide walks the import wizard as: add the ESXi host as an import storage, select the VM, click Import, then boot it. The wizard can also live-import, starting the VM while the rest of its disk copies. Proxmox tested the wizard from ESXi 6.5 to 8.0, so an ESXi 9 host is outside that range. A VM with snapshots imports "significantly slower", a datastore name with a character like '+' can break the import, and pointing the wizard at vCenter instead of the host "will dramatically reduce performance". The wizard's connection service limits itself to four parallel connections to the ESXi API, and Proxmox recommends running imports one after another. Note each guest's network settings first: the adapter changes, and Windows warns when you give the new one the old IP.

Windows guests. Uninstall VMware Tools and install the VirtIO drivers while the VM still runs on ESXi. Import with the disk on SATA so the first boot works, attach a small temporary VirtIO SCSI disk so Windows loads the driver, then switch the boot disk over; Proxmox's Windows driver guide says switching without that dummy disk ends in "INACCESSIBLE BOOT DEVICE". The Windows boot guide covers the stop codes if one slips through.

Shared SAN storage. On Fibre Channel or iSCSI, Proxmox's guide starts from one big LUN with shared thick LVM, where a snapshot needs "snapshots as volume chains". That has been a technology preview since 9.0, and the roadmap's next goal is to take it out of preview, so it is still one in 9.2. Design around it before you commit a SAN estate; Blockbridge's qcow2-on-LVM technote shows how it works.

Quorum. A two-host ESXi HA design does not carry over. Proxmox needs three votes, and two nodes get the third from a QDevice. Give corosync its own low-latency network: a node running HA guests that loses quorum reboots when its watchdog times out after 60 seconds, per the HA manager manual. The cluster setup guide has the commands.

The cost line. Broadcom's own example, three hosts with one 8-core CPU each, licenses 48 cores of VVF or VCF at whatever per-core price your quote carries. The same three hosts run Proxmox for EUR0, or EUR360 a year on the Community subscription and EUR1,110 on Basic, one socket per host at list price.

Who Should Use What

Use Proxmox VE 9.2 if:

• You're building a new homelab or small server from scratch in 2026
• You want both KVM VMs and lightweight LXC containers from one interface
• You plan to add a second and third node and want free clustering, live migration and HA
• You want API access for Terraform, Ansible or scripted provisioning without a licence fee
• You're facing a VVF or VCF renewal and the 16-core-per-CPU count no longer makes sense

Use free ESXi 8.0U3e if:

• You're studying for a VMware certification and need hands-on vSphere 8 experience
• You're running enterprise hardware with VMware-certified drivers that would be painful on Linux
• Your host needs at most 2 physical CPUs and 8 vCPUs per VM, and you can do without API management, patches past 8.0U3e and clustering

Keep an existing paid vSphere environment if it is working and you aren't up against a renewal yet.

The Verdict

Free ESXi coming back is good for the ecosystem. Proxmox has rough edges. Post-import settings need review, and snapshots on shared thick LVM still depend on a technology preview.

The gap between the two free tiers is large. Proxmox VE 9.2 gives you containers, clustering, live migration, load balancing, a full API and no CPU or vCPU caps for $0. Free ESXi 8.0U3e gives you a single-host VM platform capped at 2 physical CPUs and 8 vCPUs per VM, with no vCenter, no API management, no HA, no patches past its own build and no free version 9. On the paid side, Broadcom's per-core VVF and VCF licensing with its 16-core-per-CPU floor is what sends shops to the migration table above.

I would install Proxmox. For a new build in 2026 it is not close. Between the two free tiers it is more capable. The KVM and ZFS you learn carry over to real infrastructure work, and so does Linux networking. Coming from ESXi, work down the table, prepare the VirtIO drivers, and import one VM at a time.

Tune the defaults, size the host with the Proxmox hardware guide or the capacity planner, and keep the ZFS ARC guide open if the host runs ZFS.