VMware VVF price versus VCF. What each bundle includes and how to price both per core.

VCF and vSphere Foundation are both priced per core with a 16 core minimum per processor, so the question is whether you will deploy what VCF adds. Buyers who priced both before the quote arrived got first offers 15 to 25 percent lower.

What is the difference between VMware Cloud Foundation and vSphere Foundation?

VMware Cloud Foundation (VCF) is Broadcom's full private cloud stack: compute, software defined networking, software defined storage and the cloud management and automation layer, sold as one platform. VMware vSphere Foundation (VVF) is the compute focused option, built around the hypervisor with a smaller storage allowance and a reduced operations tool.

Both are per core subscriptions with the same minimum of 16 cores per processor. What differs is the set of layers you are entitled to run, so the price gap only pays off if you deploy the layers VVF leaves out.

How much vSAN storage comes with each bundle?

Each VCF core carries 1 TiB of vSAN capacity and each VVF core carries 0.25 TiB, pooled across your licensed cores. Say you license 3 hosts with two 16 core processors each. That is 96 cores, which gives 96 TiB of vSAN on VCF and 24 TiB on VVF.

If your clusters run on external arrays, the larger allowance buys nothing. If they run on vSAN, check the raw capacity you actually consume before assuming VCF is the cheaper way to get it. Broadcom also sells extra vSAN capacity per TiB as an add on, and pricing that line against the full upgrade can be the better comparison.

What does vSphere Foundation leave out that buyers assume it includes?

• NSX. No software defined networking, so no distributed firewall, no overlay segments and none of the advanced routing features such as VRF and EVPN.
• VCF Automation. No self service catalog or orchestration for provisioning.
• HCX. The workload migration tool sits in VCF only, which matters if you planned to use it for a data center move.
• Fleet Management and SDDC Manager. Lifecycle management for the whole stack is a VCF feature.

Broadcom's own comparison describes VVF as carrying some VCF capabilities or limited versions of them. Read that as a reason to test each feature you rely on against the VVF entitlement before you sign.

How are VCF and vSphere Foundation priced?

Both bundles are priced per physical core per year on a term subscription, with every processor counted at 16 cores or more. VVF carries a lower rate per core than VCF. The rate you pay comes from your quote, your term length and your discount band. Our VCF pricing brief tracks the 2026 list and negotiated ranges.

Because the unit and the minimum are identical, you can price both bundles yourself with one core count and two rates. The core count is already yours, and the two rates can come from a budgetary quote or benchmark data. The per core mechanics are set out in the VMware licensing comparison.

Why is the 16 core minimum a separate problem from the bundle?

The bundle decides which software layers you pay for. The minimum decides how many cores you are billed for, whichever bundle you pick. A host with two 12 core processors has 24 physical cores and is billed for 32, a third more, on VCF or on VVF.

Across fleets that mix small core hosts with larger ones, the minimum added 10 to 25 percent to the billed count in our work. Switching to VVF while keeping many small hosts removes the software overreach and keeps the hardware inflation. Change the bundle at the next renewal and the host layout at the next hardware refresh.

How do you compare VCF and vSphere Foundation pricing for your own cores?

Count billable cores host by host, apply the minimum, then multiply by the VCF rate and the VVF rate on the same term. The example below uses a hypothetical company with illustrative rates of $300 per core for VCF and $150 for VVF. They are round numbers chosen for readable arithmetic. Replace them with the rates on your own quote.

Say you run 20 hosts, each with two processors. Ten hosts carry 24 core processors and ten older hosts carry 12 core processors. Only the ten larger hosts run vSAN and NSX in production today.

The VCF premium on the whole fleet is $120,000 a year, or $360,000 over the term, and it only pays off if the NSX and automation layers go into production. Licensing the small host cluster at VVF saves $48,000 a year, which is the value of a feature audit done cluster by cluster.

What does the core minimum cost in this example?

The ten small hosts are billed for 80 cores they do not have. That is 11 percent on top of the 720 physical cores, or $12,000 a year at the VVF rate. Five hosts with two 24 core processors would give the same 240 physical cores, all billed at face value.

Consolidation has to wait for the hardware refresh. Put the refresh date on the table during the negotiation anyway, because a known consolidation changes the core count Broadcom should price the later years of the term on.

Why do buyers pay for VCF features they never deploy?

Because VCF is usually offered during a renewal already shaped by a large price increase, when the buyer is looking for a reason the increase is justified. The full stack supplies that reason. It turns a price rise into an upgrade, with capabilities that have real value for organizations that deploy them.

What is missing from that conversation is a deployment plan, because no one in the room owns one. NSX and the automation layer need project work, skills and a roadmap slot. The renewal negotiation creates none of these, so the entitlement arrives and the implementation does not. A year later the company is running compute on a private cloud subscription.

What should you ask for before funding the VCF premium?

Ask for the same evidence you would ask of any other project:

1. Who owns the deployment of NSX, vSAN or VCF Automation, by name.
2. Which quarter the work starts.
3. Which workload goes onto the new layers first.

