VMware Licensing After Broadcom: The Complete Guide

Broadcom completed its acquisition of VMware on 22 November 2023. Within six weeks, the licensing model that customers had operated against for two decades was replaced. The transition that followed has been the largest enterprise-software licensing change since the introduction of subscription pricing for productivity software more than a decade ago. The implications are not finished landing — customers are still discovering them in audit findings, renewal proposals, and migration cost models in May 2026.

This guide is the consolidated picture, written for customers who need to make decisions about their VMware estate under the current licensing regime. It covers what the catalogue actually contains, how pricing actually works, how the partner programme channels customer interactions, how support has changed, what audit risk looks like in the new model, and what the realistic options are for customers who are not satisfied with where this has landed. Where details are still evolving — and several still are — that is flagged.

What changed and when

The headline change is the end of perpetual licensing. From December 2023, VMware no longer sells perpetual licenses for any product in the core compute, storage, networking, and cloud-management portfolio. Existing perpetual licenses remain valid in customer environments but are no longer eligible for new Support and Subscription (SnS) contracts after their existing SnS expires. Customers with perpetual licenses can run them indefinitely, but only with active support if they have rolled them into a subscription bundle.

The second headline change is the collapse of the catalogue. The pre-acquisition VMware catalogue contained dozens of standalone SKUs across vSphere, vSAN, NSX, Aria, Tanzu, and adjacent products. The post-acquisition catalogue contains two principal bundles — VMware Cloud Foundation (VCF) and VMware vSphere Foundation (VVF) — plus a small set of standalone add-ons. Standalone vSphere, standalone vSAN, and standalone NSX are no longer sold separately to most customers. Some standalone availability remains for very small environments and for specific edge cases (for example, vSphere Standard for very small deployments) but is the exception, not the rule.

The third headline change is per-core pricing. The previous per-CPU model has been replaced with per-core pricing across the new bundles. The conversion ratio used at renewal events is roughly sixteen cores per CPU — a number designed to approximate prevailing server core counts but which, in practice, increases the unit count for customers running high-core-count modern servers. The combination of subscription pricing, per-core measurement, and bundle-based catalogue has produced what most customers experience as a material price increase even before any list-price action.

The fourth and arguably most consequential change is the partner-programme restructure. The pre-acquisition VMware partner programme had tens of thousands of authorised resellers worldwide. The post-acquisition Broadcom Advantage Partner Program retains a much smaller set — by mid-2024 most observers reported a reduction of roughly seventy to eighty per cent from the pre-acquisition partner base — and channels most enterprise transactions through this smaller set of named partners. For customers, this means fewer competitive bids on renewals and a much closer commercial relationship between Broadcom and the customer.

The two bundles: VCF and VVF

The replacement catalogue centres on two bundles. Understanding what each contains, who each is for, and how they price relative to each other is the first thing every VMware customer should be able to do.

VMware Cloud Foundation (VCF)

VCF is the flagship bundle. It includes vSphere (the compute hypervisor), vSAN (the software-defined storage layer), NSX (the network and security layer), and the Aria suite (the management and automation stack). VCF is positioned for customers building a private cloud or running a substantial multi-product VMware estate. It is the bundle Broadcom most prefers to sell, because it is the largest in dollar terms and because it most fully extracts value from customers who would otherwise have mixed-and-matched standalone products.

VCF is priced per core, with a minimum core count that has shifted across the catalogue's lifetime. Editions have varied — Standard, Advanced, Enterprise — with the principal differences sitting in the Aria components and certain advanced NSX features. For most customers, VCF Advanced is the central commercial proposition.

VMware vSphere Foundation (VVF)

VVF is the lighter bundle. It contains vSphere, a quota of vSAN capacity (typically 100 GB per core in current SKUs), and the Aria management components — but not NSX, and with reduced Aria functionality compared to VCF. VVF is positioned for customers who run vSphere as their primary virtualisation layer but who do not use vSAN or NSX as full enterprise software-defined infrastructure.

