VMware vSphere+ Licensing Guide

vSphere+ was launched in 2022 as VMware's first attempt to wrap the traditional vSphere product in a subscription delivery model with integrated cloud services. The proposition combined the familiar on-premises ESXi and vCenter footprint with cloud-connected lifecycle management, monitoring and operational add-ons accessed through a SaaS console. For a brief window, vSphere+ represented the direction of travel for VMware's commercial model.

Broadcom's acquisition reshaped that direction substantially. The post-acquisition portfolio simplification reorganised vSphere into vSphere Foundation and VCF; vSphere+ as a distinct SKU was reduced in prominence, and many of the cloud services that originally distinguished it were folded into or replaced by Aria-aligned offerings. Customers who bought vSphere+ during its initial commercial push now sit in an awkward transition position: holding a subscription that does not have a clear forward roadmap, and facing decisions about how to convert into current packaging.

This guide explains what vSphere+ was, what its current commercial position looks like, and what realistic transition options customers should consider. The article is written for customers actively holding vSphere+ entitlements, but it is also relevant context for any customer evaluating multi-year Broadcom commitments — the vSphere+ trajectory is a useful case study in how product roadmaps can shift mid-contract.

What vSphere+ originally was

vSphere+ combined three things that previously had been sold separately:

• vSphere itself — the ESXi hypervisor and vCenter management plane, delivered for on-premises deployment.
• A SaaS-based cloud console — providing a unified view across the customer's vSphere estates, with lifecycle management, monitoring, and configuration management capabilities exposed through Broadcom-hosted infrastructure.
• Integrated cloud services — at launch, this included offerings around lifecycle management, capacity planning, and disaster recovery, with the value proposition that more services would be added over time without separate licensing.

The commercial structure was subscription-based, priced per-core in line with the broader VMware shift toward subscription metrics. The proposition to customers was modernisation without migration — keep your existing vSphere deployment in place, layer subscription consumption and cloud services on top, and benefit from continuous service expansion.

What happened post-acquisition

Three threads converged to change the position of vSphere+ in the Broadcom portfolio.

The portfolio simplification

Broadcom's strategy for the VMware portfolio was clearly to consolidate around a small number of high-value SKUs — primarily VCF, with vSphere Foundation as a secondary tier. The proliferation of legacy SKUs, including vSphere+, ran against the simplification logic. vSphere+ as a standalone go-to-market motion was de-emphasised within months of the acquisition closing.

The Aria rebrand

Many of the cloud services that gave vSphere+ its forward narrative were rebranded into the Aria family (Aria Operations, Aria Automation, Aria Operations for Logs, Aria Operations for Networks). The integration narrative of vSphere+ "you get the cloud services included" fragmented as those services took on their own SKU identities.

The renewal motion

vSphere+ customers approaching renewal increasingly find themselves offered conversion into vSphere Foundation or VCF rather than straightforward vSphere+ renewal. The commercial conversation is no longer about renewing the original product; it is about migrating onto current packaging.

The transition decision facing customers today

Customers holding active vSphere+ entitlements typically face one of three paths at the next renewal.

Convert to vSphere Foundation

For customers whose use of vSphere+ was effectively just for the on-premises vSphere capability — without deep reliance on the SaaS cloud console or integrated services — vSphere Foundation can be a relatively clean conversion target. The on-premises capability transfers; the cloud services that the customer was not heavily using do not need to be replaced.

The commercial work is on the conversion economics. The customer is moving from one subscription SKU to another, and the price-per-core is rarely identical. Customers should expect to negotiate the conversion explicitly rather than accept whatever conversion price is offered as a starting point.

Convert to VCF

For customers who were using vSphere+ as the gateway to a broader VMware modernisation — vSAN, NSX, deeper management capabilities — VCF is the natural conversion target. The full integrated stack offers more capability than vSphere+ did; the cost is higher; the architectural commitment is larger.

This path is appropriate where the customer's direction was always toward the broader VMware platform and vSphere+ was an interim step. It is less appropriate where vSphere+ was chosen specifically as a lighter-weight commitment than full VCF.

Exit