If those three answers exist, the premium buys capability. If they do not, it buys intent, and intent renews every year at the same price as capability.

Should you take VCF now because it is Broadcom's strategic platform?

The common advice is to take VCF at this renewal because it is where Broadcom is investing and the discount on it is deeper. We disagree for most customers. A deeper discount on a larger bundle can still cost more than VVF, and the strategic value only arrives once the layers are deployed.

The better course is to license VVF, or VCF only on clusters with a dated deployment plan. Ask for today's VCF rate to hold for any cores you upgrade during the term. Revisit the tier at every renewal, because a deployment that did not happen in year one rarely happens in year three.

How do you prove which VCF features you actually use?

Audit what is deployed rather than what you are entitled to. Check each layer that separates VCF from VVF and record whether it runs production workloads today, with evidence you could show a Broadcom account manager.

• NSX. Log in to NSX Manager and count the segments and distributed firewall rules that carry production traffic. A deployed manager with no production segments counts as not in use.
• vSAN. In vCenter, open each cluster's vSAN capacity view and note the used capacity in TiB. Compare it with the 0.25 TiB per core that VVF would give you, plus the cost of any add on capacity.
• VCF Operations. Note which dashboards and alerts your operations team uses every week. The limited VVF version may cover the monitoring you actually do.
• VCF Automation. Count published catalog items and requests over the last 90 days. If no one has requested anything, nothing in your operation depends on it.
• HCX. List migrations completed or scheduled. If a move is planned, date it, because it may justify VCF for one term only.

How do you count cores for either bundle?

Use Broadcom's License Counting PowerCLI Tool, published with Broadcom KB 313548, which reports cores and vSAN TiB per host with the 16 core rule applied. RVTools gives a second view: its vHost tab lists processors and cores per processor for every host, which is enough to find the small core hosts that sit below the minimum.

Run the count before Broadcom or the partner builds a quote, and keep the host by host sheet. When the quote arrives, compare it line by line with your own numbers.

What have we seen in recent VCF and vSphere Foundation decisions?

Across roughly 25 to 35 Broadcom VMware renewals we advised in 2024 and 2025, the bundle was rarely chosen on features. It was chosen on the core count arithmetic and the discount ladder the seller presented. Four patterns came up repeatedly:

• Undeployed premium. In about 7 out of 10 cases, the networking, storage and management capabilities that justified the higher bundle were still not in production a year after signature.
• Compute only on the full stack. Between 30 and 50 percent of customers on VCF used only the compute layer in practice, the same finding measured from the other side.
• Pricing both bundles first paid. Buyers who priced VCF and VVF against each other before the quote arrived landed 15 to 25 percent lower on the first offer. The seller then had to respond to a comparison the buyer had already made.
• The minimum applied everywhere. On hosts with small core processors, the per processor minimum added to the bill whichever bundle was chosen.

Do customers under 5,000 cores have any negotiating power?

More than the public narrative suggests, which holds that only very large customers can negotiate. Customers under 5,000 cores negotiated materially better outcomes in our work when they had credibly scoped a partial migration. What counted was whether an alternative had been costed. The absolute size of the footprint mattered less, which puts that power inside the buyer's control.

A costed partial move does not have to be large. Pick a workload slice with few VMware dependencies, price it on another platform and show the numbers. The economics of one common route are in our VMware to Nutanix migration analysis, and the full Broadcom library sits in the Broadcom knowledge hub.

What will the Broadcom account team say about VCF, and how do you answer?

Expect the conversation to steer toward VCF and toward a single number for the whole footprint. These are the lines we hear most often, with the reply that keeps the discussion on your data.

Which contract terms should you ask for when you choose a bundle?

• Upgrade price hold. A fixed VCF rate for cores moved up from VVF during the term, so the decision to wait costs nothing.
• Tier by cluster. Written confirmation of which clusters sit on VCF and which on VVF, attached to the order with the agreed core count.
• Tier change at renewal. The right to move cores from VCF back to VVF at the next renewal without a penalty on the rate.
• Growth core pricing. The same per core rate for cores added mid term, on either bundle.
• vSAN add on rate. A price per TiB for extra capacity on VVF, so storage growth does not force a full VCF upgrade.
• Renewal cap. A limit on the increase at the next renewal, since this contract sets the starting point for the next one.

Broadcom will not grant all of these. Table them early, while the price is still open. Our guide to price cap negotiation covers the wording.

What to do next

1. Twelve months before renewal. Run a feature usage audit that proves deployment, cluster by cluster, for NSX, vSAN, VCF Operations, VCF Automation and HCX.
2. At the same time. Count cores host by host with the Broadcom counting tool and flag every host billed above its physical cores.
3. Nine months out. Price both bundles at your own core count, before any quote arrives, and model a split by cluster.
4. Six months out. Scope and cost a partial migration, however small your footprint, and date any host consolidation.
5. Before funding VCF anywhere. Require a named owner, a start quarter and a first workload for each layer the premium pays for.
6. When the quote arrives. Compare it line by line with your count and table the contract terms above. The VCF and VVF comparison calculator helps you test the split.

Frequently asked questions