VVF means VMware vSphere Foundation. What the bundle includes and what it costs per core.

VVF is VMware vSphere Foundation, the smaller of Broadcom's two VMware bundles. Knowing where it ends and VCF begins decides what you pay per core, and a host by host recount decides how many cores you pay for.

What does VVF stand for in the Broadcom VMware catalog?

VVF stands for VMware vSphere Foundation. It is the smaller of the two bundles Broadcom now sells VMware through, built around vSphere, vCenter and an operations management layer, and priced per core on subscription. Broadcom describes it on the VMware vSphere product page.

The acronym matters because Broadcom collapsed thousands of VMware SKUs into a short list after the acquisition. Two names now carry almost every enterprise conversation. From version 9.0, vSphere is only offered inside VVF or VCF, so the old standalone vSphere Standard and Enterprise Plus choices are gone from the new release.

• VVF, VMware vSphere Foundation. vSphere Enterprise Plus, vCenter, operations management, Kubernetes and a capped vSAN capacity entitlement per core.
• VCF, VMware Cloud Foundation. The full private cloud platform. It adds NSX networking, a larger vSAN entitlement and automation tooling, as set out on the VMware Cloud Foundation page.
• Add ons. Extra vSAN capacity and advanced services price separately on top of either bundle.

What is inside the VVF bundle?

Broadcom's VVF 9.1 FAQ lists five parts. Each has limits that matter when you compare it with what you run today.

• vSphere Enterprise Plus. The hypervisor edition most large VMware customers already ran, including DRS and distributed switching.
• vCenter Standard. One instance for central management.
• vSphere Kubernetes Service. Formerly Tanzu Kubernetes Grid. Broadcom's program terms give the Kubernetes parts a shorter support life cycle than the rest of the software.
• VCF Operations, with fewer features. The successor to Aria Suite Standard. The VVF program terms allow it to monitor VVF cores only, and Broadcom's 9.1 feature comparison reserves real time monitoring and predictive capacity management for VCF.
• vSAN at 0.25 TiB per licensed core. Capacity can be pooled across clusters where VVF is deployed. Anything above it needs the vSAN add on license.

What does VVF leave out?

VVF has no NSX and no VCF Automation, and its operations tooling is the reduced version. If your network team runs NSX microsegmentation or overlay networks in production, VVF alone will not cover that cluster. If you run physical network security and a separate automation tool, it usually will.

The VVF program terms also bar deploying the software on any cloud service, so hosting providers need a different contract.

How does VVF differ from VCF in scope and price?

VVF covers compute virtualization and operations. VCF covers the full software defined data center, and the list price gap between them is large enough to fund a serious negotiation. Decide from the capabilities you deploy today, whatever bundle the seller opens with.

Our feature by feature comparison covers the detail, and our VCF and VVF comparison calculator puts the two side by side on your own core count.

Where do buyers overpay?

Overpayment concentrates in two places. The first is VCF quoted to environments that only run vSphere. The second is vSAN capacity counted as free value when it duplicates SAN or NAS storage you already own and will keep for years. Both show up in the first quote, and both come down when you challenge them with deployment data.

How does Broadcom count cores for VVF?

Broadcom licenses VVF per physical core with a minimum of 16 cores per CPU. A host with two 12 core CPUs is licensed as 32 cores, even though it has 24. The floor adds cost wherever an environment was built on small, cheap processors, and it rarely appears as a separate line on the quote.

Which counting rules change the invoice?

• 16 core floor. Every CPU bills at 16 cores minimum, whatever its physical count.
• Every physical core counts. Broadcom's VVF program terms require a license for each core on the server, including cores deactivated in the BIOS. Moving or shutting down workloads does not reduce the count. Only hardware changes do.
• Order minimums. In March 2025 distributors told partners that orders from April 10, 2025 would need at least 72 cores per product. Broadcom then said the 16 core minimum had not changed, and the current VVF program terms set no order minimum. Ask your partner to confirm in writing that none has been applied to your quote.
• Cluster design. Consolidating onto fewer, larger CPUs reduces the floor penalty at the next hardware refresh.
• Compliance reports. Customers must upload a compliance report 180 days after license registration and every 180 days after that. A missed report can degrade management features and suspend support.

Broadcom documents these rules through its support portal and knowledge base. Before any renewal, rebuild the core count from the hypervisor inventory instead of accepting the seller's number. Our per core calculator applies the floor for you, and our guide to VMware core licensing covers the edge cases.

How do you check your own core count?

Three sources give you a count you can defend line by line against Broadcom's.

1. Broadcom's counting script. Knowledge base article 313548 provides a PowerCLI module, FoundationCoreAndTiBUsage.psm1, that reports licensable cores per host and vSAN TiB. Run it with all cores active, as the article instructs.
2. vCenter inventory. Each host's hardware summary shows CPU packages and cores per package. Export it and apply the floor per CPU in a spreadsheet.
3. RVTools. The vHost tab lists sockets and cores for every host in one export, which makes it easy to spot decommissioned hosts still sitting in the seller's records.

What does a recount look like in practice?

