vSphere Express: a fixed 128 cores, one year, one order per customer

The replacement for vSphere Standard has a code: VCF-VSP-EXP. It has a price: $9,600 a year at TD SYNNEX, €9,631.77 net at Software-Express. It has an availability date: 2 November 2026. And it has a product sheet listing what is in and what is out. The only thing we could not find, as of 4 November, is a public Broadcom announcement.

In September we wrote about an announcement that did not exist: two Broadcom executives had said so to a journalist, on the sidelines of VMware Explore, and behind it there was no version, no date, no price and no feature sheet. Two months later the situation has flipped in a curious way. Now there is a version, a date, a price and a sheet — in the distributors' catalogues — and what is still missing is the announcement. For anyone who has to sign a purchase order, a price list and a commitment are not the same thing.

What the sheets say, and who signs them

Three European distributors have it listed — TD SYNNEX, Software-Express and Serverhero — and the German channel press has picked it up. This is what they agree on:

The context that explains why this is surfacing now: vSphere Standard and Enterprise Plus stopped being sold at the end of October 2026. Express is what is left in the catalogue below VCF for a small estate, under terms that look nothing like the ones Standard had.

The arithmetic of a package that does not flex

Before comparing anything you have to count correctly, and almost nobody does. What Broadcom bills is not your physical cores: it is the minimum of 16 cores per processor. A host with two 8-core CPUs has 16 physical cores and bills 32. In the renewals we have sat through, the number the customer has in their head is almost never the number the vendor bills, and the gap never runs in their favour. That is the sum to do first, and it is what turns this package into one-size-fits-all with exactly one size that fits.

The headline $75 per core is paid only by the fourth row. Everything below it pays the same $9,600 for less machine — twice as much per core on a pair of hosts — and everything above it cannot buy it at all. The package does not adapt to your estate: your estate has to fit the package.

It is worth saying the other part, because it is just as true: $9,600 a year for a four-node cluster with vCenter, HA and vMotion is not outrageous. Compared with what it costs to put that same hardware under VCF, it is cheap. The problem with Express is not the price. It is the rigidity, which is a different thing and gets managed differently.

The three lines that decide whether it exists for you

One order per customer, no expansion. If you add two more nodes next year, there is no second package. What there is, is moving up a tier, with the budget that implies. A package that does not grow with you is good for getting through one financial year, not for planning three.

One year. A twelve-month term turns the question into a different one. It is not "do I buy Express?", it is "what will I have decided by month ten?". That is the part people tend to leave for later, and the one that then gets decided in a hurry.

Eligibility. And this is where the argument turns around. The package presented as the answer for VMware's small customers is reserved, on paper, for customers who are not VMware customers: they never were, or have not bought in three years. If you have spent a decade renewing vSphere Standard, the channel says you need express authorisation and that the details for existing customers were expected in mid-November. As things stand today, for you there is only one honest answer: get it in writing before you design anything on top of it.

In September, when all this was a remark on the sidelines of a conference, Eric Sloof summed it up in a sentence that has aged well: "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". That is eight things. Seven weeks later, the distributor has seven of the eight; the only one still blank on its sheet is the support model.

One important qualifier, because we went looking before writing this: Broadcom does document vSphere Express in its public techdocs. The VCF 9.1 licensing page says that "vSphere Express uses the same licensing infrastructure as VMware Cloud Foundation and vSphere Foundation with some restrictions to license management functions", and clarifies that getting both a default licence and licence keys, which does apply to VCF and vSphere Foundation, "is not applicable to vSphere Express". In other words: the vendor is explaining how to license a product it is not willing to announce. There is technical documentation and there is no announcement, no price, no term and no eligibility signed by them. For anyone who has to take this to an investment committee, that is worse than silence: it looks officially real right up to the moment you ask for it in writing.

DRS is not what hurts most

The first thing everybody looks at in the exclusion list is DRS, and it is the one we would worry about least. Without DRS there is no automatic load rebalancing between nodes: machines get moved by hand or with simple rules, and on a four-node cluster that is entirely manageable. We say this knowing what we sell: our own platform is Proxmox VE with Ceph, and it has no DRS equivalent either. It is not the problem.

