Proxmox licence costs vs. VMware and Hyper-V: an honest 2026 comparison

Since Broadcom acquired VMware in November 2023, the discussion around hypervisor licensing has not gone quiet in the mid-market. Almost every second DATAZONE advisory session in 2026 starts with the same question: “What does Proxmox actually cost us if we move away from VMware? And isn’t Hyper-V cheaper anyway, because we already have Windows?”

This article is not a price list. EUR figures depend too much on configuration, region, reseller terms and contract length to quote honestly here. What we deliver: the structural differences between the three models, the units of comparison you can use to run the numbers for your own environment, and the migration side-costs that get forgotten in almost every first estimate.

Understanding Proxmox licence costs: community repo vs. enterprise subscription per socket

Proxmox VE is open source under AGPLv3. That means the hypervisor itself is free of charge — there is no per-core or per-VM licence. What you can buy is a support subscription per physical CPU socket per year. This subscription separates two things that VMware bundles: access to production-grade software and commercial support.

The Proxmox offering currently has four tiers:

• Community repo (free): not a production-hardened repository in the strict sense, but the public repo with the latest patches. Common for test and development environments; usable in production without SLA if you provide your own internal support.
• Community subscription (smallest paid tier): access to the enterprise repository with more stable, longer-tested packages. No ticket support.
• Basic: enterprise repo plus a limited ticket quota per year.
• Standard and Premium: enterprise repo, higher ticket quotas, faster response times, phone support in the premium tier.

All tiers are billed per physical CPU per year. A two-socket host costs twice as much as a one-socket host, regardless of core count. That is the decisive difference to VMware.

For orders of magnitude: even the premium per-socket tier stays within a range that, for a typical three-node cluster with two sockets each, sits in the low four-digit range per year. Exact figures come directly from Proxmox Server Solutions or from us in a quote. The important point for the comparison: the subscription does not scale with core count, RAM or number of VMs.

Proxmox Backup Server as a separate line item

Something first-pass estimates often miss: the Proxmox Backup Server (PBS) has its own subscription, also per socket per year. If you use PBS seriously, you should include the backup host. Setup details are in our post on backup strategy for SMBs with Proxmox and TrueNAS.

VMware VVF and VCF per core: what Broadcom made of the portfolio

Broadcom reduced the VMware portfolio to two bundles: VMware vSphere Foundation (VVF) and VMware Cloud Foundation (VCF). For classic mid-market customers, VVF is the relevant size; VCF targets private-cloud operators.

The three structural changes that dominate the 2026 bill:

1. Subscription instead of purchase: perpetual licences are no longer sold. Existing customers lose access to updates and security patches when their support contract runs out.
2. Priced per core, not per socket: every core of every physical CPU is licensed.
3. Minimum of 16 cores per CPU: even if your CPU only has 8 cores, you pay for 16. Small hosts are structurally penalised by this.

For a two-socket host with 24-core CPUs that means 48 cores per host times three hosts, so 144 cores, times number of years. Smaller 8-core CPUs would still be billed as 32 cores per host. If you want exact Broadcom list prices, get them from an authorised Broadcom partner. We do not quote numbers because list prices and end-customer prices are not identical and terms vary per customer. Background and negotiation experience is documented in our German posts on VMware licence costs 2026 for SMBs and VMware under Broadcom: Proxmox as an alternative.

What VVF includes and what it doesn’t

VVF contains vSphere, vCenter, Aria Operations and the Tanzu Kubernetes base. For many SMB customers that is more than they need — Aria and Tanzu stay unused. If you only want the hypervisor plus vCenter, there is no cheaper path any more. vSAN, NSX and the full Aria stack are only included in VCF, which is the more expensive tier.

Hyper-V Datacenter and CALs: the “free” model with an asterisk

Hyper-V ships with Windows Server and is not separately licensed. That sounds attractive but hides two cost blocks that often disappear from comparison spreadsheets.

Windows Server Datacenter per core: to run Hyper-V with an unlimited number of Windows VMs per host, you need Datacenter. Datacenter is also licensed per physical core, with a minimum of 16 cores per server and 8 cores per socket. For a two-socket host with 24-core CPUs that is 48 Datacenter cores per host, plus the corresponding CALs.

Client Access Licences (CALs): every user or device accessing Windows Server needs a user or device CAL. For 50 employees in a typical Windows domain environment that adds 50 user CALs, independently of Hyper-V.

System Center: anyone running Hyper-V in a cluster with central management, live migration across more than two hosts and monitoring will hardly avoid System Center Datacenter. That is a third licensing line, again per core.

