VMware Licensing Changes: What Broadcom's Model Means for Your Renewal

Perpetual VMware licenses are gone. Everything is now term-based, billed per physical core, with a mandatory minimum of 16 cores per CPU, and the old standalone products have been folded into subscription bundles. For most estates that means a materially higher renewal, and the levers that still move the number are core count, term length, and support scope — not the list price.

Here is how the Broadcom VMware licensing subscription model works, when the product changes landed, and what to do before your renewal date.

Three of VMware's changes matter more than the rest:

Perpetual licenses were retired. You no longer own anything. Every entitlement is a term that expires, and lapsing means losing support and access to updates rather than simply staying on an old build.

Pricing moved to physical cores. The unit is no longer the socket or the VM — it is the core, counted across every physical processor in every host running the product.

Standalone SKUs were consolidated. Broadcom folded VMware vSphere Standard, Enterprise Plus, Essentials Plus, and most separately purchased components into a small number of bundles built around VMware Cloud Foundation and vSphere Foundation. Buying just the one VMware product you need is largely no longer an option, and vCenter now arrives inside a suite rather than as a line item.

The acquisition of VMware closed in late 2023, and the move to subscription was announced almost immediately after. Through 2024 the portfolio was consolidated and the partner program was rebuilt. By 2025 most enterprises had hit their first post-acquisition renewal date, and through 2026 the remaining legacy estates are reaching expiry.

The practical implication: this is no longer a change you can wait out. If you are still on prior owned entitlements, your negotiation is happening now rather than at some future point.

The mechanic that surprises people is the floor. Per Broadcom's own guidance, you must license a minimum of 16 physical cores for each CPU, regardless of how many cores that processor actually has.

A host with two 8-core processors has 16 real cores but licenses as 32. On estates built from lower-core-count hardware, that gap alone inflates licensing costs well beyond what the estate consumes. Some advisory firms also report a broader minimum purchase — a 32-core or 72-core minimum purchase depending on channel and program — though this is not stated in the published core-counting guidance, so confirm it against your own quote rather than assuming it.

Storage is entitled differently again. Capacity comes bundled per core licensed:

Additional capacity is purchasable beyond that entitlement, which is where estates with heavy storage and light compute get caught.

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

Broadcom does not publish a rate card, and any figure you find online is an estimate. What is consistent is direction: tier consolidation moves most customers up, the core minimums put a floor under smaller estates, and the storage entitlement is a capacity cliff rather than a flat allowance. The only way to know what your estate costs is to request a quote.

SMBs are hit hardest. The 16-core floor is regressive — it costs a large data center with dense processors almost nothing and costs a small estate with modest hardware a great deal. If you run a handful of hosts, model your specific configuration rather than applying any published percentage.

Service providers face a separate problem. The partner channel was restructured, tiers were consolidated, and providers who resold VMware at thin margins found the economics rewritten underneath them. If you buy through a provider rather than direct, ask how their own cost base changed before you accept their quote as market rate.

The negotiation happens on the inputs, not the rate card.

Audit your real core counts first. Do not accept an assumed number. In one engagement a customer took a planned term from 712 cores down to roughly 630 simply by reconciling the count against a hardware refresh that had already happened. Every core removed is removed for the whole term. Treat this as capacity planning, not procurement paperwork.

Consolidate onto denser hardware. Because the floor is per processor, fewer processors with higher core counts license more efficiently than many small ones. This is a hardware decision with a licensing payoff, so it belongs in the same conversation.

Trade term length for rate. Longer commitments attract better pricing. A three-year commitment is the common baseline, and 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.

Separate support from the subscription and review it on its own merits rather than accepting the bundled figure.

Model your exit credibly. Microsoft Hyper-V, Nutanix, Proxmox, and Red Hat OpenShift Virtualization are real alternative platforms, and Microsoft Azure offers a migration path for VMs leaving the data center entirely. A quantified exit strategy is the only leverage that reliably changes a commercial conversation with an account team. It has to be genuine analysis — a bluff is transparent to anyone who negotiates these for a living.

Check your buying path. Portable subscriptions can be purchased directly from Broadcom in some programs, and contracts routed through the partner channel require deal registration handled correctly in the Broadcom portal. Getting either wrong late in a cycle costs discount, not just time.

For most organizations the honest answer is optimize. Replacing your hypervisor is a multi-year program touching every runbook, backup policy, monitoring integration, and operational habit your team has. Live migration behaviour, observability tooling, and automation all have to be rebuilt on the new platform. The subscription increase is painful; a rushed migration across virtualization platforms is usually more expensive once the labour is counted honestly.

That calculus flips for estates that are small, simple, or already substantially in public cloud. If most of your compute is heading to a hybrid cloud footprint anyway, paying full top-tier rates to run a shrinking private cloud remnant makes little sense — one customer we worked with is targeting roughly 75 percent cloud against 25 percent on-premises and sizing the commitment to the destination, not the starting point. Equivalent cloud service options are worth modelling in that scenario.

Two operational notes that rarely appear in pricing discussions but change the picture. Air-gapped and classified environments have a specific activation path — disconnected-mode licensing works, but it needs planning rather than discovery during deployment. And with RAM prices where they are, memory tiering onto NVMe can hold total cost down even as licensing rises, which sometimes matters more than the line item everyone is staring at.

Facing a VMware contract and unsure what you should actually be paying? AceMQ handles VMware licensing and renewal quotes for enterprise customers, including core audits and rough-order-of-magnitude modelling before you commit. Request a renewal quote.

Are perpetual VMware licenses still available?

No. That model was retired and all entitlements now renew on a term. Existing owned licenses continue to function but no longer receive support or updates.

How is VMware licensing calculated now?

Per physical core across all processors running the product, with a mandatory minimum of 16 cores per CPU. A processor with fewer than 16 cores is still billed at 16.

When did the VMware licensing changes take effect?

The subscription move was announced shortly after the acquisition closed in late 2023, with portfolio consolidation running through 2024. Most enterprises hit their first affected contract in 2025 or 2026.

What happened to vSphere Standard and Enterprise Plus?

They were consolidated into the Foundation suites. Most standalone SKUs, including Essentials Plus, are no longer sold separately.

Can I downgrade from VCF to a cheaper bundle at renewal?

Generally no. Moving down from VCF to a legacy SKU is not typically available, which makes the initial choice difficult to reverse. Confirm this before committing.

How much vSAN capacity comes with a subscription?

VCF includes 1 TiB of vSAN capacity per core licensed. VVF includes 0.25 TiB per core, rounded up. Additional capacity is purchased separately.

Will my VMware costs rise?

Almost certainly, since you move from an owned asset to an annual subscription and most estates also move up a tier. How much depends on your core count, hardware density and term, which is why it has to be quoted rather than estimated.

What are the main alternatives to VMware?

Microsoft Hyper-V, Red Hat OpenShift Virtualization, and comparable hypervisors are the platforms most often evaluated, alongside migrating workloads to Microsoft Azure or another cloud environment. Each carries real migration cost, so model it properly before treating it as a threat in negotiation.

What is the fastest way to reduce VMware licensing costs?

Audit actual core counts, then consolidate onto fewer, denser processors. Because the 16-core minimum applies per processor, reducing processor count often saves more than any discount you negotiate.