Broadcom and VMware, read in full.

Why Broadcom changed the deal.

In November 2023 Broadcom closed its acquisition of VMware and re-set the commercial model with immediate effect. Perpetual licences and Support & Subscription contracts ceased to be sold from late 2023. Eighty-plus product SKUs were rationalised to two principal bundles: VMware Cloud Foundation (VCF) and VMware vSphere Foundation (VVF). Pricing moved from per-CPU to per-core with a sixteen-core minimum per CPU. Distribution moved from a wide partner ecosystem to a select named-channel direct-billed posture. Term moved from annual support to subscription on three-year and five-year terms.

The implication for procurement is that every VMware renewal under Broadcom is a new commercial conversation. The buyer no longer renews an existing entitlement; the buyer transitions an estate from the legacy commercial model to the new subscription model, at the new commercial economics. An Admodum Broadcom / VMware engagement therefore models the transition as a strategic decision: stay on the new subscription model, migrate workloads to an alternative hypervisor, or split the estate.

This pillar groups the firm’s Broadcom / VMware commentary into ten editorial sections. Each section names the load-bearing mechanic, links the deeper spoke articles, and points to the practice page, the relevant white papers and the knowledge hub for the buyer who wants the engagement methodology.

VCF and VVF: the new portfolio.

VMware Cloud Foundation (VCF) is the premier Broadcom bundle. VCF includes vSphere Enterprise Plus, vSAN Enterprise, NSX (with the Distributed Firewall, Gateway Firewall and Advanced Load Balancer), Aria Suite (the management surface, formerly vRealize) and HCX (the workload-mobility surface). VMware vSphere Foundation (VVF) is the lower-tier bundle: vSphere Enterprise Plus, Aria Suite Standard, no vSAN, no NSX.

The buyer-side question is which bundle reads against the deployed estate. A buyer running plain vSphere with no vSAN, no NSX and minimal Aria use is over-paying on VCF; a buyer running the full software-defined data centre with vSAN, NSX micro-segmentation and Aria Operations is under-priced on VVF. The Admodum methodology audits the deployed feature use against the bundle entitlement.

The full reading sits in the Broadcom VMware Transition paper. The two-bundle architecture replaces a previous eighty-plus SKU catalogue; the simplification reduces ordering friction but removes the legacy per-product re-sizing levers.

Per-core licensing and the conversion math.

The Broadcom commercial model prices VCF and VVF per physical core, with a sixteen-core minimum per CPU. A two-CPU host with twenty-four cores per CPU bills against forty-eight cores. A two-CPU host with twelve cores per CPU bills against thirty-two cores (the sixteen-core minimum applies to each CPU). The legacy per-CPU model billed against two CPUs regardless of core count.

The conversion math is the buyer-side starting point. A buyer running dense modern processors (32-core, 64-core, 96-core CPUs) sees a multi-digit per-core cost against the legacy per-CPU economics, even before the published Broadcom rate-card change. A buyer running older lower-core CPUs sees a smaller transition but a larger minimum-charge effect.

The Admodum methodology runs the conversion math against the actual deployed estate (every host, every CPU, every core), models the transition cost against the legacy renewal cost on a multi-year basis, and identifies the workload-density opportunities where consolidation onto fewer, denser hosts reduces the core count. The full reading sits in the VMware Exit Architecture paper.

The renewal posture under Broadcom.

Broadcom’s renewal posture has hardened across the post-acquisition period. Multi-year terms are increasingly the default ask; published support tiers have been reduced; the legacy partner-led renewal motion has been replaced by direct-billed accounts above a named revenue threshold. Discount discipline has tightened; flexibility on bundle definition (VCF or VVF) is now the principal commercial lever.

The buyer-side methodology runs a four-axis read on every Broadcom renewal. The bundle axis (VCF or VVF, with feature-use evidence). The term axis (one-year, three-year, five-year, against the buyer’s strategic transition plan). The discount axis (against the published rate card and the buyer’s peer-band evidence). The exit axis (a credible alternative-hypervisor migration cost that bounds the Broadcom commercial position).

The fourth axis is the load-bearing one. Without a credible exit, the buyer’s renewal leverage is small. With a credible exit (a documented Nutanix / OpenShift / Proxmox migration plan with quoted costs and a realistic timeline), the buyer’s renewal leverage is materially larger.

Exit architecture and the alternatives.

The buyer-side exit catalogue runs across five principal alternatives. Nutanix AHV (the AOS / AHV stack, with Nutanix Cloud Manager and Nutanix Disaster Recovery) is the closest functional analogue to VCF for mid-sized enterprise estates. Red Hat OpenShift Virtualisation (running KubeVirt under OpenShift) is the natural destination for buyers already running Red Hat OpenShift and ready to consolidate VMs onto the container platform. Proxmox Virtual Environment is the open-source destination for cost-sensitive workloads. Microsoft Azure Stack HCI (now Azure Local) is the destination for buyers integrated into the Microsoft estate. The hyperscalers (VMware Cloud on AWS / Azure VMware Solution / Google Cloud VMware Engine) are the lift-and-shift destinations.

