Choose a Broadcom VMware partner on its ability to manufacture leverage, because since the 2023 acquisition reset the commercial rules — perpetual sales ended, the portfolio moved to per-core subscriptions with a 16-core-per-CPU floor, and point products were folded into the VMware Cloud Foundation bundle — the renewal number is set by what Broadcom believes you can walk away from, not by a price list. The firm you want has built credible migration alternatives, right-sized core counts before a quote was issued, handled enforcement letters from the buyer’s side, and earns nothing from VMware resale.
Published 2 February 2026 · Last reviewed 9 March 2026
Broadcom’s acquisition of VMware in late 2023 rewrote the commercial model in one stroke. Perpetual licenses are no longer sold; entitlement is a time-boxed, per-core subscription with a 16-core minimum per CPU, so lightly populated sockets are licensed to the floor. Point products were consolidated into bundles — VMware Cloud Foundation (VCF) at the full-stack end, vSphere Foundation (VVF) and the slimmer vSphere editions beneath it — which lifts the entitlement baseline at every renewal. The channel was simultaneously narrowed to an invitation-based partner program, and many mid-size accounts were moved to distributor-led servicing. The combined effect, widely reported by buyers and described factually here, is renewal arithmetic that can multiply prior spend even where the estate has not grown.
Enforcement moved with the model. Organisations running expired-perpetual VMware — particularly those still consuming patches without an active contract — have received cease-and-desist letters asserting infringement and explicitly reserving audit and legal rights, while a lapsed subscription can carry a reinstatement uplift on top of back-dated fees. Cloud-connected components can report deployment data home, narrowing the room to self-correct quietly. A Broadcom VMware engagement is therefore rarely a single service: it is a platform decision (stay, shrink or migrate) wrapped inside a renewal negotiation, often with an enforcement response running alongside — and the timing logic in when to bring in help applies with unusual force, because the leverage work takes longer than the talks.
General information for buyers, not legal or licensing advice; no firms are named here. The directory, filtered to Broadcom VMware, lists the firms covering this vendor — alphabetical, balanced pros and cons, listed not ranked.
A credible alternative, built and priced. Broadcom’s position strengthens or weakens with one variable: whether your threat to leave is real. The capability to test is not negotiation theatre but migration engineering — can the firm produce a costed, timelined business case for moving some or all of the estate to an alternative hypervisor or cloud platform, defensible enough to put on the table? Firms that have actually run such migrations (or carved out workloads to shrink the renewal) negotiate differently from firms that have only read about them. The point is not that you must leave; it is that the modelling must be real enough that staying becomes a choice with a price.
Core arithmetic before the quote. Per-core licensing with a 16-core-per-CPU floor rewards estates that consolidate onto fewer, fuller sockets and punishes sprawl. A practiced partner audits core counts, socket population and cluster design before Broadcom sizes the deal, and can show engagements where re-platforming or host consolidation cut the licensable baseline ahead of the negotiation. That work is the cheapest money in the entire exercise.
Bundle fluency. Whether you need the full VCF stack or can hold the line at vSphere Foundation or a slimmer edition is the structural question inside most renewals — the components you will never switch on are the margin. The trade-offs are unpacked in VCF vs vSphere Foundation; a partner should model both from your deployment data and be able to point to at least one engagement where it advised the smaller package.
Enforcement craft. If a cease-and-desist letter is on the desk, response sequencing matters: what is acknowledged, what is measured, what is negotiated, and when counsel joins. Estates weighing a freeze on perpetual versions or third-party support need the licensing consequences mapped honestly — the factual positions on both sides are laid out in perpetual vs subscription — and a partner should be able to describe, with anonymized examples labelled indicative, how it has landed those situations without litigation.
Term and structure, not just discount. Multi-year term length against price protection, true-up treatment, reinstatement waivers, divestiture and ramp clauses: on a vendor whose pricing power is high, the durable wins are structural. Ask what structure the firm has moved on a Broadcom paper, not what percentage it once achieved. The Broadcom VMware vendor hub maps the enforcement landscape; VMware license negotiation lists the firms doing this work.
| Your position | How it is licensed | What a partner verifies before anything is signed |
|---|---|---|
| VCF subscription | Per-core, full stack (vSphere, vSAN, NSX, management) bundled; 16-core minimum per CPU | Which bundled layers are actually deployed; whether VVF or a slimmer edition covers real usage; core and socket right-sizing across clusters |
| vSphere Foundation / vSphere editions | Per-core compute subscription, narrower feature set | Whether feature needs genuinely force an upgrade path; renewal uplift exposure; add-on pricing vs bundle pricing on your numbers |
| Active perpetual + support | Legacy license plus support contract Broadcom is retiring | What happens at support expiry; subscription-conversion terms vs freeze, third-party support or migration — each modelled with its risks |
| Expired perpetual | Valid for licensed versions; no patch entitlement | Patch-consumption exposure (the cease-and-desist trigger); reinstatement arithmetic vs alternatives; response plan if a letter arrives |
The fourth row is where enforcement concentrates. If that is you, the engagement starts as audit defense and becomes a negotiation; the worst sequencing is to negotiate first and measure later.
The provider landscape divides on one fact: who else pays them. Independent boutiques earn fees only from buyers; several built deep VMware practices when the acquisition hit and have live migration and enforcement-response experience — independence is the structural advantage, bench depth varies. Resellers and program partners know the deal desk and the bundle mechanics intimately, but Broadcom’s narrowed, invitation-based channel makes partner status itself a revenue relationship with the vendor; advice that lands on a bigger bundle deserves an extra look when the adviser books margin on it — a factual trade-off to be disclosed, never assumed away. Big Four practices bring procurement scale, benchmark libraries and board-room weight, with the usual alliance-disclosure question. Law firms belong in the picture earlier than usual here, because cease-and-desist letters are legal instruments; the working pattern pairs counsel with a commercial licensing team rather than substituting one for the other — the division of labour is mapped in lawyer or consultant. SAM tooling counts cores and tracks versions well, but a dashboard is not a migration business case.
On fees: fixed-scope, day-rate, retainer and gain-share all appear in VMware work. Gain-share priced against “savings vs initial quote” deserves scrutiny on this vendor in particular, because opening quotes can be high enough that a large “saving” is compatible with a poor outcome; the incentive mechanics are unpacked in fee models explained. No prices are published on this site.
Red flags, VMware edition: a savings percentage quoted before anyone has read your core counts; a migration threat the firm cannot cost or timeline when asked; “we know people at Broadcom” offered as the method; undisclosed resale, referral or partner-program revenue; advice to ignore a cease-and-desist letter; and any plan that treats the renewal date as the start of the work rather than the deadline for it.
1. “Do you, or any affiliate, earn revenue from Broadcom — resale, referral or partner-program incentives — today?” In writing, first; the full conflicts protocol is in the independence test.
2. “Walk us through a renewal you ran after the model change: what the opening position was, what moved, and what made it move.” Practiced firms answer with leverage mechanics, not adjectives.
3. “Build the outline of our migration alternative: what would you model, how long would it take, and when has a client of yours executed rather than merely threatened it?”
4. “Where in our cluster design would you look for licensable cores we are wasting against the 16-core floor?” A real answer references socket population and consolidation; a vague one references “optimization.”
5. “A cease-and-desist letter arrives Monday. What happens Tuesday?” Listen for sequencing — measurement before admission, counsel’s entry point, who speaks to the vendor.
6. “When did you last advise a client to take less — a smaller bundle, fewer cores, a shorter term?” The question the directory exists for; see also the wider list in 20 questions to ask.
7. “Which parts of this engagement are commercial, which are legal, and where do you stop?” Honest boundaries signal experience; omniscience signals its absence.
Adjacent guides and the working pages for this vendor, plus the directory filtered to Broadcom VMware.
The full enforcement landscape on this site →
The firms doing renewal and migration work →
The bundle decision inside most renewals →
What the model change means for your estate →
Who your advisor really works for →
Every field guide on the site →
Broadcom runs an active enforcement program rather than a classic audit cycle alone: organisations using VMware on expired perpetual entitlements have received cease-and-desist letters that assert infringement and explicitly reserve audit and legal rights, and cloud-connected components can report deployment data back to the vendor. Formal compliance reviews sit behind that outreach, so a letter should be treated as the opening of a negotiation, not a formality.
Perpetual licenses remain valid for the versions they cover, but Broadcom stopped selling them and no longer renews the support contracts beneath most of them. Running current patches without an active subscription is what triggers enforcement letters. The realistic options — subscribe, freeze the estate, take third-party support, or migrate — each carry licensing and risk trade-offs a partner should model rather than assert.
VMware subscriptions are sold per core with a floor of 16 cores per CPU, so a lightly populated socket is licensed to the floor even if it carries fewer cores. Estates built on many small hosts often pay for cores they do not have, which is why core-count and cluster-design right-sizing before the quote is one of the highest-value pieces of work a partner can do.
No. The catalog still distinguishes the full VCF stack from vSphere Foundation and the slimmer vSphere editions, and which one fits depends on whether you actually run the storage, network and management layers VCF bundles. The vendor’s commercial energy favours the larger bundle, which is exactly why the modelling should come from your deployment data, not from the quote.
Twelve months or more before renewal if a platform decision is in scope, because the leverage work — building a credible migration alternative, right-sizing cores, sequencing the decision — takes longer than the negotiation itself. A cease-and-desist letter compresses that clock to days; engage before responding.
Tell us which VMware situation you are in — renewal, bundle decision, enforcement letter or migration case — and we will route your brief to firms that genuinely cover it, with each firm’s independence status stated on its profile. Free for buyers, no vendor ever sees your brief, no markup.
Our weekly dispatch on vendor audit programs, regional developments and one buyer move. Subscribe to The Licensing Radar.