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. Broadcom told the press in September 2026 that a refreshed vSphere Standard is coming, with details expected in 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. Patches from the support portal go only to entitled customers. That is the background against which the tier question is asked 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 a two-node-cluster product, 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; VCF’s built-in load balancer runs only until 30 May 2027, and only with Avi licences. 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 two things were deprecated at 9.0: Virtual Volumes and vCenter Enhanced Linked Mode, which forces storage and multi-vCenter design changes on any estate that upgrades into VVF or VCF 9.

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. Two hosts with two 8-core processors and two hosts with two 24-core processors licence as 32 plus 96, or 128 cores; the small processors cost the same as 16-core ones. Our core-counting guide works through the arithmetic and the reported 72-core minimum-order episode of 2025, which Broadcom never confirmed and the documents do not carry. The one exception is VCF Edge, at 8 cores per processor with a ten-site minimum 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, and a usage report must be submitted at least every 180 days. Miss it and the programme documentation allows the management plane to be degraded and support, including updates, to be suspended. After a licence expires there are 90 days to renew, then hosts disconnect from vCenter and workloads cannot be started.

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: a compute-only cluster’s share can be spent by a vSAN cluster elsewhere in the estate. What catches people is the measure. Consumption is counted on the raw physical capacity every host contributes to every vSAN cluster, and Broadcom’s knowledge base says in as many words that the vCenter capacity overview, which shows datastore capacity after policies, is the wrong number to use.

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: one offering, no premium tier

Since the 2024 portal transition all VMware products are covered by a single offering, Broadcom Software Maintenance, and VVF and VCF both include its Essential Support: round-the-clock handling of severity 1 incidents 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. What Broadcom sells on top are services: a technical adoption manager, extended expert services and workshops. Support requests may be routed to certified partners, which is where our engineering partner Vixen.UNO sits for the estates we run under managed services.

Term length against the calendar

VCF 9 moved 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, each supported 27 months. vSphere 7 ended general support on 2 October 2025, and vSphere 8’s end of general support is widely reported for October 2027; Broadcom’s lifecycle page sits behind a login, so confirm the date on your own account before signing.

Put the two together. 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 reported end of support for the only version it can run; a five-year term runs four years past it. Nothing in the programme documentation converts a Standard subscription into VVF mid-term: that is 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, and it should be made with the 2027 date on the table, not discovered at the first security advisory that has no 8.x patch.

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; Broadcom itself positions it at roughly 128 cores. 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 capacity and compliance, or a quarter of a terabyte of vSAN per core, VVF is the entry point, with two checks: VVF was withdrawn in some EMEA countries in December 2025, so confirm availability, and its operations tooling may only monitor VVF cores. VCF is right when at least two of NSX, automation with tenancy, a terabyte of vSAN per core, Private AI services or HCX migrations are planned inside the term. One of them alone is usually cheaper as an add-on, and Broadcom’s own executives have acknowledged complaints from customers who bought the stack and ran “bits and pieces” of it.

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 where the capacity audit pays for itself.

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 over the last quarter, 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