VVF vs VCF 9.1: what is actually different, component by component, and what follows for design

The short answer

Per Broadcom’s KB 455220, VVF is “a subset of the full VCF platform stack”: VVF 9.1 brings vSphere Enterprise Plus with vCenter, vSphere Kubernetes Service, VCF Operations with logs and diagnostics, and vSAN, and VCF 9.1 adds NSX networking, VCF Automation, VCF Operations for Networks, HCX, SDDC Manager and, where the SKU includes them, VCF Private AI Services. VVF includes 0.25 TiB of vSAN capacity per licensed core, VCF 1 TiB per core. Both are subscriptions licensed per physical core with a minimum of 16 cores per processor, and Broadcom’s product line comparison of April 2026 makes vSphere 9.1 available only inside these two.

Component by component

Broadcom’s current feature comparison, a white paper of 30 September 2026 for VCF and VVF 9.1.1, marks almost every compute and storage feature for both products, from DRS, HA and Fault Tolerance to vSAN ESA, stretched clusters and file services. The products part at the management, network and automation layers, which the table takes from Broadcom’s component lists.

Broadcom: VVF and VCF 9.1 FAQs (VCF: 3 September 2026); programme documents (June 2026); TechDocs 9.1 component list (29 September 2026) and deployment guide (1 October 2026); VCF blog (13 July 2026).

Networking, Kubernetes and operations: where the line runs

NSX is the main difference. Broadcom’s 9.1 component list gives NSX Manager, NSX Edge and the virtual network appliance the platform type “VCF” only. The distributed switch functions, from LACP and private VLANs to NetFlow and port mirroring, are marked for VVF in the comparison; overlay networking, routing, VRF, NAT, VPN and VPCs come with NSX.

Kubernetes is only partly the dividing line: vSphere Kubernetes Service is in both, but the comparison marks GitOps integration, Secret Service, External DNS and Cert Manager for VCF, not VVF. On VVF the Supervisor runs on distributed switch networking with the Foundation Load Balancer, which a Broadcom blog of July 2026 calls “included out of the box” for both VVF and VCF, or with Avi as an add-on. NSX segments and VPCs need NSX Manager, and so VCF.

Both products include VCF Operations, the component that licenses 9.1: the VVF FAQ calls it “a required component for centralized license management”. VCF adds VCF Operations for Networks, HCX for workload migration, the identity broker and real-time metrics services and, per the comparison, certificate and password management. SDDC Manager, which Broadcom describes as providing “Lifecycle management for ESX, vCenter, HCX, and NSX” and the deployment of workload domains, is VCF only.

What a VCF 9.1 deployment adds

Both products are built with the same VCF Installer, and the two 9.1 deployment wizards offer the same principal storage: vSAN ESA or OSA, NFS v3, or VMFS on Fibre Channel. For VVF, the installer deploys vCenter, VCF Operations and the VCF management services; Broadcom notes that it “deploys vSphere Foundation only with VCF management services”. For VCF, it also deploys NSX Manager and SDDC Manager, adds an NSX traffic type to the distributed switch and an “NSX Host Overlay Network”, a “dedicated VLAN separation for NSX tunnel endpoint VMkernels”, and allows VCF Automation to follow as a Day-N operation.

For the design, a VCF instance needs that VLAN, the addresses and the capacity for the NSX Manager and SDDC Manager appliances from the first deployment. Broadcom also lists configurations it does not support when converging existing infrastructure to VCF, among them vCenter instances with Enhanced Linked Mode or vCenter High Availability, vCenter instances without a distributed switch, and clusters on lifecycle baselines or with manual or partially automated DRS. Our reading, not a Broadcom statement: a VVF estate that may grow into VCF is easier to move if it avoids these from the start.

Mixing VVF and VCF in one estate

An estate that needs NSX or automation in some clusters only can run both products. In 9.1 the unit of that split is the vCenter instance: “You can assign only one primary license to a vCenter instance”, per Broadcom’s licensing documentation, and hosts or vSAN clusters take another licence only as an override.

Broadcom TechDocs 9.1 licensing: licensing model, overview, primary licence, override licences and mixed-version environments (1 October 2026); KB 441960; VVF and VCF programme documents (June 2026).

