This is not a choice between two live products: Broadcom closed vSphere Standard to new purchase and renewal at the end of July 2025, so a Standard estate maps onto vSphere Foundation (VVF) by default — a bundle that contains substantially more than Standard ever did, priced accordingly per core. The real decision is whether to accept that mapping, ride the current entitlement to the end of vSphere 8 support in late 2027, or use the forced step-up as the trigger to replatform part of the estate.
Published 31 December 2025 · Last reviewed 31 December 2025
vSphere Standard survived the first round of Broadcom’s portfolio simplification. When perpetual licensing was withdrawn in early 2024 and the catalogue collapsed into subscriptions, Standard carried on as the entry-level per-core subscription beneath vSphere Foundation (VVF) and VMware Cloud Foundation (VCF) — the natural landing spot for estates that wanted the hypervisor, vCenter and not much else.
That ended in mid-2025. With the vSphere 9 generation, Broadcom consolidated the enterprise catalogue onto the two bundles: vSphere Standard (and the briefly revived Enterprise Plus edition) reached End of Sale on 31 July 2025, closed to both new purchase and renewal. The vSphere 9 release line ships only inside VVF and VCF; a Standard entitlement keeps you on the vSphere 8 branch, which remains supported into late 2027.
So the SKU mapping every Standard customer eventually faces is upward: Standard’s direct successor on the price list is VVF. The two are not equivalents. Standard was a deliberately thin edition — the hypervisor with vMotion and high availability, but without DRS, without the Distributed Switch, without any storage entitlement. VVF carries the full enterprise-tier hypervisor feature set plus operations tooling, a Kubernetes runtime and an included vSAN allowance. The comparison below maps exactly what changes — in features, in metric and in commitment shape.
This guide compares licensing programs as published by the vendor; it is general information, not legal or licensing advice for your situation, and it names no firms. Program terms change — verify current terms against your own quote. The firm directory lists VMware-capable advisors with balanced pros and cons, listed, not ranked.
| DIMENSION | VSPHERE STANDARD (LEGACY) | VVF — VSPHERE FOUNDATION |
|---|---|---|
| Availability | Closed — End of Sale 31 July 2025; no new purchase, no renewal | Current; one of the two principal subscriptions in the 2026 catalogue |
| Version access | vSphere 8 branch only; supported into late 2027 | vSphere 9 generation; the actively developed release line |
| Hypervisor features | vMotion, high availability; no DRS, no Distributed Switch, no Fault Tolerance | Full enterprise tier: DRS, Distributed Switch, Fault Tolerance and the features that historically required Enterprise Plus |
| Management | vCenter Standard | vCenter Standard |
| Storage (vSAN) | None included | 0.25 TiB per licensed core included (since April 2025); add-on capacity per TiB beyond |
| Operations & Kubernetes | Neither included | Foundational operations and log tooling; Kubernetes runtime services |
| Metric | Identical basis: per physical core, with every CPU counted as at least 16 cores. A 72-core per-order minimum announced for April 2025 was withdrawn within days; check the floors on your own quote | |
| Commitment shape | Low per-core rate for a thin feature set; nothing bundled, nothing wasted | Materially higher per-core rate carrying components a Standard-shaped estate never used; multi-year terms quoted with discount pressure |
| Renewal dynamics | None remaining — the term ends and the SKU ends with it | Standard subscription renewals; leverage depends on credible alternatives, covered below |
The structural point sits in the last three rows. The metric is the same, so the migration quote is driven almost entirely by the per-core rate difference between a thin SKU and a full bundle — multiplied across every core you run. For an estate that used Standard precisely because it needed nothing more, the uplift buys capability it never asked for. That is not an argument against VVF; it is the reason the quote deserves a forensic read rather than a signature.
End state one: renew into VVF. The default path, and for many estates the right one. It fits organisations that will genuinely use what the bundle adds — DRS for load balancing across clusters, the Distributed Switch, moderate vSAN use inside the included 0.25 TiB-per-core entitlement — or that simply need to stay current on a supported, actively developed release line beyond 2027. If the estate was Standard-shaped only by budget rather than by architecture, VVF is less an uplift than a catch-up.
End state two: run the clock on vSphere 8. A Standard subscription runs to the end of its term, and the vSphere 8 branch it entitles remains supported into late 2027. That window is real planning time: long enough to evaluate alternatives properly, negotiate without a deadline at your back, or schedule a hardware refresh to coincide with whatever comes next. Perpetual Standard keys with lapsed support keep functioning indefinitely — without patches or support — a position some organisations accept for static, isolated clusters and one whose trade-offs are the subject of the perpetual-versus-subscription guide.
End state three: replatform some or all of it. Standard estates are, by construction, the least locked-in tier of the VMware install base: hypervisor-level dependency only, third-party storage, no NSX, no automation layer. That makes the credible-alternative case easier to stand up here than anywhere else in the catalogue — and even a partial migration plan, costed and dated, changes the tone of the VVF negotiation. The honest version of this test is architectural: if your team relies on vCenter workflows, integration tooling and operational muscle memory, price the switching cost honestly before treating the alternative as leverage.
Most real outcomes mix the three: VVF on the clusters that earn it, the vSphere 8 clock on the rest, and a genuine evaluation running in parallel. The mix is the negotiation position.
The quote arrives as a fait accompli; treat it as an opening position. A forced SKU migration compresses the buyer’s options, and quotes are framed accordingly: the new bundle, your full core count, a multi-year term. Everything in that frame is negotiable — term length, payment shape, which clusters are in scope at signature, and the rate itself, which moves furthest when a costed alternative exists. The dynamics are the same as any VMware renewal negotiation, with one advantage: the 2027 support horizon gives a Standard estate more genuine runway than most renewal events allow.
Audit the core count before the vendor does. Per-core licensing with a 16-core-per-CPU floor means the licence requirement is a function of hardware inventory, and hardware refreshes to higher-core-count processors expand it silently. A dated core inventory — sockets, cores per socket, clusters in scope — is the first artefact any negotiation or compliance assessment should produce, and it is also the defence against quotes sized on assumptions rather than fact.
Keep the entitlement paper trail. Standard estates often date back through years of perpetual purchases, upgrades and partial migrations to subscription. Order forms, entitlement records and support histories determine what you actually hold — and what any migration credit or trade-in discussion starts from. Reconstructing that record after the quote lands is harder than maintaining it before.
Mind who explains your options. Much of the advice reaching Standard customers comes through channels that earn margin on the outcome — on the VVF order, on the hardware refresh, on the alternative platform. The independence test applies in full: ask who profits from each option being chosen before weighing the advice that accompanies it.
Assuming a renewal exists. The costliest surprise is calendar-shaped: discovering at quote time that the SKU you planned to renew left the price list in July 2025. If a Standard term expires inside your current budget cycle, the migration decision is already live whether or not anyone has scheduled it.
Paying the bundle rate for a thin-SKU workload. VVF’s economics assume you use some meaningful part of what it adds. An estate that deploys it exactly as it deployed Standard — hypervisor, vCenter, nothing else — pays the full-bundle rate for the old footprint. If that is the plan, the unconsumed components belong in the negotiation as explicit cost, not in the roadmap as aspiration.
Letting the 9-versus-8 framing rush the decision. “Standard is end of sale and vSphere 9 has shipped” sounds like urgency, but the 8 branch is supported into late 2027. The deadline that matters is your term end and the support horizon, not the marketing calendar. Conversely, do not let the runway breed complacency: replatforming an estate takes most organisations longer than they expect.
Repeating minimum-core folklore. The withdrawn 72-core per-order minimum still circulates as if in force, and sizing decisions get made on it. The floor that exists is 16 cores per CPU. Both over- and under-counting flow from commentary; the only reliable source is the terms on your own quote.
Co-terming away your leverage. Folding a Standard estate’s migration into a larger VCF or VVF agreement can buy discount, but it also moves your most mobile workloads — the ones with genuine alternatives — inside a single renewal event where they anchor nothing. Decide deliberately which clusters belong in the big agreement and which stay independent.
No. Broadcom closed vSphere Standard to new purchase and renewal at the end of July 2025. A Standard subscription runs to the end of its current term and then ends; the quoted successor is VVF or, for full-stack estates, VCF. There is no like-for-like renewal path.
No. The vSphere 9 generation ships only inside the VVF and VCF bundles. A Standard entitlement keeps the estate on the vSphere 8 branch, which remains supported into late 2027 for customers with active subscriptions or support. That gap between term end and support end is the realistic planning window.
The hypervisor steps up from Standard’s feature set to the full enterprise tier — DRS, the Distributed Switch and the higher-end availability features Standard never included — plus vCenter, a Kubernetes runtime, foundational operations tooling and a 0.25 TiB-per-core vSAN entitlement. Whether those are a benefit or shelfware depends on whether the estate was designed to use them. The next tier up is compared in VCF vs VVF.
A 72-core per-order minimum was announced to take effect in April 2025 and was withdrawn within days after broad pushback; Broadcom subsequently characterised it as never officially sanctioned. The floor that remains in force is 16 cores per physical CPU. Verify the minimums on your own quote rather than on commentary in either direction.
They keep functioning. A perpetual licence whose support has lapsed continues to run the version you hold, without updates, security patches or vendor support. Some organisations run static, isolated clusters that way as a bridge — the trade-offs are covered in the perpetual-versus-subscription guide.
No. This is a directory, not a ranking. Firms are listed alphabetically with balanced pros and cons. Independence is shown as a pro and reseller, Big-Four or vendor-side-audit ties as a con, both stated as factual trade-offs for you to weigh.
Mapping a Standard estate onto the 2026 catalogue, pricing the three end states against each other and walking into the migration quote with leverage designed in — that is precisely the work of a VMware licensing advisory engagement. The Broadcom VMware hub maps the vendor’s wider licensing world, and the directory lists every firm covering VMware — with balanced pros and cons, listed, not ranked. New to choosing an advisor at all? Start with how to choose a software licensing consultant.
The two live bundles, head to head →
What Broadcom changed, and your three end states →
Every firm for this work →
The renewal-event playbook and its firms →
Filtered, listed, not ranked →
Every field guide on the site →
Tell us the vendor, the service you need and where things stand, and we will route your brief to firms that genuinely cover that combination. The directory and matching are free for buyers, no vendor ever sees your brief, and we add no markup.
Our weekly dispatch on vendor audit programs, regional developments and one buyer move. Subscribe to The Licensing Radar.