VCF. The bundle that re-prices every renewal.

VMware Cloud Foundation is now the strategic SKU under Broadcom — the bundle that absorbs vSphere, vSAN, NSX, and Aria into a single per-core subscription. Conversion economics, bundle attribution, and minimum-core sizing are the three places enterprises lose the most money at renewal. We assess, negotiate, and defend the VCF position.

How VCF is sold now.

VCF replaces the legacy per-CPU stack with a single per-core subscription that bundles vSphere, vSAN (capped), NSX, Aria Operations, and Aria Automation. The list price is the same regardless of how much of the bundle a customer actually deploys. Most enterprises consume between 40% and 70% of the stack but pay for 100% of it.

The bundle is positioned as a strategic uplift. In practice it is also a renewal lever: the SKUs that previously protected a buyer at renewal — standalone vSphere Standard, standalone vSAN — are no longer available to most buyer profiles.

What auditors verify in VCF.

For a VCF customer, the audit centres on whether the consumed cores match the entitled cores, whether the deployed editions match the contracted SKU, and whether any non-VCF VMware product is being run against the VCF entitlement without a separate licence. Bundle attribution is where the contested numbers usually sit.

Auditors will pull vCenter inventory, SDDC Manager records, NSX Manager exports, vSAN cluster sizing, and the Aria deployment manifest. If the bundle entitlement does not match the deployed capacity, the gap becomes a settlement claim.

Three VCF audit traps.

Minimum 16-core rule on small hosts

The 16-core-per-CPU minimum sizing rule for VCF dramatically inflates the licence count on small or older hosts. Buyers consolidating onto fewer, denser hosts often discover the rule too late to redesign.

vSAN capacity above the included tier

VCF bundles a capped amount of vSAN storage per core. Above that cap, additional vSAN add-on capacity is licensable separately — a frequent gap in the entitlement that emerges only at audit reconstruction.

Aria features used without included entitlement

Aria Operations and Aria Automation features turned on under the VCF default settings may exceed the included entitlement tier, particularly for self-service portals, advanced metrics, or third-party connector usage.

Defences we use in VCF engagements.

Most VCF disputes are won on the bundle attribution, the minimum-core rule, and the conversion ratio applied to legacy entitlement. The defences below have all been used to reduce a real claim or renewal.

Perpetual vSphere/vSAN/NSX entitlement preservation under conversion

Per-CPU to per-core ratio negotiation

16-core minimum applicability to legacy hosts

vSAN add-on capacity carve-out from VCF

NSX standalone retention versus VCF inclusion

Aria entitlement tier verification

SDDC Manager scope and managed-cluster boundaries

VCF on public cloud (VMC, AVS, GCVE) treatment

Hybrid VCF + standalone vSphere environments

Partial conversion path and co-term alignment

True-up window and notice-period challenges

Multi-year discount and price-cap recovery

Edition uplift inside VCF SKUs

Test, dev, and DR environment treatment

Affiliate and divested-entity carve-out

Renewal price-protection and ramp commitments

Where VCF savings tend to land

In documented VCF engagements the largest single reduction usually comes from challenging the conversion ratio from legacy per-CPU vSphere entitlement to per-core VCF subscription. The second largest comes from removing hosts from the VCF-managed footprint where they did not require the full stack. The third comes from rejecting the minimum-core sizing on legacy hosts where the contract pre-dates the rule.

VCF licensing questions.

Do we have to move to VCF at renewal?

There is no contractual obligation to convert. There is, however, a commercial reality that standalone vSphere and standalone vSAN are no longer offered to many enterprise buyer profiles at renewal. The decision is whether to convert on Broadcom's terms or to negotiate a different path. Both have been done.

What is the 16-core rule?

VCF and VVF subscriptions apply a minimum of 16 cores per CPU when calculating licence quantity. On a host with two 8-core CPUs, you license 32 cores even though the host has 16. The rule materially inflates the licence count on older or smaller hosts and is the single biggest sizing surprise we see.

Is vSAN included in VCF?

A capped amount of vSAN is included per core in VCF. Beyond that cap, additional vSAN add-on capacity is licensable separately. Storage-heavy workloads will frequently exceed the included tier without anyone noticing until audit.

Can we keep perpetual entitlements alongside VCF?

Yes. Mixed environments are common. Perpetual entitlements remain valid for use; VCF subscription covers the new or migrated footprint. The audit risk is in double-counting — proving which hosts are entitled under which contract requires clean records.

How is VCF priced relative to the old stack?

Most enterprises see a 2x to 5x list-price increase converting from the legacy perpetual stack to VCF subscription. Discount and negotiation typically recover a meaningful share of that, but rarely all of it. The renewal economics should be modelled before the conversion conversation begins.

VCF. The bundle that re-prices every renewal.

How VCF is sold now.

What auditors verify in VCF.

Three VCF audit traps.

Defences we use in VCF engagements.

Where VCF savings tend to land

VCF licensing questions.

VCF conversion in front of you?
Don't sign alone.

VCF. The bundle that re-prices every renewal.

How VCF is sold now.

What auditors verify in VCF.

Three VCF audit traps.

Defences we use in VCF engagements.

Where VCF savings tend to land

VCF licensing questions.

VCF conversion in front of you?Don't sign alone.

VCF conversion in front of you?
Don't sign alone.