The bill becomes “cheap” if a business already needs Windows Server Datacenter licences for its application VMs anyway. In an environment that mainly runs Linux VMs, where Windows only holds the AD role, this quickly turns against Hyper-V, because Datacenter per core still has to compete with Broadcom prices.

Migration costs on a separate line: the honest view

A mistake we see regularly in advisory sessions: customers compare annual licence A against annual licence B and overlook the switching cost. It is one-off, but it is not small.

From VMware to Proxmox typically covers: VM conversion, rebuilding storage attachment, moving from vSAN to Ceph or external iSCSI/NFS, redoing backup, migrating firewall rules, adapting monitoring, training the team. Realistically, several person-weeks per cluster depending on size. A practical case study with actual hours is documented in from VMware to Proxmox — a real-world migration.

From Hyper-V to Proxmox is technically similar, but Windows VMs need VirtIO drivers and the AD integration must be planned again. Practical details: Hyper-V to Proxmox migration without data loss.

From VMware to Hyper-V is the most expensive path, because you carry both the Windows Server licence cost and the migration work. We rarely see this route if licence cost alone is the driver.

Parallel operation: during migration, both environments run. That costs power, rack space and — potentially — double licences for the transition period. Budget that period realistically.

A practical calculation for the mid-market: three-node cluster as a reference

Take a typical reference case: 3 hosts, 2 CPU sockets each, 24 cores each, 50 employees, mixed Linux and Windows workloads. No specific EUR numbers, but the units you multiply:

Line item	Proxmox Standard	VMware VVF	Hyper-V Datacenter
Base hypervisor	6 sockets/year	144 cores/year	144 cores/year
Central management	included	included (vCenter)	System Center 144 cores/year
Backup software	PBS 6 sockets/year	third party or Data Protection	third party or DPM
User licences	none	none	50 user CALs
Support model	tiered per socket	bundle price per core	volume contract with Microsoft
Scaling with more cores	flat	linear	linear

The picture: Proxmox is the only model that does not scale linearly with core count. If you build 24-core CPUs today and move to 32-core CPUs tomorrow, Proxmox charges the same, while VMware and Hyper-V charge a third more.

Pure licence savings are not enough as a reason

In DATAZONE advisory work we consistently recommend: do not migrate just for licence savings. Migrate when two or three factors converge — renewal shock plus hardware refresh plus team readiness for new technology. Pure licence savings often get eaten up by migration effort and the year-one learning curve. From year two on, the maths tips clearly in favour of Proxmox.

If you are looking for implementation support, details on our approach are on IT-Service Virtualisierung. For the storage side, we frequently recommend TrueNAS as an external NFS or iSCSI target — configure a suitable build in the TrueNAS configurator.

FAQ

Is Proxmox really free to use?

Yes, the community repo is free to use, even in production. What you do not get without a subscription: access to the more stable enterprise repository and ticket support. For serious production use we recommend at least the community subscription per socket so that you receive the tested enterprise repo.

How many cores per CPU must I license at minimum with VMware?

Currently 16 cores per CPU. If your CPU has fewer cores, you still pay for 16. This hits small hosts with 8-core CPUs hardest and makes consolidation on fewer, larger hosts more economically attractive — which in turn concentrates failure risk.

Is Hyper-V really cheaper if we already have Windows?

Sometimes. The effect kicks in when you would buy Windows Server Datacenter for application VMs anyway and Hyper-V operation comes essentially as a by-product. In Linux-heavy environments, or for customers running mainly file servers, domain controllers and a few services, the advantage disappears quickly.

What does a migration from VMware to Proxmox typically cost?

Realistically, several person-weeks per cluster, plus parallel-operation time. For a three-node cluster with 30 to 50 VMs we see project durations of eight to sixteen weeks, depending on storage rebuild and team experience. That is the point at which pure licence savings often disappear in year one.

Can I keep running Proxmox with my existing SAN?

Yes, Proxmox supports iSCSI, NFS, Fibre Channel and several proprietary SAN attachments. Customers coming from VMware with an iSCSI or NFS SAN can usually keep it. vSAN customers on the other hand must rebuild — either onto Ceph or onto an external storage target.

How often does the Proxmox licence model change?

Historically very rarely. Proxmox has kept the per-socket subscription model stable for many years. Tiers and prices are adjusted occasionally, but the structural model — open source plus subscription per CPU — has not changed. That is one of the reasons mid-market customers view the switching investment as calculable.