VMware Cloud Foundation 2026. Negotiate the Broadcom VCF framework on your terms.

VMware Cloud Foundation is the load bearing VMware licensing conversation at the 2026 renewal cycle. Broadcom restructured the entire VMware portfolio around the VCF bundle, retired the perpetual license model, switched the metric from per processor to per physical core, and folded vSphere, vSAN, NSX, and Aria into a single subscription bundle.

The publisher's opening position anchors the bundle across the customer's broader compute estate at the upper customer scale. The buyer side response anchors VCF against actual deployment segmentation, actual core count, actual consumption, and actual renewal scope, so that the contract matches the customer's real VMware estate rather than the publisher's preferred broad VCF coverage.

A disciplined negotiation typically delivers twenty five to forty five percent savings against VCF at the renewal cycle. Read the related Broadcom VMware services practice, the Broadcom VMware negotiation playbook, and the VMware licensing assessment service.

VCF intersects with five principal commercial dimensions across the customer's VMware estate:

1. The VCF bundle. Anchors the negotiation against the customer's actual VMware bundle deployment.
2. The per core metric. Anchors the negotiation against the customer's actual physical core count rather than the publisher's preferred per processor model.
3. Consumption. Anchors the negotiation against actual VMware deployment consumption across the VCF subscription term.
4. Bundle scope. Anchors the negotiation against the customer's actual deployment of vSphere, vSAN, NSX, Aria, and the broader VCF components.
5. The renewal cycle. Anchors the negotiation against the customer's actual VCF renewal scope.

These five dimensions compound, with the cumulative effect that VCF runs as the load bearing VMware licensing conversation at the 2026 renewal cycle.

The VCF contract

VMware Cloud Foundation is the publisher's preferred packaging. It bundles vSphere, vSAN, NSX, and Aria into a single subscription metered on physical cores. The publisher's opening position anchors the bundle against a broad VMware deployment trajectory at the upper customer scale, so VCF ends up covering the customer's wider VMware estate across the contracted subscription term.

VCF therefore runs alongside the broader VMware renewal cycle, the consumption profile, and the support contract. Read the related audit risks under Broadcom VMware licensing for the audit dimension.

VCF is sold in three principal subscription terms:

1. One year. A short term that preserves optionality but carries the highest per year price.
2. Three year. The mid term option, often the default Broadcom offers.
3. Five year. The upper customer scale term, typically positioned with the deepest headline discount but the thinnest price protection.

The buyer side selects the subscription term against the customer's actual VMware roadmap rather than the publisher's preferred long term commitment. Read the broader Broadcom VMware negotiation playbook 2026.

The bundling

Bundling is the second commercial dimension at VCF. The publisher segments the VCF bundle across four principal components, and bundle scope is what anchors total contract value.

1. vSphere Foundation. Covers the customer's vSphere deployment across vCenter, ESXi, and the broader vSphere estate.
2. vSAN. Covers the customer's vSAN deployment across vSAN OSA, vSAN ESA, and the broader vSAN estate.
3. NSX. Covers the customer's NSX deployment across NSX Networking, NSX Advanced Load Balancer, and the broader NSX estate.
4. Aria. Covers the customer's Aria deployment across Aria Operations, Aria Automation, Aria Networks, and the broader Aria estate.

The buyer side narrows the bundle to the customer's actual VMware deployment rather than the publisher's preferred broad VCF coverage. Read the broader Broadcom VMware knowledge hub and the VMware licensing assessment service for the bundling work.

The per core metric

The per core metric is the third commercial dimension at VCF. The publisher meters the VCF subscription against the customer's actual physical core count, replacing the historical per processor model. A sixteen core per processor minimum drives subscription cost up significantly for hosts that fall under the sixteen core threshold.

Hosts fall into four core count populations:

