VMware Licensing Cost: How Pricing Actually Works in 2026

VMware licensing cost is calculated per physical core, with a minimum of 16 charged for every processor and a 72-core minimum on any order, sold as a subscription bundle rather than a perpetual license. VMware pricing has no public rate card — every quote is negotiated — so the useful question is not "what is the price" but "which inputs is my price built from, and which of them can I change".

Three inputs decide your VMware licensing cost under Broadcom's pricing: your core count, the bundle tier, and your term length. Only the first two are really under your control.

The unit is a physical core. Count them all across your VMware infrastructure, then apply the floor.

There are two separate minimums, and confusing them is the most common sizing error we see.

The per-CPU floor: 16 cores. You must license a minimum of 16 for each physical processor, regardless of how many it actually has. A two-socket host with 8-core processors has 16 in reality and licenses as 32.

The order minimum: 72 cores. Since April 2025, Broadcom applies a minimum order quantity of 72 per order line. A single small host does not license as 16 — the order still has to reach 72. Small estates pay for capacity they will never deploy.

The two stack. Count first, then round each processor up to 16, then check the total against the order minimum. Whichever is larger is what you buy.

That is where smaller estates lose money. On a dense modern processor the 16-core floor costs nothing. On older or smaller hardware it can double your billable total against no change in workload — and the order minimum then puts a hard floor under the whole transaction.

Standalone products largely no longer exist. Broadcom VMware collapsed a catalog of more than 160 products into a handful of subscription offerings — the single largest of the licensing changes to follow Broadcom's acquisition of VMware. Most legacy VMware SKUs did not get a like-for-like replacement; they were absorbed into a tier.

Where the legacy products went:

The pattern is worth stating plainly: anything that used to be an à la carte purchase is now a reason to buy a higher tier. If you use NSX at all, you are on VCF. That is the mechanism behind most of the increases people describe as price rises — the tier moved, not just the rate.

The two remaining bundles:

VCF carries a materially higher price per core than vSphere Foundation. VMware's storage entitlement is the detail people miss — an estate with heavy storage and light compute can exceed the included capacity and pay again for the difference.

One constraint worth knowing before you sign: you generally cannot move back down from VCF to a legacy SKU. We watched a public-sector customer discover that mid-negotiation. Once you are on the top tier, downgrading is not a lever you still hold.

Nobody publishes real numbers, and any licensing calculator you find online is estimating. Broadcom's pricing is not published, resellers quote a server license under agreement, and the figure you are offered depends on your size, your tier, your term, and how the negotiation goes. The only reliable way to find out what your estate costs is to request a quote — anyone quoting you a per-core number off a blog post is guessing.

What we can tell you is which way the inputs push. Tier consolidation moves most customers up. The order minimum puts a floor under small estates. The vSAN entitlement is a capacity cliff rather than a flat allowance. And missing your renewal anniversary carries a late-renewal surcharge, so the calendar is a cost input too.

Small businesses feel this hardest. The core minimums are regressive: they cost a large data center with dense processors almost nothing and cost a small estate with modest hardware a great deal. Enterprises with volume also negotiate; a ten-host shop generally does not.

The negotiation happens on the inputs, not the rate.

Audit the real count first. Do not accept an assumed number from a renewal quote. One customer took a planned term from 712 down to roughly 630 simply by reconciling against a hardware refresh that had already happened. Every one removed is removed for the whole term.

Consolidate onto denser hardware. Because the floor is per processor, fewer of them with higher density license far more efficiently than many small ones. This is a hardware decision with a licensing payoff and belongs in the same conversation.

Trade term length for rate. Longer commitments attract better pricing. We have seen five-year terms used specifically to lock a predictable annual figure for budgeting rather than to chase the deepest discount — often the more valuable outcome for a finance team.

Watch how an increase is offset. When an estate crosses a minimum threshold, the additional volume is sometimes offset by a reduced per core rate. That trade is negotiable, and it is worth asking for explicitly rather than accepting the headline figure.

Right-size the tier. If your VMware workloads do not use the full private cloud stack, being quoted for it is expensive. Match the licensing models on offer to what you actually run — existing VMware customers are frequently quoted a tier above their real usage.

Model your exit credibly. Microsoft Hyper-V, Nutanix and Proxmox are real options, and a quantified alternative is the leverage that reliably changes a commercial conversation. It has to be genuine analysis — a bluff is transparent to anyone who negotiates these for a living.

Facing a renewal and unsure what you should be paying? AceMQ handles

VMware licensing and renewal quotes, including capacity audits and

rough-order-of-magnitude modeling before you commit. Request a renewal quote.

The free ESXi hypervisor has come and gone from availability more than once under different owners, including before and after the acquisition, and its status has not been stable. Treat any free tier as unsuitable for production planning — if a workload matters, license it, and if it does not, question why it is on this platform at all.

Perpetual VMware licenses are no longer sold — subscription-based licensing replaced them. Existing ones keep running but receive no support or updates, which for most organizations makes them a compliance problem rather than a saving.

For most estates, optimize rather than migrate. Replacing a hypervisor is a multi-year virtualization program touching every runbook, backup policy and monitoring integration you have, and every VM in the estate. The subscription increase is painful; a rushed migration is usually more expensive once the labor is counted honestly.

That calculus flips for estates that are small, simple, or already substantially in public cloud. Paying full top-tier rates to run a shrinking on-premises remnant of VMs makes little sense when the workload is heading to cloud-native infrastructure anyway.