The buyer-side methodology runs a workload-by-workload migration analysis. Some workloads (high-IO databases, regulated workloads with named hypervisor requirements, third-party-application certifications tied to vSphere) cannot migrate; these stay on Broadcom under the new model. Other workloads (general-purpose virtualisation, development and test, internal IT services) move readily to an alternative.

The full reading sits in the VMware Exit Architecture paper. The Admodum methodology builds the exit catalogue against the buyer’s named workloads, with documented migration costs, performance evidence and timeline.

Migration economics, in numbers.

A VMware-to-alternative migration carries three cost categories. The licence cost of the destination platform (Nutanix subscription, OpenShift subscription, Proxmox support contract or Azure Stack HCI per-core fees). The migration project cost (the implementation partner, the architectural design, the migration tooling, the in-house team time). And the operational cost of the destination platform (the platform-engineering capability that VMware previously absorbed).

The buyer-side methodology models the three categories on a five-year basis against the Broadcom new-model renewal cost. The break-even is typically eighteen to thirty months for general-purpose workloads, longer for specialised workloads. The model is sensitive to scale (large estates absorb the migration cost more readily) and to the buyer’s existing platform capability (a Red Hat-mature buyer migrates to OpenShift Virtualisation more cheaply than a buyer learning Red Hat from scratch).

The migration is rarely the whole-estate option. The Admodum recommendation is typically a split-estate: the workloads that can migrate at favourable economics migrate; the workloads that cannot stay on Broadcom under the new model at the negotiated renewal terms.

The OEM channel collapse.

Broadcom dissolved much of the legacy VMware partner ecosystem in the months after the acquisition. White-label OEM agreements with named server vendors (Dell, HPE, Lenovo, Cisco UCS) were terminated and re-negotiated under Broadcom’s direct-billed terms. The named OEM-bundled VMware licences (the ‘included’ vSphere on Dell PowerEdge purchases, the HPE-branded VMware bundles) ceased to be available under the previous packaging.

The procurement implication is that any buyer renewing OEM hardware and expecting the historical VMware bundle should plan for a separate Broadcom commercial conversation. The OEM hardware refresh now requires an independent VMware licensing negotiation; the previous bundle is no longer the procurement default.

The named-channel partners that survived the rationalisation (the Broadcom Pinnacle and Premier tiers) operate under tighter Broadcom commercial discipline; the legacy partner-led discount flexibility has narrowed materially.

Audit and compliance posture.

Broadcom has, post-acquisition, intensified compliance discipline across the VMware estate. The legacy partner-led informal-audit posture has shifted toward more direct Broadcom-led compliance verification. The per-core licensing model creates a new compliance surface: the deployed core count against the contracted core count is the primary audit read.

The buyer-side compliance posture is therefore the same discipline the buyer applies under any per-core publisher. An audit-quality inventory of every host, every CPU, every core, every active vSphere licence, every NSX entitlement use, every vSAN deployment. The reconciliation against the contracted entitlement, the documented evidence of every change since the last reconciliation and the named-contact protocol for any Broadcom outreach.

The full methodology runs inside the Audit Defence programme. The post-acquisition compliance environment is materially different from the legacy VMware environment; the buyer-side discipline has had to harden in step.

The renewal cycle.

The Broadcom VMware commercial relationship now runs on multi-year subscription cycles: typically three-year and increasingly five-year. The renewal window opens nine to twelve months before contract anniversary; the negotiation runs against Broadcom’s fiscal-year-end calendar (31 October) with named quarter-end leverage; the signature closes inside the publisher’s named fiscal quarter.

The Admodum Broadcom / VMware practice runs the cycle across every engagement, under one of three commercial frameworks: fixed fee for scoped deliverables, contingency / gainshare for measurable savings and annual retainer for continuous coverage across the cycle.

The Broadcom knowledge hub aggregates the wider reading: the practice page, the two white papers, named case studies, blog analysis and an FAQ block for the buyer who is two clicks from a senior advisor call.

Reading list.

The pillar groups Broadcom / VMware commentary into ten sections above. The spoke band below opens the forty named articles inside the cluster, each one a deep-read on a specific mechanic. The white papers below sit alongside the pillar as the methodology deliverables; the practice page sits alongside as the engagement entry point.

A short follow-up checklist for the reader who is closing this page: visit the Broadcom / VMware practice for the engagement entry point; visit the Broadcom knowledge hub for the aggregated reading; request the two Broadcom / VMware white papers (Transition, Exit Architecture); or open a private conversation with a senior Admodum advisor through /contact/.