1. Under sixteen cores. Hosts running fewer than sixteen physical cores per processor. The publisher applies the sixteen core minimum, which inflates subscription cost above the host's actual core count.
2. Exactly sixteen cores. The cleanest commercial outcome. Metered cores match the minimum.
3. Over sixteen cores. Hosts running more than sixteen physical cores per processor. The publisher meters the subscription at actual core count, which reflects the real deployment.
4. Bespoke core count. Negotiated counts at the upper customer scale, anchored to the customer's specific hardware profile.

The buyer side meters the VCF subscription against the customer's actual physical core count rather than the publisher's preferred sixteen core minimum. The exercise also examines whether the customer should consolidate to fewer hosts with higher core counts to reduce the per host minimum penalty. Read the related Broadcom audit defense service for the per core audit dimension.

Consumption

Consumption is the fourth commercial dimension at VCF. The publisher tracks deployed cores against the contracted commitment across the subscription term, and the consumption trajectory drives every renewal conversation.

There are four consumption patterns to track:

1. Under consumption. The customer pays for the contracted core count but deploys fewer cores. The buyer side moves the next renewal to actual deployed cores rather than the contracted ceiling.
2. At consumption. Deployed cores match the contracted commitment. The cleanest commercial baseline.
3. Over consumption. Deployed cores exceed the contracted commitment. Without intervention this produces a true up and forward escalation at renewal.
4. Bespoke consumption. Negotiated patterns at the upper customer scale, with bespoke true up and true forward mechanics.

The buyer side aligns the next contract to the customer's actual VMware consumption rather than the publisher's preferred broad VCF baseline. Read the broader Broadcom VMware case study for a worked example.

The renewal cycle

The renewal cycle is the fifth commercial dimension at VCF. Each renewal sets scope, quantity, and term for the next subscription period, and Broadcom uses the renewal as the lever for the largest price moves.

Four renewal questions matter:

1. Scope. Which VCF components actually renew, and which can be dropped or substituted against the customer's real deployment.
2. Quantity. The renewal core count, anchored to actual deployed cores rather than the contracted ceiling.
3. Term. One, three, or five year, selected against the customer's VMware roadmap, not the publisher's preferred long term commitment.
4. Bespoke terms. Negotiated price protection, true up mechanics, and exit rights at the upper customer scale.

The renewal also examines whether the customer should evaluate alternative hypervisors, hyperscaler workload migration, or competitive virtualization platforms as part of the renewal posture. Read the broader Broadcom VMware negotiation playbook landing.

Exposure

Exposure is the sixth commercial dimension at VCF. Four sources of exposure compound at the renewal cycle:

1. Bundle escalation. Customers who historically licensed only the components they used, such as vSphere alone, vSphere plus vSAN, or vSphere plus NSX, now find themselves paying for the full VCF bundle even when they deploy only vSphere.
2. Per core escalation. Customers running hosts with fewer than sixteen cores per processor see a meaningful subscription cost inflation under the sixteen core minimum.
3. Consumption drift. Deployed cores creep above the contracted commitment between renewals, surfacing as a true up at the next subscription start.
4. Renewal escalation. Broadcom has applied substantial price increases at the first VCF renewal cycle, with documented cases of three to five times the prior VMware spend.

Exposure therefore drives the size of the gap between the publisher's opening position and a defensible buyer side outcome. Read the broader Broadcom VMware negotiation enterprise playbook 2026 for a deeper treatment.

The buyer side moves

There are eleven buyer side moves that compound across the VMware estate at the VCF renewal cycle:

1. Anchor to actual deployment. Run VCF against the customer's actual VMware deployment, actual physical core count, actual bundle scope, and actual consumption rather than the publisher's opening position.
2. Pick the right term. Match the VCF subscription term to the customer's VMware roadmap, not a default five year commitment.
3. Scope the bundle. Walk through vSphere Foundation, vSAN, NSX, and Aria one at a time and only include components that match real deployment.
4. Right size on cores. Meter against the customer's actual physical core count and test host consolidation opportunities to reduce the sixteen core minimum penalty for under sixteen core hosts.
5. Reset consumption. Move under, at, over, and bespoke consumption patterns onto a contract that matches the customer's actual VMware consumption.
6. Plan the renewal. Set scope, quantity, term, and bespoke protections that match the customer's actual VMware renewal scope.
7. Hold the term line. Take multi year commitments only when the price protection terms are durable.
8. Challenge the bundle. Examine whether vSphere Foundation alone may be the right fit for the customer's actual VMware deployment.
9. Challenge the sixteen core minimum. Negotiate metered cores against actual physical cores rather than the per processor minimum.
10. Build a competitive posture. Develop credible options across alternative hypervisors and hyperscaler workload migration paths.
11. Run audit and renewal together. Sequence VMware audit response so the audit posture runs alongside the broader VCF renewal cycle.

