Summary
- The counting rules are public and exact: a core is "a single physical computational unit of the Processor", every core on the Server must be licensed, and each processor carries a floor of 16 Cores — so an eight-core CPU is billed as sixteen. None of the nine Broadcom documents read here prints a per-core currency figure or a subscription length.
- Three partner compilations put the same vSphere Foundation core-year at $135, $150 to $190 and about $155. By my own multiplication the floor on a single processor spans $2,160 to $3,040 a year across those figures, roughly 1.41 times, on a quantity Broadcom states precisely.
The unit has a definition, a floor and a formula
Start with the document that sells the thing rather than the one that prices it. The vSphere Standard Specific Program Documentation dated May 2026 opens with definitions, and its first one is short: "Core" means a single physical computational unit of the Processor. The same document describes the Processor as "a single, physical chip that houses at least one Core that can execute computer programs". The June 2026 program document for VMware vSphere Foundation states the commercial basis in a single line: License Metric. Software is subscription software licensed on a per Core license metric with a minimum licensing requirement of 16 Cores per Processor.
Note what those two sentences do not contain. No dollar sign, no euro, no term in months. A licence metric and a minimum. That is the whole of the commercial statement.
The definition is not a stray clause. The VMware Licensing Glossary defines a Core as a Physical Core in a physical computing environment, defines Physical Core as "a single physical computational unit of the Processor", and defines a Hyperthread as "a technology by which a single physical core is shared between 2 logical cores" — which tells you, before any arithmetic, that the two logical processors a hyper-threaded core presents are not two licensable cores on the host.
Sixteen cores for a CPU that has eight
The floor is stated three times, in three frames. The core-counting article for VMware Cloud Foundation and vSphere Foundation puts it as a heading — "Key Licensing Rule: The 16-Core Minimum" — and then as an instruction: "You must license a minimum of 16 physical cores for each CPU (physical processor) in your ESXi hosts, even if a CPU has fewer than 16 cores." The vSphere 9 capacity article opens with "vSphere 9 implements a per-core licensing model with a mandatory minimum of 16 cores per physical CPU (socket)" and reduces the rule to a formula: total capacity needed = number of CPUs × max(16, physical cores per CPU). The vSphere 8 licensing page gives the buyer the same instruction in the second person: total the physical CPU cores for each CPU on all ESXi hosts, one licence per core, and "the minimum license capacity you can purchase is 16 cores per CPU".
The worked example is Broadcom's own, and it is where the floor stops being a footnote. A host with two eight-core CPUs is counted as two times sixteen, or thirty-two licensable cores. A host with two twenty-four-core CPUs is counted as forty-eight. Together, eighty.
Here is my arithmetic on that example, and it is mine, not Broadcom's. The eight-core machine carries sixteen physical cores and thirty-two billable ones: a multiplier of 2.0. The twenty-four-core machine carries forty-eight physical cores and forty-eight billable ones: a multiplier of 1.0. Across the pair, eighty billable against sixty-four physical, 1.25. A four-core CPU would sit at 4.0; a twelve-core CPU at 16 ÷ 12, or about 1.33; anything at sixteen cores or above at 1.0.
That is what a floor priced per core does that a meter does not. Below sixteen cores the invoice stops tracking the machine. And the floor reaches parts of the machine a buyer may not think it owns: the program documentation requires every Core on the Server to be licensed, "including Cores deactivated by the BIOS", and the counting article warns that BIOS-disabled physical cores can make Broadcom's own counting script inaccurate and says all physical CPU cores should be activated for an accurate count.
The ceiling lives in another instrument
Every VMware buyer has heard that the licence is capped at thirty-two cores per CPU. In the documents read here, that cap belongs to a different meter. The vSphere 8 licensing page lists four licensing models, and the thirty-two-core per-CPU arrangement is one of the others, requiring additional CPU licences above thirty-two cores. Attaching it to the per-core subscription would bolt one instrument's ceiling onto another instrument's unit.
A five-hundred-and-twelve-core ceiling on vSphere Standard appears on a consultancy price guide reviewed on 4 November 2026 — not in any Broadcom document read here. And the order minimum is a live disagreement: one partner page describes a seventy-two-core minimum order as part of the current terms, while the same consultancy guide says a 2025 seventy-two-core minimum has since been dropped. No Broadcom-authored document in this corpus prints an order minimum at all. On the public vendor record, a reader cannot settle it.
Two registers, one machine
The glossary adds a second counting rule with a different subject: "In cases where Hyperthreading is not enabled, one (1) vCPU is recognized as one Core. In cases where Hyperthreading is enabled, two (2) vCPUs are recognized as one Core." That rule is about a vCPU presented in a virtualised or public-cloud environment. The host rule is about the Server.
Put them side by side and the gap is visible. A host with two eight-core CPUs and hyper-threading enabled presents thirty-two logical processors. Under the vCPU rule, thirty-two vCPUs recognise as sixteen Cores. Under the host rule, the same machine bills thirty-two Cores. Both numbers come from Broadcom documents. Neither is wrong — they answer different questions — and no document read here prints the step between them, or a conversion from a cluster's socket count to the billable core total beyond the host-level formula itself.
The vendor's instruction to the buyer is consistent about what to count and silent about how to total it: the physical CPU cores for each CPU, across all ESXi hosts, with every core on the server licensed. Sockets are the unit of the floor. Cores are the unit of the price. The buyer's own asset register may hold either.
The numerator is quoted
Now the part that is not in the licensing documents. Nine Broadcom-authored documents were read for this briefing — two program documents, a glossary, two knowledge-base articles, a product documentation page, a portfolio announcement, a product guide and a foundation FAQ. None of them prints a per-core currency figure for vSphere Standard, vSphere Foundation, vSphere Enterprise Plus or Cloud Foundation.
The nearest thing to an official number is a refusal, reported. On 4 November 2026 The Register recorded that a Broadcom spokesperson described the new vSphere Express rate as "significantly lower" than VVF or VCF and "declined to quote a dollar amount", with customers directed to a reseller for pricing and terms. An adjective is not a rate.
The channel fills the space, and disagrees with itself. AceMQ states plainly that "Broadcom publishes no rate card: list prices are the partner price list as reported by Veeam Community and Rimini Street, checked 20 October 2026", and lists vSphere Foundation at $135 per core per year and vSphere Standard at $50. Blue Sky Systems prints a SKU line — "VMware vSphere Foundation 8 1YR | VCF-VSP-FND-8 | $190 per core" — with multiyear at $150 and vSphere Standard 8 at $50. C4C Group opens with the caveat that "Broadcom does not publish a universal price list, but the indicative public list figures widely reported for the three subscription tiers are set out below, quoted per core per year", and puts vSphere Foundation near $155 and vSphere Standard near $55.
Three pages, one edition, three answers. Mine again: sixteen cores at $135 is $2,160 a year on a single processor; at $150, $2,400; at $155, about $2,480; at $190, $3,040. The highest over the lowest is roughly 1.41 — the same CPU, the same floor, a floor price that moves by about two-fifths depending on which partner page a buyer happens to read. For vSphere Standard, sixteen cores is $800 at $50 and $880 at $55.
There is one place where a per-core rate can be derived from a package rather than asserted. The consultancy guide describes vSphere Express as a fixed 128-core, one-year package listed by a distributor at $9,600 a year — $75 a core, by the division that page prints and I only check.
The term is defined, not dated
The April 2024 VMware Product Guide defines the object without dating it: "Subscription Software means Software that is licensed for a specific term and includes Support Services (at the Support Services level purchased) for the duration of such term (Subscription Term)." A specific term is still a blank. No Broadcom-authored document read here fills it with a number of years for these editions.
What Broadcom does print are calendar dates. The 4 November 2026 portfolio announcement states that "vSphere Standard version 8 and vSphere Enterprise Plus version 8 will remain available for sale until October 31, 2027, and will have Extended Support included in any active subscriptions to those offerings until the earlier of the applicable subscription end date or October 31, 2028", and introduces vSphere Express for customers with 128 cores across all environments. The vSphere Foundation 9.1 FAQ dates general availability to 5 May 2026, describes subscription-based licence files, and states that perpetual licences cannot be upgraded without moving to subscription.
So the buyer gets an end-of-sale date, a support date, a product generation and a licence file — and the one number that turns a per-core rate into a forecast, the term, stays in the quotation.
What is new in this reading
BTW already holds five published VMware articles and a shelf of event cards. They cover an AI-factory launch in September, the running cost of infrastructure-software dependency in July, a misconfigured Google network update that broke stretched clusters, ESXi patch debt, and ESXiArgs. Further cards cover the Broadcom acquisition, the Netflix patent suit, AWS's VCF-as-a-service, a Hyper-V comparison and hypervisor basics. None of them reads the licensing unit — what a core is, what the floor does to a small CPU, which register the vCPU rule belongs to, or where the published denominator stops and the quoted numerator starts.
That is the subject here.
What I read, and what that limits
Thirteen documents were read: nine Broadcom-authored, four published by partners and one news organisation. The quotations are page text as returned by retrieval of the exact links above; no page or PDF was opened in a browser session. The May and June 2026 dates are the dates printed in the retrieved text, not inspected file metadata. The glossary, both knowledge-base articles and the vSphere 8 page carried no visible revision date. The vSphere 8 page is version 8.0 documentation while the vSphere 9 rule comes from a separate article, and each is cited with its own version attached.
Two Broadcom product pages requested for this briefing returned HTTP 404 at 23:09 UTC on 20 November 2026 and were never read. They are cited nowhere and their failure is not evidence of what they print. Every absence above is scoped to the thirteen documents named here, never to Broadcom's estate as a whole.
Nothing here says a per-core rate is too high, unlawful or unenforceable, that any customer was overcharged, or that the floor is a penalty. The finding is narrower and harder to argue with: the quantity is documented to the core, and the rate is not documented at all.
The bill has a published denominator
An estate manager can now do something genuinely useful before a renewal conversation. Count cores per CPU, not sockets. Apply the floor: anything under sixteen cores bills at sixteen. Activate the BIOS-disabled cores, because the vendor's own script needs them to count accurately. Then hold the arithmetic in one hand and the quotation in the other, and notice that the first is exact, published, sectioned and dated, while the second is a rate that three public pages cannot agree on.
The instrument is legible from the unit to the floor. It goes blank exactly where the money starts — and a buyer who knows which half is which can at least stop arguing about the wrong one.
VMware's directory record is at VMWare.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






