VCF vs VVF: what each Broadcom bundle includes (and where you may be overpaying)

After Broadcom consolidated the VMware portfolio, most buyers land on one of two bundles: VMware Cloud Foundation (VCF) or VMware vSphere Foundation (VVF). Picking the wrong one — or not realizing both are bundles — is where the bundling premium hides.

What each bundle includes

VVF is the smaller bundle, aimed at general-purpose virtualization: vSphere Enterprise Plus, vSAN capacity, and the Standard tier of operations and log management. If you run vSphere and vSAN, VVF is the intended fit.

VCF is the full private-cloud stack: everything in the vSphere + vSAN core, plus NSX networking, automation and self-service, a Kubernetes/container platform, and lifecycle management. It is priced accordingly.

The key point both bundles share: you can no longer buy a bare hypervisor. Even the smaller bundle carries components you may or may not use.

Where the premium hides

• Buying VCF for a vSphere + vSAN workload. If you do not run NSX, automation, or the container platform, you may be licensing a full private-cloud stack to use a fraction of it.
• The per-core vSAN entitlement. Both bundles include a vSAN capacity allowance per core (VVF and VCF grant different amounts). Exceed it and you owe vSAN capacity add-ons — an easy line item to miss.
• Edition drift. A mid-term change in what you deploy can move you across the VCF/VVF line without anyone re-checking the entitlement.

Matching the bundle to what you actually run

The right bundle is a function of what is actually deployed across your fleet — not a default or a sales recommendation. RenewalIntel maps each host to its edition and measures vSAN consumption per core against the bundled allowance, so the VCF-versus-VVF decision rests on your real usage and any add-on gap is priced with the calculation shown.