VVF is also priced per core. Its price point is meaningfully lower than VCF per core, and for customers without substantial vSAN or NSX requirements it is usually the better economic choice. Customers who have historically licensed only vSphere — by far the largest share of the VMware installed base — find VVF the closest equivalent to their previous purchase pattern.

Standalone availability

Outside the two bundles, the standalone catalogue is intentionally limited. vSphere Standard remains available for small deployments. Standalone Aria products are available in some configurations but are increasingly funnelled into VCF. Standalone NSX exists for some specific networking use cases. Standalone Tanzu and the application-platform products have been reorganised under a separate Tanzu Platform business unit with its own commercial structure.

The standalone catalogue is not the future direction of the licensing model. Customers should expect any remaining standalone SKUs to be progressively retired or repriced unfavourably to discourage their use. Planning that depends on standalone availability is planning against the direction of the catalogue.

Pricing mechanics: per core, per year, per bundle

VMware licensing under Broadcom is denominated in core-years. A customer with a thousand cores on a three-year VCF subscription is purchasing three thousand core-years, priced at the per-core rate negotiated for their environment. The mechanics are simple but the consequences are large.

Per-core conversion from legacy entitlements

Customers renewing from legacy per-CPU entitlements convert at a published ratio. The ratio has shifted across the catalogue's lifetime — early versions converted at one CPU equals eight cores, later versions at one CPU equals sixteen cores, with some negotiated outcomes ranging between the two. The conversion ratio is the single largest determinant of renewal cost for customers moving from legacy entitlements to current bundles, and it is negotiable.

Minimum core counts

Most current bundles carry a minimum core count per CPU socket — typically sixteen cores per socket — even if the physical socket has fewer cores. The minimum has the effect of increasing the per-server licensing cost for customers running older or smaller-core-count hardware. The minimum is published in the SKU terms and applies to any host running the licensed bundle.

Subscription term and price protection

Subscription terms are typically three or five years. The headline per-core price typically improves with longer terms. Renewals after the initial term, however, do not always reflect the initial discount — without explicit price-protection language, renewals can move significantly upward. Securing renewal pricing at a defined uplift over initial pricing is one of the most consequential negotiation points in any VCF or VVF agreement.

List versus negotiated pricing

The published list price is rarely the price customers actually pay. Negotiated discounts vary widely — by deployment size, by strategic value to Broadcom, by competitive alternatives, by timing relative to Broadcom's quarter and fiscal year. In our engagement data, discounts in the twenty-to-fifty per cent range against list are achievable for mid-size and larger customers; smaller customers see less discount but are generally paying for smaller bundles, so absolute exposure is lower.

Support changes: SnS, Severity 1, and the new escalation paths

Support has been restructured alongside licensing. Three changes matter most.

First, support is now bundled into subscription. Standalone Support and Subscription contracts attached to perpetual licenses have been phased out. Customers with perpetual licenses who want active support must either renew within a subscription bundle or accept that their perpetual licenses run unsupported.

Second, support tiers have been simplified. The pre-acquisition Production Support, Premier Support, and Mission Critical Support tiers have been consolidated. Current support is structured around standard subscription support and a higher-tier offering for enterprise customers. The functional differences sit mainly in response-time commitments for Severity 1 issues and in the availability of named technical account managers.

Third, the support escalation paths have been rebuilt. Customers who previously had named VMware support contacts have, in most cases, been re-mapped to Broadcom support workflows. The customer experience of escalation in the new structure has been variable. Customers reporting issues have noted longer initial response times in non-Severity-1 cases, though Severity 1 response has largely been preserved.

The partner programme: fewer partners, closer relationships

The Broadcom Advantage Partner Program is structured around named partners with defined territory and customer assignments. Most enterprise transactions flow through a named partner. For customers, the partner is both a commercial intermediary and a service-delivery partner — many partners now offer implementation and managed services around VCF and VVF deployments.