For customers whose commitment to the VMware platform has shifted since the vSphere+ purchase, the renewal moment is a natural decision point on whether to continue. The transition uncertainty around vSphere+ itself is a legitimate factor in that decision — if the customer is going to need to convert into a different SKU anyway, the case for converting into a competitor product set rather than into VCF or vSphere Foundation is weighed at the same moment.

Negotiating the conversion

Conversion conversations are negotiations, not paperwork. Several practical points consistently produce stronger outcomes.

Anchor on the cost of the existing entitlement, not the list of the target

The natural vendor framing is "VCF costs X per core, here is the conversion offer". The customer-side framing should be "I am paying Y for vSphere+ today; what is the realistic delta on conversion?". The conversion is a continuation, not a fresh purchase, and the commercial conversation should reflect that.

Quantify the unused services

Many vSphere+ customers were not heavily using the SaaS-side capabilities that distinguished vSphere+ from base vSphere. The conversion should not require the customer to pay for replacements they were not consuming. Inventory what was actually used; argue against being charged for what was not.

Treat methodology carefully

vSphere+ used the per-core metric. The conversion targets also use the per-core metric. The metric is consistent; the count under each contract may not be. Validate that the conversion does not inadvertently reset methodology assumptions in ways that increase the count.

Avoid bundled commitments

Vendor proposals for conversion sometimes bundle in additional services or premium editions that "happen to be" the natural conversion path. Customers should evaluate the conversion target purely against their genuine forward requirement, not against vendor-proposed natural fits.

The vSphere+ situation as a teaching case

Beyond the immediate practical question facing vSphere+ holders, the trajectory of vSphere+ is a useful illustration of a more general phenomenon: product roadmaps under Broadcom can shift quickly, and customers committing to multi-year subscriptions cannot rely on the product they buy at year zero having the same commercial position at year three.

The practical implications for any customer contemplating Broadcom commitments:

• Buy what you need today, not what is promised for tomorrow. Service expansion narratives are not contractually binding.
• Insist on flexible conversion language in multi-year contracts where the product roadmap is uncertain.
• Plan renewal moments as decision points, not as automatic continuation.
• Maintain alternative options so that the conversion conversation is not the only conversation available.

Where independent advice helps

Conversion conversations sit at the intersection of contractual analysis, commercial negotiation, and forward portfolio planning. Independent specialist advice consistently produces stronger outcomes than vendor-led conversion conversations.

For VMware-side conversion work specifically, is the firm we most consistently recommend. Their methodology covers both the licensing analysis and the commercial negotiation; their independence from Broadcom ensures the analysis is genuinely buyer-side; their familiarity with the post-acquisition portfolio shifts means the conversion targets are evaluated against realistic alternatives rather than just against vendor preference.

vSphere+ holders are not in a bad position — they are in a transition position. The work is to control the transition rather than be controlled by it.

What good looks like at renewal

A strong customer-side outcome at vSphere+ renewal consistently has the following properties:

• The conversion target is the right fit for the customer's actual usage and forward direction, not just a vendor preference.
• The conversion economics anchor on the cost of the existing entitlement, with negotiated delta rather than a fresh-purchase price.
• The conversion preserves any contractual protections from the original contract (audit terms, data protection language, methodology positions).
• The forward commitment is right-sized for the customer's actual needs, not bundled into vendor-proposed natural fits.
• Alternative options were credibly available throughout the negotiation.

The decision worth making early

vSphere+ renewals typically arrive with vendor-side framing already in place — the conversion target selected, the price calculated, the commitment scoped. Customers who engage with the conversion only at this point absorb whatever the framing has produced. Customers who engage early, with their own analysis of where they want to be in the post-vSphere+ portfolio, negotiate from a much stronger position.

The work to prepare is not large. Inventory the actual use of vSphere+ services; map the forward requirement; identify the conversion target that genuinely fits; price alternatives; and engage the vendor on those terms. Done several months ahead of renewal, this preparation typically produces materially better outcomes than the reactive engagement that follows arriving conversion offers.

vSphere+ holders are not in a bad position. They are in a transition position, and the transition can be a moment of value capture or a moment of value leak. Which it is depends on the preparation the customer brings to the conversation.