VMware vSphere Support Alternatives: What Broadcom Means for Your Virtualisation Stack

The Broadcom VCF Mandate: What Actually Happened to vSphere Pricing

Broadcom's management of the VMware acquisition followed a playbook that was entirely predictable to anyone who watched the CA Technologies and Brocade integrations: rationalise the portfolio, force customers into higher-value bundles, and extract maximum short-term value from the installed base. For vSphere customers, this translated into mandatory migration to VMware Cloud Foundation (VCF) subscription licensing — a bundle that includes vSphere, vSAN, NSX, and Aria Suite, regardless of which components you actually use or want.

The commercial consequence was immediate and severe. Customers who had been licensing vSphere Standard or Enterprise Plus at known, budgeted rates found themselves facing VCF pricing that bundled components they didn't need at a total cost 2–5× their prior spend. Broadcom's position was blunt: this is the product now. The previous perpetual licences and à la carte support model were gone.

What Broadcom could not eliminate, however, were your perpetual licence rights to vSphere versions you already own. Customers who purchased vSphere under perpetual licences retain the right to run those versions indefinitely. What they don't retain from Broadcom is the right to cost-effective maintenance. That's where third-party support enters.

VMware vSphere Version Support Matrix

Broadcom has significantly simplified the vSphere support lifecycle since the acquisition, with aggressive end-of-support dates used as migration pressure levers. The table below shows current status across vSphere versions and what third-party support covers at each level:

What Third-Party vSphere Support Covers

Hypervisor and ESXi Security Engineering

VMware ESXi has a substantial CVE history, including hypervisor escape vulnerabilities that carry the highest criticality ratings in enterprise software. Under Broadcom's support model, security patches are bundled with maintenance subscriptions or charged as Extended Support surcharges. Third-party support provides independent ESXi security engineering — vulnerability analysis, patch development, and remediation guidance specific to your vSphere version — without Broadcom's lifecycle pricing pressure.

vCenter Server Operational Support

vCenter Server is the management plane for your entire virtual infrastructure. Configuration issues, performance degradation, certificate expiry, SSO failures, and upgrade path complications are common operational challenges that require deep vCenter expertise to resolve quickly. Third-party support provides 15-minute P1 response for vCenter issues, with engineers who know vCenter's internal architecture rather than working from scripts.

Storage Integration and vSAN Support

Enterprise vSphere deployments depend on storage integration — whether through traditional SAN/NAS, software-defined storage via vSAN, or hyperconverged infrastructure. Third-party support covers vSphere storage layer issues including VMFS datastore problems, RDM configurations, multipath I/O configuration, and vSAN cluster health issues. This is particularly valuable for organisations that run vSAN independently from Broadcom's current VCF vSAN licensing.

Networking and Distributed Switch Support

Distributed Virtual Switches (DVS), VXLAN overlay configurations, and host networking profiles are common sources of production issues in complex vSphere environments. Third-party support provides networking configuration support and troubleshooting for vSphere network components — whether you're running NSX or traditional vSwitch environments.

The vSphere TPS Cost Model by Environment Size

Broadcom's VCF pricing is calculated on a per-core basis, making the total cost directly proportional to your host processor core count. The table below illustrates the financial impact of third-party support versus VCF at representative environment sizes:

Note: VCF pricing estimates based on published Broadcom per-core rates. TPS estimates based on GoVendorFree published rates. Actual costs depend on licence edition, core count, and contract terms.

The Strategic Alternatives Framework

Third-party support is the primary lever for organisations that want to continue running vSphere cost-effectively. But it operates within a broader strategic context, and the right approach depends on your virtualisation roadmap:

Addressing the Hypervisor Support Risk Objection

The most common objection to vSphere third-party support is security risk — specifically, the concern that independent providers cannot match Broadcom's ability to respond to hypervisor vulnerabilities. This objection does not withstand scrutiny for three reasons.

First, vSphere security vulnerabilities are identified and published through standard CVE processes, not through Broadcom's internal research. The vulnerability intelligence that informs patch development is public — what differs is who develops the fix and how quickly. Third-party support providers focus specifically on the versions their clients run, rather than spanning Broadcom's entire current portfolio.

Second, Broadcom's acquisition-era support quality has demonstrably declined. Ticket routing delays, loss of experienced VMware engineers to attrition, and the commercial incentive to push customers toward VCF upgrades rather than fixing issues on supported-but-exiting versions are all well-documented. Independent TPS providers have strong incentives to maintain SLA performance — client retention depends on it.

Third, for organisations on vSphere 6.5, 6.7, or 7.0, Broadcom's standard support is already gone. The choice is not Broadcom support versus TPS — it is TPS versus no support at all.

The vSphere TPS Transition Process

Transitioning vSphere from Broadcom maintenance to third-party support is a commercial and operational process, not a technical migration. No changes are made to your ESXi hosts, vCenter installation, or virtual machine configurations:

1. vSphere estate inventory — Host count, ESXi versions, vCenter version, cluster configurations, and any Broadcom advanced features in use (NSX, vSAN, vSphere Replication). This forms the TPS coverage definition.
2. Perpetual licence confirmation — Verify your licence entitlement against Broadcom's licensing portal. Document your perpetual licence keys and associated entitlements for the TPS contract baseline.
3. TPS coverage assessment — GoVendorFree conducts a technical review of your vSphere environment to confirm coverage scope, identify any configuration anomalies, and establish security patch currency baseline.
4. Contract execution — TPS agreement executed covering hosts, vCenter instances, and SLA terms. Typically completed within 5–10 business days.
5. Broadcom subscription non-renewal — Standard non-renewal notification per Broadcom's contract terms. No technical changes required.

Who Should Consider vSphere TPS?

Third-party vSphere support is the right decision for a specific profile of organisation. You are the right candidate if you are running vSphere 6.5, 6.7, or 7.0 on perpetual licences with no active plan to migrate to VCF in the next 24 months; if Broadcom's VCF pricing represents a 2× or greater increase over your prior maintenance spend; or if you are a financial services, healthcare, or public sector organisation where hypervisor stability and known support costs are board-level requirements.

You should evaluate carefully if you have active NSX or vSAN investments where Broadcom feature development is providing measurable business value, or if you have a firm 12-month timeline to migrate to an alternative hypervisor (in which case TPS as a bridge is still viable but contract terms need to reflect the transition plan).

GoVendorFree has supported vSphere environments across technology companies, financial services firms, and NHS trusts since 2016. Our VMware TPS service covers all vSphere versions, all edition types, and all deployment configurations.