These moves are set out in detail in the Broadcom VMware negotiation playbook landing, the Broadcom VMware negotiation playbook 2026, and the broader Broadcom VMware services practice. Read the related VMware VCF migration cost estimator and the VMware licensing assessment service.

How we engage

• VCF scoping. Six week engagement that scopes the VCF contract, anchors actual VMware deployment, and identifies the immediate commercial moves at the next VCF renewal cycle. Broadcom VMware services practice.
• VCF negotiation. Subscription negotiation engagement that handles VCF, the bundling, the per core metric, and the broader VMware renewal conversation across the renewal cycle. Broadcom VMware negotiation playbook.
• VMware audit defense. Audit defense engagement that handles the VMware audit response, compliance posture, and remediation across the audit cycle. Broadcom audit defense service.
• Vendor Shield. Always on multi vendor management posture that covers VMware alongside the broader enterprise software estate. Vendor Shield.
• Run the calculator. The VMware VCF migration cost estimator sizes VCF against actual physical core count and bundle scope.

What to do next

A clean VCF renewal posture starts twelve months ahead and works through deployment, bundle scope, term, and competitive posture in order. The checklist below is the sequence we run on engagement.

1. Pull the current VMware estate inventory. Catalog every host, cluster, processor, physical core count, and VMware component actually deployed.
2. Map deployment to bundle scope. Tag each cluster against vSphere, vSAN, NSX, Aria, and the broader VCF components and identify lines that are not used.
3. Run the per core math. Compute the actual physical core count and test host consolidation options to defeat the sixteen core minimum penalty on under sixteen core hosts.
4. Set the term posture. Pick one, three, or five year against the VMware roadmap and the exit horizon, not the publisher's preferred long term commit.
5. Build a competitive credible alternative. Develop options across alternative hypervisors, hyperscaler workload migration, and the broader virtualization market.
6. Stage the negotiation calendar. Open the conversation nine to twelve months before renewal and stay outside the ninety day window where Broadcom holds the leverage.
7. Run audit and renewal together. Sequence the VMware audit response so the audit posture is settled before the VCF renewal closes.
8. Document the close. Capture the bundle scope, per core count, term, price protection, and exit rights in a redlined order form that matches the actual VMware deployment.

Frequently asked questions

What is the Broadcom VCF framework?

The Broadcom VMware Cloud Foundation framework is the publisher's preferred VMware packaging. It bundles vSphere, vSAN, NSX, and Aria into a single subscription metered on physical cores. The framework anchors the VCF bundle against the publisher's preferred broad VMware deployment trajectory across the contracted subscription term.

What is the per core framework?

The per core framework is the metering Broadcom applies against the VCF subscription. The publisher meters the subscription against actual physical core count.

A sixteen core per processor minimum inflates subscription cost for hosts that fall under the sixteen core threshold. The buyer side anchors metered cores against the customer's actual deployment rather than the publisher's preferred minimum.

When should the VCF negotiation start?

The VCF negotiation should start nine to twelve months before the VCF renewal cycle. The buyer that arrives at the anniversary prepared holds the leverage. The customer that arrives inside ninety days hands the leverage back to Broadcom.

What savings can the framework deliver?

A disciplined VCF negotiation typically delivers twenty five to forty five percent savings against the VCF renewal at the 2026 cycle. The framework anchors VCF against the customer's actual physical core count and bundle scope rather than the publisher's preferred broad VCF coverage.