What does change a design sits further down the list and gets read with less attention. vSAN is not among the included items: if your storage is vSAN, this package does not cover half your estate, and that has to be settled before signing, not after. GPU and vGPU are out: any plan for accelerated desktops or inference on those hosts falls over. Memory tiering is out: if you were counting on it to densify instead of buying RAM, redo the hardware budget. And with no live patching, every hypervisor patch goes back to being a planned window with its reboot — which is exactly the work that feature existed to save you.

What you are really buying is a calendar

A twelve-month subscription signed in November 2026 expires in November 2027. In the same quarter, vSphere 8 reaches end of general support: 11 October 2027, the date recorded in the TechThoughtLeaders licensing tracker for 8.0 and all its updates. We cite it from there and not from a public Broadcom page, because we could not find it linkable on the vendor's own site. If your estate is on 8.x, it is worth putting next to the other one.

The two dates land virtually together, and that is the reading that matters: Express does not buy you a decision, it buys you a calendar that expires at the same time as the other one. We have already written about why the rollback plan expires on its own when you let the clock run without touching it. This is the same thing, with the advantage that now you know when the alarm goes off.

When we would buy it and when we would not

Among other things, we move people from VMware to Proxmox for a living. Even so, these are the four situations where we say yes to Express:

And these are the four where we say no, however much of a hurry the sales rep is in:

Six things we would ask for in writing before signing

None of the six needs a project. The first two take an afternoon with the inventory in front of you, and they are the ones that change the number. That sum — counting billable cores, reading the SKU small print and putting both dates on the same calendar — is half of a platform consulting engagement; the other half is deciding afterwards, with the numbers in front of you, whether the way out is to renew, to sit still, or to start the VMware to Proxmox migration.

The question that decides this is not whether vSphere Express is expensive. It is how many billable cores you actually have, whether you can even buy it, and what you will have settled by month ten.

Sources. Consulted on 4 November 2026. The fixed 128-core package, the one-year term, the sentence "Pro Endkunde ist nur ein Paket möglich, eine Erweiterung ist nicht möglich", the price of €9,631.77 net and the lists of included and excluded features come from the VMware vSphere Express sheet at Software-Express. The availability date (2 November 2026) and the sentence "Bezug nur für autorisierte Endkunden bzw. definierte Net-New-Kunden" come from the notice published on administrator.de on 28 October 2026, which quotes a supplier email. The $9,600 TD SYNNEX price, the three distributors listing it, the end of sale of vSphere Standard and Enterprise Plus at the end of October 2026, the explicit exclusion of vSAN, the mandatory nature of the VCF Operations instance, the fact that details for existing customers are not expected until mid-November and the absence of any official Broadcom announcement, press release or blog post come from the article "VMware vSphere Express: Kehrtwende oder Schadensbegrenzung?" in ChannelPartner, dated 4 November 2026. The SKU code VCF-VSP-EXP, the three-years-without-purchases rule for net-new eligibility and the $75-per-core equivalence come from the C4C vSphere Express guide. The two Broadcom sentences about licensing vSphere Express ("uses the same licensing infrastructure as VMware Cloud Foundation and vSphere Foundation…" and "is not applicable to vSphere Express") come from the VCF 9.1 Licensing Overview page on techdocs.broadcom.com: there the product is documented, which is precisely the contrast the article draws. The Eric Sloof quote is from his post of 13 September 2026. The 16-core-per-processor minimum is recorded in the TechThoughtLeaders Broadcom licensing tracker, which also warns that the so-called 72-core-per-order minimum has never been publicly confirmed — which is why we do not use it in the table. The five-row table and the per-billable-core costs are our own sums over those two figures ($9,600 and the 16-core-per-socket minimum): they can be redone with a calculator. The end of general support date for vSphere 8 (11 October 2027) circulates in every channel analysis but we could not verify it on a public Broadcom page, and we present it that way in the text. What we say about our own platform (Proxmox VE with Ceph, with no DRS equivalent) is ours and is not backed by any of those sources. The photograph in the social image is "HP Server Board (Top)", by cole8888, CC BY-SA 2.0 via Wikimedia Commons.