VMware renewal 2026: vSphere Standard, Enterprise Plus, VVF or VCF, and how to pick the tier

The line-up in September 2026

Broadcom’s product-line comparison of April 2026 lists two standalone vSphere editions, Standard and Enterprise Plus, and vSphere as a component of VMware vSphere Foundation and VMware Cloud Foundation. Essentials Plus, still on the list in January 2024, is gone. The sentence that decides most renewals is printed in the same document: Standard and Enterprise Plus “are only available as versions up to the 8 Update 3 release”, and vSphere 9.1 features “are only available as part of VMware vSphere Foundation 9.1 and VMware Cloud Foundation 9.1”.

Broadcom product-line comparison, April 2026; VVF and VCF 9.1 FAQs. The Register reported on 2 September 2026 that a Broadcom executive said an updated vSphere Standard is coming and that more details are likely at VMware Explore in Germany in mid-October; until it ships, plan on the 8 U3 ceiling.

Perpetual licences ended in December 2023, and a perpetual holder cannot move to 9.1 without converting to subscription first. Updates and upgrades require an active subscription or support contract; the exception Broadcom documents is patches for critical security advisories (CVSS 9.0 or higher) on supported versions, today vSphere 8.x; Broadcom makes them available to all customers, including perpetual holders whose support has expired. That is the background to the tier question at every renewal we see through our VMware optimisation work.

What each tier switches on

The feature rows below come from Broadcom’s own comparison; the VCF column from the 9.1 FAQ. The pattern is that Standard is the small-cluster edition (in September 2026 a Broadcom executive put its target at around 128 cores), Enterprise Plus and VVF share the vSphere feature set, and VCF adds the network and automation layers.

Firewall (vDefend) and Avi load balancing are add-ons even inside VCF: from VCF 9.0 the built-in NSX load balancer is entitled only for load balancing VCF’s own appliances and for Layer 4 load balancing of vSphere Supervisor, and Broadcom recommends Avi for general-purpose load balancing. Advanced Cyber Compliance is sold for VCF only.

Two names changed on the way to 9.x: Aria Operations is VCF Operations, Aria Automation is VCF Automation, and the subscription documents still carry the old names in places. And 9.0 deprecated, among others, Virtual Volumes, vCenter Enhanced Linked Mode and Host Profiles. All three are still present in 9.0, and Enhanced Linked Mode is kept there so that existing estates can upgrade, but Broadcom will remove them in a future release. For vVols the line comes earlier: Broadcom discontinued vVol certifications for 9.0 and considers vVols support on 9.0 only case by case, for a limited time, so migrate VMs off vVols datastores before the upgrade; the multi-vCenter change can follow later, before Broadcom removes Enhanced Linked Mode.

The counting rules that do not change with the tier

Every subscription tier is licensed per core with a minimum of 16 cores per processor. The programme documentation is explicit that every core on the server where the software is installed must be licensed, “including Cores deactivated by the BIOS”, and a core is defined as a physical unit, so hyper-threads do not count. One host with two 8-core processors and two hosts with two 24-core processors license as 32 plus 96, or 128 cores. Our licensing guide covers the arithmetic and the 72-core minimum per order: reported in March 2025 to take effect on 10 April, reported withdrawn in April and reported by a UK reseller for UK purchases from 1 December 2025. We found it in neither the programme documentation nor Broadcom’s core-counting article, but Broadcom’s own vmware.com site still hosts a video titled “Broadcom’s New 72-Core Order Minimum Explained”, so ask for the order minimum in writing with the quote. To take the count for your own hosts, run the script in Broadcom’s KB 313548 with all cores enabled, as the KB advises; our step-by-step guide shows how. The one exception is VCF Edge, at 8 cores per processor with at least ten sites within a year of the first deployment and 256 cores per site at most.

New in 9.x is the mechanism, not the metric: licence files replace the 25-character keys, VCF Operations becomes the mandatory licensing component, joined in 9.1 by a licence server, and a usage report and a licence update are due at least every 180 days. Miss them and, per the programme documentation, management-plane functions are degraded or blocked and support, including updates, suspended; Broadcom’s 9.1 documentation then treats the licences as expired. After a licence expires there are 90 days to update it, then hosts disconnect from vCenter and workloads cannot be started, though existing ones are not proactively stopped.

The vSAN entitlement, counted on raw terabytes

VVF includes 0.25 TiB of vSAN capacity per licensed core, rounded up to the next whole TiB; VCF includes 1 TiB per core. The entitlement is pooled across the cores of the same product: a compute-only cluster’s share can be spent by a vSAN cluster elsewhere in the estate. Consumption is counted on the raw physical capacity every host contributes to every vSAN cluster, and Broadcom’s knowledge base says that the vSphere Client’s vSAN Capacity Overview shows available datastore capacity, not the raw physical storage required for licensing.