The partner-programme restructure has two practical effects on customers. First, competitive bidding on renewals is much harder than it used to be. The named partner for a customer's region and segment is typically the only realistic counterparty for a competitive bid on a Broadcom renewal. Second, the partner's commercial latitude is constrained. Partners cannot typically improve materially on Broadcom's directly negotiated pricing, which means the negotiating game with Broadcom must be played directly with Broadcom rather than via partner price competition.

This has changed the economics of the renewal negotiation. Customers who used to drive material pricing improvements through partner competition now have to rely on contractual negotiation, alternative-vendor leverage, and timing as their principal commercial tools.

Audit risk in the new model

Audit risk in the post-acquisition era is higher and more systematic than it was under VMware directly. Three drivers explain the increase.

First, Broadcom has invested in compliance staffing and methodology. The audit organisation is larger, more analytically capable, and more strategically aligned with commercial objectives than the pre-acquisition VMware compliance team was. Second, the move to subscription has created a clearer commercial incentive for audits — every finding can be settled as a subscription conversion, which advances the strategic priority. Third, the partner-programme restructure has reduced the informal relationships that historically softened compliance interactions. Audits in the current era proceed more procedurally and reach findings faster.

The consequence for customers is that compliance posture matters more than it did. The audit risk is not theoretical — current audit volume across the customer base is the highest it has been in VMware's history. Customers who have not reconstructed their entitlement position in the last twelve months are at higher risk than they realise. Our companion guides on the audit process, audit triggers, and scope limitation cover the audit defence side of this in detail.

The renewal decision framework

For most customers, the central licensing question is the renewal decision: what to commit to at the next contract event, and on what terms. The decision has four major components.

Bundle selection

The first decision is VCF, VVF, or (where still available) standalone. The decision should be made on three-year forward requirements, not current usage. Customers committing to VCF are typically committing to a private-cloud strategy with multi-product VMware adoption. Customers committing to VVF are typically committing to vSphere as the primary virtualisation layer without substantial vSAN or NSX adoption. Customers who can credibly commit to neither — typically because their forward strategy includes migration off VMware — should structure their next renewal as a transitional rather than strategic commitment.

Term length

Three-year terms are most common; five-year terms are pushed for larger commitments. Longer terms attract larger headline discounts but lock in pricing and platform direction for longer. The decision is essentially a question of strategic certainty: customers who are certain about their VMware direction can capture the longer-term discounts; customers who are not certain should take shorter terms even at higher headline pricing.

Core-count commitment

Core counts are typically committed in advance for the term. Over-commitment is expensive; under-commitment requires mid-term true-up at less favourable pricing. The committed core count should reflect realistic three-year-forward consumption, with conservative growth assumptions and explicit provisions for divestiture-driven reductions.

Price protection

The renewal-time pricing for the term after this one is one of the most consequential contractual variables. Without explicit price-protection language, the next renewal could move ten, twenty, or fifty per cent upward. Securing a defined uplift cap — typically five to ten per cent annually, with a multi-year cumulative cap — is the single most valuable contractual provision most customers can secure.

Migration paths off VMware

For a meaningful and growing subset of customers, the right answer is to plan migration off VMware rather than to renew on Broadcom's terms. The realistic migration options have matured since the acquisition closed.

Microsoft Hyper-V

Hyper-V is the most direct enterprise alternative for customers with substantial Windows Server estates. The integration with Windows Server licensing, the maturity of System Center Virtual Machine Manager and Microsoft's broader management stack, and the strength of Azure integration make Hyper-V the natural default for Microsoft-centric environments. Migration timelines are typically twelve to twenty-four months for mid-size environments.

Nutanix AHV