Say you run 20 hosts: 12 older hosts with two 12 core CPUs and 8 newer hosts with two 32 core CPUs. Broadcom's renewal records still show 4 retired hosts with two 16 core CPUs each. The figures below are hypothetical, and the $150 per core annual rate is for illustration only. Use the rate on your own quote.

Removing the retired hosts takes 128 cores, or 12.5 percent, off the seller's count. The refresh removes another 96 floor cores with no loss of physical capacity. The same recount sets your vSAN entitlement: 896 cores give 224 TiB under VVF, against 896 TiB if the same cores were on VCF.

What have we seen in recent Broadcom VMware renewals?

Across roughly 35 to 45 Broadcom VMware renewals and migrations I advised in 2024 to 2025, the choice between VVF and VCF moved more money than the discount percentage. Three patterns came up again and again.

• VCF by default. Customers quoted VCF without asking were paying for NSX and a private cloud stack they did not run in roughly half the cases we benchmarked.
• Host by host recounts. Buyers who recounted cores before renewal cut the licensed core base by 10 to 20 percent against the seller's first count.
• A tested alternative. First quotes moved 20 to 40 percent when a tested migration alternative was documented and shared with the account team.

Use these ranges as benchmarks for what disciplined buyers achieved with Broadcom. Your own hardware, contract dates and alternatives decide where you land within them.

Why we would not buy VCF to future proof

The usual partner pitch is that VCF is the safe choice because it prepares you for private cloud. We disagree. In roughly 15 of the 35 plus Broadcom VMware environments we benchmarked in 2024 to 2025, NSX and the automation layer, the parts that justify VCF's premium, were still not deployed a year after signature.

License VVF for what runs today, and write a mid term upgrade option into the order with the VCF price fixed now. You can buy the upgrade at any point in the term, but Broadcom does not refund a year of unused NSX.

What negotiation tactics work on a VVF renewal?

Three tactics move VVF pricing: the bundle scope decision, a documented migration alternative, and term length traded for written price protection. Each works because Broadcom's account teams are measured on retaining the subscription base. Perpetual licenses are no longer sold, so every renewal is now a recurring negotiation.

• Scope first. Price VVF against VCF with a component by component deployment map, and refuse to pay for stack you have not deployed.
• A credible exit. A tested proof of concept on another hypervisor, such as Hyper-V or Proxmox, changes quotes far more than a verbal threat. A subset of workloads is enough.
• Term for protection. Sign a multi year commitment only with renewal caps and price holds written into the order.

Run all three before the quote lands. Once a renewal number has circulated inside your company, it becomes the reference point for everyone, and that works for Broadcom. Our vSphere Foundation negotiation guide covers the sequence in more detail.

What will the Broadcom account team say, and how should you answer?

• "VCF is where the product is going, and VVF will get fewer features." Ask which features on your deployment map are missing from VVF today. Buy against that list and price a later upgrade now.
• "Our count comes from your registered entitlements." Registered entitlements reflect what you bought years ago, often including capacity on hosts you have since retired. Send the counting script output and ask Broadcom to reconcile host by host.
• "The vSAN capacity in VCF covers your storage growth." Ask what the storage it replaces would cost you. If you keep the existing arrays, the extra TiB are worth nothing to you.
• "This discount expires at quarter end." A quarter end deadline serves the seller's forecast. Keep to your own schedule, and if you need more time, ask in writing for a short extension of current terms.

Which contract terms should you ask for?

• A renewal cap. A fixed maximum percentage increase for the next term, so the second renewal does not restart from list.
• Price holds on growth cores. The same per core rate for cores added during the term.
• An upgrade option to VCF. A fixed per core price and a credit for the VVF subscription already paid.
• An agreed core count. The recounted host by host inventory attached to the order, so future compliance reports start from your number.

The VVF or VCF decision is the negotiation. Everything after it is arithmetic on the core count.

How does the decision change with the size of the environment?

The same rules weigh differently depending on how many hosts you run and whether this is your first subscription.

• Small environments. With two to four hosts on small CPUs, the 16 core floor can be a large share of the bill and a recount finds little to remove. The bundle choice, and whether a smaller hypervisor would do the job, matter more.
• Large environments. With several hundred hosts, the floor and retired hosts add up to thousands of cores. Buying VCF only for the clusters that run NSX usually saves the most.
• First conversion or renewal. On the first switch from perpetual licenses, the bundle choice matters most. At renewal Broadcom starts from your registered entitlements, so the recount is your main correction. Our summary of the Broadcom licensing changes helps if you are converting now.

What to do next

1. Twelve months out. Pull the hypervisor inventory and rebuild the per core count, applying the 16 core floor host by host.
2. Nine months out. Map every VCF only component against actual deployment and decide whether VVF covers each cluster.
3. Before the quote. Price extra vSAN capacity separately and compare it with the storage you already own.
4. Six months out. Document one tested migration alternative, even for a subset of workloads. Our VMware exit plan sets out the steps.
5. When the quote lands. Set the internal budget from your recount. Do not let the seller's renewal quote become the budget figure.
6. At signature. Agree term length only in exchange for written renewal caps and price holds. Our Broadcom VMware renewal survival kit covers the full sequence for 2026 renewals.

Frequently asked questions