The 9.1 licensing documentation says that vSAN capacity, “when purchased through VCF, vSphere Foundation, or a vSAN add-on, also pools together in one default add-on license”, while both programme documents allow the entitlement to be “aggregated and utilized” only across the cores of their own product. Keep the TiB arithmetic per product: our core count guide shows Broadcom’s script run per cluster with -DeploymentType set to VVF or VCF. Both programme documents also let their vCenter manage only vSphere licences entitled to upgrade to the deployed version; Standard and Enterprise Plus stop at 8 Update 3, so check before you put such hosts under a 9.1 vCenter.

Moving from VVF to VCF later

Broadcom’s VVF blog of 28 September 2026 speaks of a transition to VCF “whenever you’re ready”; the documents differ by version.

Broadcom KB 455220, KB 441960 and KB 450972 (no date shown, read on 4 October 2026); TechDocs 9.1, “Paths to Building 9.1.x Environments” and the workload domain import guide (both 1 October 2026); VCF 9.1 FAQ (3 September 2026).

The 9.1 installer deploys VVF only with VCF management services, so an installer-built VVF 9.1 estate falls under that sentence; VVF can also be deployed manually without them. Broadcom’s 9.1 guide to importing a vCenter into a VCF instance as a workload domain also covers vCenter 9.0 or later, but we found no VVF case in it: ask Broadcom or the reseller for the supported route before a design depends on it. Infrastructure “is added at the vCenter level”, per the VCF FAQ, so every host under a converted vCenter moves to VCF licences. When to change tier, and for what term, is in our renewal guide; how cores are counted, in our licensing guide.

vSphere Standard vs Foundation, and VVF for VDI

Against VVF, Broadcom’s product line comparison of April 2026 gives vSphere Standard no DRS, distributed switch, vSphere Kubernetes Service, VCF Operations or vSAN, and Fault Tolerance for 2 vCPUs only. It adds: “Note that vSphere Standard and vSphere Enterprise Plus are only available as versions up to the 8 Update 3 release.” The Register reported on 2 September 2026, from interviews with Broadcom executives at VMware Explore, that VMware “will soon release an updated version of vSphere Standard”, with no version or date. As of 4 October 2026 we found no Broadcom document on a vSphere Standard 9.x.

For VDI, Broadcom documents a separate product, VVF for VDI: licensed “on a per User license metric”, “not available for sale as a standalone product” and deployed only as part of a third-party VDI offering, per its programme document of February 2026. Broadcom’s KB 439672 says that for a 9.x upgrade “only VVF and VCF are eligible, VVF for VDI is not entitled currently”, and that Broadcom “has not yet announced timelines for vSphere 9 support with VVF for VDI”. Broadcom’s KB 428674 (9 February 2026) adds that the vSphere Enterprise Plus 8 end-of-support date “does not apply to VVF for VDI (or its vSphere component)”. The VVF and VCF programme documents we read contain no VDI-specific terms.

What to list before you decide

For each vCenter instance, list its clusters and hosts with ESX version and cores, and the raw vSAN capacity per cluster. Then mark, cluster by cluster, what runs today on NSX (segments, distributed firewall, edges), on VCF or Aria Automation, on a Supervisor or other Kubernetes, and through HCX, and note Enhanced Linked Mode, vCenter High Availability, baseline-managed clusters and the DRS automation level. A vCenter whose clusters need none of the VCF-only components has no component reason for VCF, leaving the vSAN arithmetic as the remaining input; one that needs any of them is VCF, and every host under it then draws on VCF licences. Broadcom told The Register in December 2025 that “VVF is no longer available in some EMEA countries”, so confirm availability. If the list cannot be completed in-house, the estate and licence audit in our VMware optimisation service delivers a full inventory of the VMware estate.

What we do

Eurokommerz supplies VMware / Broadcom licensing together with our engineering partner Vixen.UNO, with audit, licensing and deployment under one European contract, as our software page explains. Under VMware optimisation, the Vixen.UNO team audits the estate and its licences, matches editions and subscriptions to real workloads within Broadcom’s current licensing logic, and draws up an action plan ahead of renewal and end of support, with dates. The first step is a free call; the paid technical assessment, its price fixed before work begins, delivers a report, a TCO and ROI model and that action plan. Modernisation of vSphere, vSAN, NSX and VCF follows in agreed maintenance windows with a rollback plan, then support under an agreed SLA.

FAQ