Nutanix AHV is the strongest enterprise alternative for customers seeking a hyperconverged platform broadly equivalent to VCF. AHV bundled with Nutanix's storage and management stack provides VCF-comparable functionality with a different commercial model and a substantially different operational profile. Migration is meaningful in cost terms but tractable in eighteen-to-thirty-six month timelines.

Red Hat OpenShift Virtualization

OpenShift Virtualization (formerly Red Hat's CNV) is increasingly viable for customers committed to Kubernetes-centric application platforms. The maturity for traditional enterprise virtualisation workloads has improved meaningfully through 2024 and 2025, and Red Hat has invested in migration tooling from VMware environments. The cost structure is attractive for customers already on Red Hat platforms.

Proxmox VE

Proxmox VE is the open-source alternative receiving the most attention from cost-pressured customers. Operationally robust and licensed under a permissive model, Proxmox has acquired meaningful enterprise adoption since the Broadcom acquisition. Migration tooling has matured. For specific use cases — particularly mid-market enterprises with capable Linux operations teams — Proxmox represents a credible migration target.

Cloud-native rehoming

A subset of VMware workloads can be migrated to public cloud native services without preserving the VMware abstraction. AWS, Azure, and Google Cloud all offer migration tooling for VMware workloads. The economic case depends heavily on workload profile — steady-state workloads typically run more expensively in public cloud than in on-premises VMware; bursty or variable workloads often run more cheaply.

The standalone-vSphere question

For customers running only vSphere, the most pressing licensing question is whether the cost increase under VVF makes the workload still appropriate for VMware. A typical pre-acquisition vSphere Standard customer pays roughly two to three times more per core under current VVF pricing than under their previous arrangement, after accounting for support and including the conversion ratio impact. For some customers this is acceptable; for others it triggers migration evaluation.

The decision depends on the alternative cost. Hyper-V on existing Windows Server estates often costs less than VVF for equivalent functionality. Proxmox costs substantially less for capable customers. The cost saving has to be weighed against migration cost and operational disruption. In general, the threshold where migration becomes economically rational is lower than most customers initially assume.

What to do in the next 90 days

For most customers reading this guide in May 2026, three practical actions are appropriate inside the next ninety days.

First, reconstruct your entitlement position and your deployment position. The two will not match. Understanding the gap is the foundation for any subsequent decision — renewal, audit defence, or migration.

Second, model your renewal cost under the current bundles. Run the calculation for VCF and for VVF. Compare both to the cost of your current entitlements at current support rates. The comparison will tell you what your renewal exposure looks like and which bundle direction is appropriate.

Third, evaluate at least one realistic migration alternative. The point is not necessarily to migrate; it is to have a credible alternative to use as leverage in renewal negotiation. Customers with a serious migration alternative consistently land renewals on better terms than customers without one.

What still might change

Several aspects of the licensing model are still evolving as of May 2026. Watch for changes in the following areas.

The standalone catalogue may contract further. Several standalone SKUs remain available primarily for legacy reasons; their continued availability is not guaranteed. The Aria components within VCF have continued to reshape across catalogue revisions, with new functionality added and some legacy functionality consolidated. The pricing for the Tanzu Platform business unit, which is operating under a separate commercial structure from VCF and VVF, has been evolving and is likely to continue to do so.

The partner programme is also still settling. The named-partner model has stabilised but the specific partners assigned to specific customer segments and territories remain subject to change. Customers should not assume their current named partner will remain their named partner across the term of a multi-year subscription.

Regulatory and competition-policy activity is ongoing. Multiple jurisdictions have opened or continued inquiries into post-acquisition licensing practices and partner-programme restructuring. The outcomes are uncertain but could materially affect the licensing model.

Related reading

For deeper detail on specific aspects of the new licensing model, see our companion guides on VMware pricing before and after the acquisition, vSphere 8 licensing, the 2026 licensing policy, and migration cost analysis. For the audit-defence dimensions of the new model, see our VMware audit defence guide and the broader audit process explainer.