VMware by Broadcom has signalled that it intends to refresh vSphere Standard for smaller deployments. That part is credible. The claim that a generally available “vSphere 9 Standard” already exists for customers up to 128 logical CPUs is not. As of 8 September 2026, it is a future product direction backed by executive comments, not a released SKU, published licensing programme, or contractual entitlement.
That distinction matters. Organisations should not purchase VMware Cloud Foundation (VCF) merely because someone assumes it is the only future path for a small estate. Equally, they should not make renewal, architecture, or migration decisions on the assumption that a 128-core vSphere Standard offer is available today. Both conclusions get ahead of the evidence.
The short answer
At VMware Explore 2026, Paul Turner, Chief Product Officer of VMware by Broadcom’s Cloud Foundation Division, told The Register that VMware had corrected the sales incentives that pushed customers toward VCF and had sometimes put too much emphasis on VCF. The report says that VMware will soon release an updated vSphere Standard. Ram Velaga, President of Broadcom’s Infrastructure Software Group, positioned the offer for organisations operating around 128 cores. Turner indicated that further details, including the route to market, were expected around VMware Explore Germany in mid-October.
That is a meaningful signal. It is also incomplete. VMware has not publicly documented a release date, product version, price, minimum commitment, feature matrix, channel availability, support model, or licence metric for this prospective refreshed offer. In particular, it has not stated that 128 cores is a hard ceiling, a licence bundle size, or a purchasing threshold.
First correction: it is “around 128 cores,” not “128 lCPU”
The reported wording is around 128 cores. It does not say 128 logical CPUs, 128 vCPUs, or 128 licensed processor threads. These are materially different quantities.
|
Term |
What it means |
Why it must not be substituted for the reported figure |
|
Physical CPU core |
A physical processing core in a server CPU. |
The executive comment uses the generic word “cores,” but VMware has not yet published the commercial definition for the future offer. |
|
Logical CPU (lCPU) |
A hardware execution thread exposed by a host. With simultaneous multithreading enabled, one physical core commonly exposes two logical CPUs. |
128 logical CPUs could represent roughly 64 physical cores on a two-thread-per-core host. It is not a valid reading of “around 128 cores.” |
|
vCPU |
A virtual processor assigned to a virtual machine. |
vCPU allocation is a workload-sizing measure, not a host licensing measure. |
|
128-core entitlement or cap |
A contractual purchasing or usage boundary. |
No public statement has established one. Treating the positioning comment as a cap is unsupported. |
This is not pedantry. A licensing decision based on a logical-CPU count when the vendor is discussing cores is an avoidable error. Until VMware publishes the SKU and ordering guide, call this a market-positioning signal, not a licence rule.
What is actually confirmed
The evidence supports a narrow but important conclusion: VMware by Broadcom is re-engaging with the smaller virtualisation market and plans an updated vSphere Standard. The Register directly attributed the statements to Turner and Velaga. Techzine independently reported the same interview outcome and likewise described a new vSphere Standard as forthcoming, with more details expected at VMware Explore Germany.
The current official VMware vSphere page also lists vSphere Standard as a standalone subscription choice and positions it as “basic server virtualization for development and testing environments.” This confirms that Standard remains a product identity in VMware’s portfolio. It does not, however, identify a vSphere 9 Standard edition or reveal commercial terms.
“We corrected this,” Turner told The Register when discussing incentives that drove sales teams to VCF. He added that VMware had sometimes had “too big a focus on VCF.”
For smaller customers, that change in commercial posture is potentially more significant than any single technical feature. It recognises that basic virtualisation and a full private-cloud stack are different buying decisions.
What is not confirmed—and why that matters
VMware’s own current vSphere 9.1 FAQ is unambiguous: standalone vSphere Standard and vSphere Enterprise Plus are limited to vSphere 8 Update 3 and earlier. It states that vSphere 9.0 and 9.1 features are available only through VMware vSphere Foundation (VVF) 9.0/9.1 and VMware Cloud Foundation (VCF) 9.0/9.1. The official version-comparison document repeats the same position.
The implication is straightforward. A refresh has been signalled, but the authoritative public documentation still says that there is no standalone vSphere Standard for vSphere 9.1. Until that documentation changes and an orderable SKU exists, “vSphere 9 Standard is back” is a premature headline.
|
Question |
Public position as of 8 September 2026 |
Practical consequence |
|
Is VMware planning an updated vSphere Standard? |
Yes, credibly signalled through executive comments reported by The Register. |
Monitor the upcoming commercial announcement. |
|
Is standalone vSphere Standard available for vSphere 9.0 or 9.1 today? |
No, according to current official FAQ and comparison material. |
Do not design a near-term implementation on the assumption that it can be ordered. |
|
Is 128 cores a strict limit, a licence pack, or an entitlement? |
No public evidence. The reported language is “around 128 cores.” |
Do not translate it into 128 lCPU, 128 vCPU, or a guaranteed commercial threshold. |
|
Will small customers no longer be forced into VCF? |
Not yet a contractual guarantee. The reported correction of sales incentives is encouraging, but route-to-market terms remain unpublished. |
Obtain a written quote and SKU-level terms before treating Standard as a renewal option. |
|
Will the future offer include memory tiering? |
Possible, not confirmed. Turner mentioned it as a possible feature. |
Do not base a hardware plan on it yet. |
Where VVF and VCF fit while we wait
Today’s documented vSphere 9 path remains VVF or VCF. Broadcom’s 2024 portfolio announcement established VCF and VVF as its flagship subscription offers. VVF targets the traditional vSphere estate with broader operational and Kubernetes capabilities, while VCF is the complete private-cloud stack. The current VCF 9.1 licensing documentation describes term subscriptions and primary licences for VCF and VVF, with VCF capacity expressed in cores.
This means the immediate decision should remain technical and commercial, not emotional. Choose VCF where you genuinely need the integrated private-cloud platform, including the fuller stack and its lifecycle model. Choose VVF where the vSphere 9 feature set and included operational capabilities fit the estate, but the full VCF platform is not justified. Retain or renew vSphere Standard 8 Update 3, where available and appropriate, only with a clear support and lifecycle plan. A prospective vSphere Standard refresh is a reason to delay an irreversible platform decision when the timing permits; it is not a reason to ignore current support dates, procurement lead times, or business risk.
What smaller customers should do now
First, ask your Broadcom representative or authorised partner for a written statement of the currently orderable option for your estate. Verbal positioning is not a quote. Request the exact SKU, version eligibility, subscription capacity, minimum purchase, included support, renewal conditions, and regional availability.
Second, count the estate correctly. Record physical sockets, physical cores, logical CPUs, vCPUs, vSAN capacity, and the required availability and security services separately. Do not collapse those values into a single “CPU” number. That bad habit produces bad licensing comparisons.
Third, create a decision gate around VMware Explore Germany. The reported announcement window makes it a rational checkpoint for customers with renewal flexibility. If your renewal occurs before clear terms are published, price the documented options—VVF and VCF—alongside the cost and risk of a short renewal or bridge strategy. Do not assume a future Standard SKU will be backdated or automatically available to every existing customer.
Finally, demand a feature comparison before accepting the word “Standard” as an answer. The eventual value will depend on the precise vSphere 9 features included, whether memory tiering lands in the edition, lifecycle tooling, support coverage, and the economics relative to VVF. The product name alone does not resolve any of that.
Bottom line
The rumour has a solid factual basis: VMware by Broadcom has signalled an updated vSphere Standard aimed at environments of around 128 cores, and it has acknowledged that sales incentives over-favoured VCF. That is good news for smaller vSphere customers.
But the precise claim needs discipline. There is no public evidence that vSphere 9 Standard is generally available today, that 128 is a licence boundary, or that the threshold is 128 logical CPUs. Current official documentation still limits standalone Standard to vSphere 8 Update 3 and earlier.
So the rational position is neither “nothing has changed” nor “VCF is dead for small customers.” It is this: a credible lower-end option is coming, but it is not a product you can safely architect or procure against until VMware publishes the SKU-level facts.
References
[1] VMware swings its focus back to low-end server virt, promises vSphere Standard upgrade
[2] vSphere with VCF 9.1 General FAQ
[3] VMware vSphere Version Comparison
[5] Licensing Overview for VMware Cloud Foundation 9.1
[6] VMware End Of Availability of Perpetual Licensing and SaaS Services
