Broadcom’s New Licensing Model for Smaller vSphere Environments

Broadcom has introduced VMware vSphere Express, a new, lower-cost licensing option for smaller vSphere environments. It is aimed at customers who still want the familiar vSphere experience without being pushed into the larger VMware Cloud Foundation (VCF) bundle.

In my opinion, this is a good move from Broadcom. After the licensing changes that left many SMBs and smaller VMware customers frustrated, vSphere Express gives them a practical option to stay on the platform they know.

What is vSphere Express?

vSphere Express is built on vSphere 9 and is positioned as cost-effective essential virtualization for smaller environments. It provides the core virtualization capabilities many customers actually need, while limiting the scale and licensing complexity.

The offering is available immediately in all regions and supports up to 128 cores per customer or site ID.

Included essential capabilities include:

vMotion for live migration of running VMs, with improved migration speed and efficiency
High Availability (HA) for automated restart of failed virtual machines.
Distributed Switch for centralized network management and advanced monitoring.
vCenter Quick Patch for low-impact, rapid patch management.
Zero-Trust Security, including TPM 2.0 and vTPM 2.0 support.

The licensing model

vSphere Express uses a subscription-based, per-core licensing model. The important detail is that the license is capped at 128 cores per customer or site ID, and the default license cannot be split into smaller licenses or shared across sites.

Area	vSphere Express
Target customer	Smaller environments needing essential virtualization.
Maximum capacity	Up to 128 cores per customer or site ID.
Licensing	Subscription-based; one default license, not split or shared across sites.
Core features	vMotion, HA, Distributed Switch, Quick Patch, TPM/vTPM support.
Management	Discrete instances; no central management across instances.
Upgrade path	Can be extended to vSphere Foundation or converged into VCF later.

The environment requires ESX, vCenter, VCF Operations, and a license server. Optional components include vSphere Replication, VMware Tools, and VMware Remote Console.

Who is it for?

vSphere Express is primarily for customers who:

Run a small or medium-sized vSphere environment.
Need dependable VM virtualization, HA, vMotion, and basic networking.
Do not need the full VCF platform, automation, advanced operations, or large-scale private-cloud capabilities.
Want to remain on VMware without paying for capabilities they will not use.
May want a future path to vSphere Foundation or VCF as the business grows.

A good example would be a company with two or three ESXi hosts, perhaps 40–80 cores total, running business applications, file/print services, domain controllers, databases, backup infrastructure, and a few customer-facing VMs. For that customer, vSphere Express provides the core vSphere functionality without requiring them to buy into a full VCF deployment.

What it does not replace

This is not a replacement for VCF or vSphere Foundation.

If you need centralized management across many sites, advanced automation, full VCF Operations capabilities, add-on licensing, or more than 128 cores, vSphere Express is not the right fit. The documentation specifically states that add-on licenses are not available and that VCF Operations is used only for licensing in the Express edition.

But that limitation is also the point: it is a simpler product for a simpler requirement.

Why I think this is positive

From my perspective, vSphere Express is a positive signal from Broadcom.

It shows that Broadcom has listened (at least partly) to customers who felt left behind by the move toward larger, more expensive bundles. Ars Technica reports that VMware executives said the product was created after listening to lower-end customers who wanted core virtualization capability but did not want VVF.

For many smaller customers, this could mean:

Keeping existing vSphere skills, tooling, processes, and operational knowledge.
Avoiding an immediate and expensive migration to another hypervisor.
Getting essential features such as HA and vMotion at a lower entry point.
Having a clearer path to grow into VVF or VCF later if needed.

Of course, trust will not be rebuilt overnight. Some customers have already decided to leave VMware, and others remain concerned about future licensing changes. But offering a realistic on-ramp for smaller environments is better than leaving them with only two choices: buy a much larger bundle or migrate away.

The on-premises argument

There is another reason this matters: many customers are reconsidering the cloud.

On Reddit and in customer conversations, I have seen a growing sentiment that moving everything to a public cloud provider is not always the best answer. For latency-sensitive or infrastructure-dependent workloads, on-premises virtualization can simply make more sense.

A common example is the difference between 3 ms and 17 ms latency. For many workloads, that difference may not matter. But for databases, latency-sensitive applications, backup traffic, storage-intensive systems, or tightly integrated internal services, it can have a real impact.

When workloads run on-premises, you control the network path, storage, hardware, firewall rules, and failure domains. When they run in a cloud or managed-provider environment, you may have to wait for the provider to resolve issues outside your direct control.

That can include:

Hardware failures and replacement timelines.
Firewall, routing, or network-policy changes.
Provider-side capacity or platform issues.
Support escalation processes.
More complex troubleshooting across multiple responsibility boundaries.
Additional latency introduced by WAN links, VPNs, or provider networking.

None of this means the cloud is bad. Cloud is excellent for elasticity, global reach, SaaS, burst capacity, and many modern workloads. But it is not automatically the best home for every workload.

For customers with predictable workloads, existing hardware, internal expertise, and latency-sensitive applications, a well-designed on-premises vSphere environment can be faster to operate, easier to troubleshoot, and more predictable in day-to-day performance.

My take

vSphere Express will not solve every concern customers have about Broadcom or VMware licensing. It will not bring back everyone who has already migrated away, and the 128-core limit means it is not suitable for every environment.

But it is still a meaningful step in the right direction.

It gives smaller customers a way to remain on vSphere, preserve their investment in skills and infrastructure, and avoid being forced into a platform bundle they do not need. For organizations that value predictable performance, direct control over their infrastructure, and lower operational complexity, this could be exactly the kind of practical option they have been waiting for.