For the full picture of what changed and why, see what Broadcom changed about VMware licensing.

Once you have a number you trust, the next two questions are practical: how to actually request a quote and, if your term ends in the crowded window, why 2027 renewals need starting early.

Sometimes, and the licence line is the smallest part of the answer. Proxmox VE, Nutanix AHV, Hyper-V and OpenShift Virtualization all run production workloads, so the real comparison is migration engineering time, cutover risk and the automation estate you rebuild against the renewal you can actually negotiate.

We work that comparison in full, with the crossover point and where it sits for different estate sizes, in renew VMware or migrate: the honest cost comparison. If you want the renewal side of the comparison priced properly first, that is a renewal quote.

For the per-core figures and minimum arithmetic from 37 real quotes, see what 37 renewal quotes show about pricing. Comparing terms: 1-, 3- and 5-year terms compared.

How much does VMware licensing cost?

There is no public price list. Pricing is per physical core, subject to both minimums above, sold as a subscription bundle, and quoted under agreement. Because the figure depends on your count, tier and term, the only way to get a real number is to request a quote.

How is VMware licensing calculated?

Count every physical core across all processors running the software, apply a floor of 16 per processor, then check the total against the order minimum. You buy whichever number is larger.

What is the 72-core minimum?

A minimum order quantity of 72 cores per order line, applied by Broadcom since April 2025. It is separate from the 16-per-CPU counting rule and sits on top of it. A single small host cannot be licensed on its own — the order still has to reach 72, which forces smaller estates to buy well beyond what they deploy.

Can I still buy a perpetual VMware license?

No. Perpetual licensing was retired and everything renews on a term. Existing perpetual licenses continue to function but no longer receive support or updates.

What is the difference between VCF and vSphere pricing?

VCF is the full private cloud stack and costs materially more. VVF is the compute-focused tier. They also differ on included vSAN capacity — 1 TiB per core versus 0.25 TiB.

Is ESXi still free?

Availability of a free tier has changed repeatedly and is not something to plan production around. Assume you are licensing anything that matters.

How can I reduce my VMware licensing cost?

Audit actual counts, consolidate onto fewer denser processors, right-size the tier, and trade term length for rate. Reducing processor count usually saves more than any discount you negotiate.

Will license renewals cost more than my old perpetual VMware licenses?

Almost certainly, since new VMware terms move you from an owned asset to an annual subscription. vCenter and the rest of the suite now arrive inside a package rather than separately. How much more depends on core count, hardware density, and term.

A renewal is priced exactly like a new subscription: the same per-core rate for the tier you choose, the same 16-core-per-CPU floor, the same 72-core order minimum, and the same term discounts. There is no separate renewal price list and no loyalty rate. What makes a renewal quote feel different is the starting point. Under the old model, annual Support and Subscription (SnS) ran at roughly a fifth to a quarter of the perpetual licence price. A subscription carries the whole licence every year, so the first renewal quote after a perpetual contract is routinely a multiple of the old SnS line, not a percentage increase on it.

On list pricing, vSphere Foundation (VVF) is about $138 per core per year and VMware Cloud Foundation (VCF) about $344 on a one-year term, with a three-year commitment taking roughly 12% a year off those figures. Actual renewal pricing is negotiated through an authorized partner and moves with three inputs: the tier you renew onto, the licensed core count after the minimums, and the term. The list figure is where the conversation starts, not where it ends.

The renewal-specific costs sit around the licence rather than in it. A lapse in support between contracts means re-instatement rather than renewal. A Partner of Record transfer, if your previous partner lost Broadcom authorization, adds 5–10 business days but no fee. And a renewal that lands inside the last 30 days before expiration leaves no room to compare tiers, which is the most common way a renewal costs more than it should.

Smaller estates carry the minimums hardest, and a renewal is where that shows up in writing. Take two hosts with two 8-core processors each: 32 physical cores. The 16-core floor per processor licenses that as 64. The 72-core order minimum then rounds the order up to 72. At list, 72 cores of VVF is about $9,936 a year and 72 cores of VCF about $24,768 — for an environment that physically has 32 cores. That arithmetic is the reason a small-business renewal quote can be double or triple what the hardware suggests.

Three things reduce it. Renewing onto VVF rather than VCF when NSX, vSAN and the Aria stack are not in use is the largest single lever. A three-year term is the second. Consolidating onto denser processors before the renewal, so the 16-core floor stops costing phantom cores, is the third — and it is only available if the renewal is started early enough to plan hardware around it.

If the estate is genuinely under the 72-core floor and will stay there, the honest comparison is against alternatives, and the renewal quote should show the VMware number beside a migration estimate rather than on its own.

A renewal budget has three inputs and a date. Cores: count every physical core running VMware, round each processor up to 16, and check the total against 72. Tier: VCF if you use the full stack, VVF if you use vSphere and vCenter. Term: one, three or five years, with the longer terms priced below the one-year rate. Multiply the licensed cores by the per-core rate for the tier and term, and you have the list figure to budget against; a partner quote comes in under it.

The date matters as much as the inputs. Start ninety days or more before expiration. That leaves time to get a quote for both tiers, run a Partner of Record transfer if you need one, and decide the term without a support gap. A renewal begun inside thirty days is a renewal at the quoted number. AceMQ returns renewal quotes within 24 business hours from your expiration date and core count, and prints the quote's validity date on it so the budget does not lapse before the decision does.