vSphere and vSAN subscriptions. The Broadcom era CIO playbook.

A CIO playbook for vSphere and vSAN in the Broadcom era: what changed, the four realistic subscription paths, core base engineering, and the contract terms that protect the term.

What changed for vSphere and vSAN under Broadcom?

Broadcom replaced perpetual licenses and a la carte SKUs with subscription bundles, sold per core. vSphere and vSAN now arrive primarily inside VMware vSphere Foundation and VMware Cloud Foundation editions rather than as standalone purchases.

The pricing unit is the core, with minimums per CPU. The portfolio simplification is real; so is the repricing that came with it.

What the bundle shift means commercially

• Capability you may not need: bundles carry automation, operations, and networking components many estates never deploy.
• Core counting drives cost: dense modern hosts price differently than the sprawl of older ones.
• Renewal is the negotiation: with perpetual gone, every renewal is a full repricing event.

The vSAN specifics

Per the vSAN product page, capacity now ships as a per core entitlement inside the bundles with expansion on top. Storage heavy estates need the capacity math done before the renewal call, not after.

Which subscription paths can a CIO actually choose?

Four realistic paths exist: VCF for the full stack estate, VVF for compute centric estates, a minimized bundle footprint with third party tooling around it, and a planned migration off the hypervisor. The right answer is workload math, not loyalty.

How do you size the core count honestly?

Count licensable cores per host, apply the per CPU minimums, and model consolidation before signing. Hardware refresh onto dense hosts routinely cuts the billable core base 20 to 40 percent, which compounds against every subscription year.

Where the common advice on Broadcom renewals is wrong

The standard advice is that Broadcom does not negotiate, so take the quote and budget the uplift. We disagree. In roughly 20 of the 25 to 35 Broadcom era renewals Morten Andersen advised in 2024 to 2025, material movement came from edition right sizing, core base engineering, and a credible migration scenario, even where the headline discount stayed thin. The buyer side move is to negotiate the base and the edition, not the percentage. Broadcom holds the rate card; you hold the core count and the workload placement.

Broadcom changed the price list. You still control the core count, the edition, and the credibility of your exit. Negotiate those.

Which terms protect the estate through the term?

Five terms decide whether year one pricing survives: renewal caps, edition lock language, core count true down rights, support commitments, and audit posture. Subscription estates that skip these renegotiate from zero every cycle.

1. Renewal cap: a written ceiling on the next term's per core rate movement.
2. Edition lock: the right to stay on the purchased edition without forced bundle upgrades.
3. True down rights: core count reductions at renewal when consolidation or divestment shrinks the estate.
4. Support definition: response and escalation commitments named in the order, not assumed from the Broadcom support portal defaults.
5. Audit clause hygiene: subscription does not end compliance exposure; usage beyond entitled cores is still findable.

The migration scenario as a contract term

A funded migration assessment, even one you never execute, is the only leverage Broadcom consistently respects. Estates that priced an exit before renewal negotiated from a different position than estates that could not.

What to do next

1. Inventory licensable cores per host and apply the per CPU minimums.
2. Map deployed capability against the bundle contents you are quoted.
3. Model a hardware consolidation refresh and its effect on the core base.
4. Price one credible migration scenario for portable workloads.
5. Negotiate edition, core base, renewal cap, and true down rights together.
6. Calendar the renewal at T minus 9 months; Broadcom timelines punish late starts.

The wider licensing picture is in the Broadcom VMware licensing pillar and the VCF pillar. The Broadcom VMware practice runs renewal defense end to end.

Frequently asked questions

How are vSphere and vSAN licensed under Broadcom?

As per core subscriptions inside bundles, primarily VMware Cloud Foundation and vSphere Foundation, with minimum cores per CPU. Standalone perpetual licensing is gone, and every renewal is a repricing event.

How much did Broadcom era renewals increase costs?

Unprepared estates in our 2024 to 2025 file saw 2x to 4x uplifts, driven by bundle capability they never deployed and unengineered core bases. Prepared estates cut that materially through edition and core base work.

Can you negotiate with Broadcom at all?

Yes, on structure more than rate. Edition right sizing, core true down rights, renewal caps, and a credible migration scenario all moved outcomes in our engagements, even where headline discounts stayed thin.

Should we migrate off VMware instead of renewing?

Price the scenario either way. Estates with portable workloads gain leverage from a funded migration assessment even if they stay; estates that cannot credibly leave should engineer the core base and lock protective terms instead.

What is the biggest hidden cost in the new bundles?

Paying for components you never deploy. Map deployed capability against bundle contents before accepting a VCF quote when VVF or a minimized footprint covers the actual workload.