Worked examples from Broadcom knowledge base article 313548. vSAN is optional in VVF: Fibre Channel and NFS estates simply do not use the entitlement.

The arithmetic explains why storage-heavy estates drift towards VCF even when they need none of NSX: at 1 TiB per core the storage licence disappears into the core count. It is also why the honest comparison for a VVF quote includes the vSAN add-on line from the start.

Support: what is included and what is sold on top

Since the 2024 portal transition, Broadcom says, all VMware products are covered by a single offering, Broadcom Software Maintenance, and VVF and VCF both include its Essential Support: continuous handling of severity 1 incidents for eligible customers who request it, with a 30-minute initial response target, updates and upgrades, and the support portal. The old tier names, Production, Basic, Business Critical and Premier, do not appear in the current handbook. On top, Broadcom’s knowledge base describes Broadcom Advanced Support with a support account manager or a designated support engineer for VCF product families, and Broadcom sells services: a technical adoption manager, extended expert services and workshops. Broadcom’s handbook also allows delivery through authorised partners certified by Broadcom, and some support requests are routed to them, so check who delivers first-line support under your contract. For the estates we look after under VMware optimisation, our engineering partner Vixen.UNO provides support under an agreed SLA, alongside your Broadcom support. What each part covers, and who answers a case, is in our guide to VMware support after Broadcom.

Term length against the calendar

In July 2025 Broadcom moved VCF 9 to a six-plus-one support model: six years of general support from the major release, with an estimated end of service in June 2031, minor releases every nine months or so, the early ones expected to get 27 months of support and the last 45. vSphere 7 ended general support on 2 October 2025, and Broadcom’s VCF blog said in August 2025 that vSphere 8 “will be supported until October 2027, with an optional two-year Extended Support period available for purchase”; the day, 11 October 2027, comes from press reports and a Broadcom table for its telco stack, so confirm it on Broadcom’s product lifecycle page before signing, as our vSphere 8 guide explains.

A three-year Standard or Enterprise Plus term signed at the end of 2026 runs to the end of 2029, about two years past the end of general support for the only version it can run; a five-year term runs four years past it. We found nothing in the programme documentation that converts a Standard subscription into VVF mid-term, so expect a new purchase. A VVF or VCF 9.x term of three years sits inside the 9.x lifecycle; a five-year term reaches its end. The tier decision is therefore also a version decision, to be made with the 2027 date on the table.

How we pick the tier

Start from what will actually run during the term, not from the feature list. If the estate is two or three hosts with HA and vMotion, no DRS, no distributed switch, and the applications tolerate a platform that stops at 8 U3, Standard is defensible. If DRS, Storage DRS, the distributed switch or VM encryption are in use, Enterprise Plus is the floor, with the same version ceiling. If you need vSphere 9 now, Kubernetes on the cluster, VCF Operations for monitoring, logs and diagnostics, or 0.25 TiB of vSAN per core, VVF is the entry point, with two checks: Broadcom confirmed in December 2025 that VVF is no longer sold in some EMEA countries, so confirm availability, and its operations tooling can only be used to monitor VVF cores, per the programme documentation. VCF is right when NSX, automation with tenancy, Private AI services or HCX are planned inside the term: Broadcom’s VVF 9.1 FAQ lists none of them as a VVF add-on (its VVF add-ons are vSAN capacity, VMware Live Recovery Cloud, Site Recovery Manager and Avi Load Balancer). If storage is the only reason, compare VCF with VVF plus vSAN add-on capacity on the same quote. Our VVF vs VCF comparison goes through the two component by component.

The renewal traps

Counting sockets or vCPUs instead of physical cores, or forgetting that BIOS-disabled cores count. Sizing vSAN on datastore capacity instead of raw capacity. Buying VCF for NSX and then licensing the firewall and the load balancer as add-ons anyway. Mixing VVF and VCF under one estate without checking which cores the operations tooling may manage. Leaving a host out of the count because it “only runs backups”. Signing a five-year term on an 8.x edition. Assuming the Private AI Foundation add-on covers the GPU driver licence, when vGPU workloads also need NVIDIA AI Enterprise. And renewing on the old host count when a right-sizing pass would take a host out of the cluster before the quote is issued, which is what the capacity audit is there to find. Our quote checklist takes the quote itself line by line.

What we do

Eurokommerz reviews VMware renewals for companies across the EU: the core count host by host, the raw vSAN capacity, the features actually in use, and the version path against the 2027 date, and then the tier that fits. Where the estate can lose a host before renewal, the optimisation comes first and the quote second. The engineering is done with our partner Vixen.UNO under one contract; the outcome is a renewal you can explain line by line.

FAQ