VMware/Broadcom Third-Party Support: The Complete Enterprise Guide (2026)

01. The Broadcom Acquisition: What Actually Changed

When Broadcom closed its acquisition of VMware in November 2023, it wasn't a traditional tech consolidation. It was a PE-style cash extraction playbook applied to one of the world's most critical infrastructure platforms.

Here's what happened, and why it matters for your perpetual licenses:

Timeline of Disruption

• November 2023: Broadcom acquisition closes at $61 billion. VMware's R&D roadmap is immediately restructured.
• February 2024: Broadcom announces end of perpetual licensing. New purchases are subscription-only.
• Q1 2024: Partner ecosystem collapse begins. Thousands of VMware resellers drop support or exit the market entirely.
• Mid-2024: VMware support contracts jump 200–500% at renewal. Forced bundling with VCF and vSphere Foundation.
• 2025–2026: Perpetual license holders face increasingly aggressive renewal pressure and limited options from Broadcom directly.

End of Perpetual Licensing

This is the core shift. For 20+ years, enterprises could purchase VMware licenses outright. You owned perpetual use rights. Support was optional and renewable annually.

Under Broadcom, all new purchases are subscription-based. You pay annually, forever. If you stop paying, your licenses disable. This isn't a technical change—it's a business model forced on the entire installed base.

Forced Migration to Subscription Bundles

Broadcom eliminated à la carte support. When your contract renews, you're offered bundles like VCF (VMware Cloud Foundation) or vSphere Foundation. You pay for hypervisor + NSX + vSAN + integrated management, whether you use all of it or not.

The bundling strategy achieves two things: it raises the floor price, and it forces customers into products they may not need.

Price Increases: 200–500% for Typical Customers

Case in point: a mid-market enterprise with 40 sockets of vSphere 7, 2 vSAN clusters, and NSX infrastructure was paying Broadcom ~$180K/year. At renewal, the same stack under VCF pricing: $780K/year.

That's not inflation. That's extraction.

02. VMware/Broadcom Product Landscape in 2026

The current Broadcom VMware portfolio looks like this:

Core Products & Current Positioning

• vSphere: Hypervisor (versions 7, 8). Subscription-only for new licenses. Versions 5, 6, 7 still supported for perpetual holders.
• vCenter: Management platform. Same licensing model split.
• vSAN: Hyper-converged storage. Critical for many deployments. Bundled under VCF.
• NSX: Network virtualization & security. Now split into NSX-T (traditional) and NSX+. Pushing bundled purchases.
• Aria (formerly vRealize): Monitoring, automation, lifecycle management. Rebranded as part of VCF.
• vSphere Foundation: New bundled offering (vSphere + NSX + Aria). Mid-market target.
• VMware Cloud Foundation (VCF): Broadcom's marquee bundle. All-in-one hypervisor + storage + network + management. Enterprise target. Highest margin.
• Tanzu: Kubernetes/container platform. Subscription model. Orphaned by Broadcom, facing uncertain future.
• Horizon: VDI/remote access. Support continues for perpetual holders, but direction unclear.
• Workstation: Desktop hypervisor. Perpetual licensing model survives here.

What Perpetual License Holders Own (and How Long)

If you purchased perpetual licenses before February 2024, you own unlimited use rights for those versions. Broadcom cannot revoke them. But support eligibility is time-limited:

Key point: Perpetual licenses don't expire. But Broadcom's support timelines are aggressive. vSAN 7.x general support ends October 2029. NSX-T 3.x support is ending this year. If you're running older versions, migration pressure is real.

End-of-General-Support (EOGS) Strategy

Broadcom is using EOGS dates as a squeeze mechanism. When a product version approaches EOGS, Broadcom stops issuing security patches unless you're on active support. Perpetual license holders can't buy support for out-of-support versions, so they're forced to upgrade or switch.

03. What VMware/Broadcom Third-Party Support Covers

Third-party VMware support—also called independent support or TPS—bridges the gap between perpetual licensing rights and operational reality. Here's exactly what it covers:

Core Coverage Areas

• Perpetual License Support: All perpetual-licensed VMware products (vSphere, vCenter, vSAN, NSX, vRealize/Aria, Horizon, Workstation) remain eligible for security patches, bug fixes, and configuration support indefinitely.
• Security Advisories & Patches: TPS providers maintain vulnerability databases and provide patches for CVEs affecting your versions—even when Broadcom has reached EOGS.
• Break/Fix & Troubleshooting: 24/7 technical support with target response times (often 15 minutes for critical). Expert engineers (many are former VMware staff).
• Interoperability Support: Help with hardware compatibility, guest OS support, third-party application integration. This is where TPS often outperforms Broadcom.
• Performance Tuning & Optimization: Capacity planning, resource optimization, architectural reviews.
• Compliance & Regulatory Support: Evidence of support for audits, compliance reporting (DORA, NIST, ISO 27001, PCI DSS).

What's NOT Covered

Be clear on boundaries:

• Broadcom cloud/SaaS products (Aria Operations Cloud, etc.).
• New feature development (TPS is maintenance-focused, not R&D).
• Products that require Broadcom IP or proprietary integrations (some newer Aria modules).
• Professional services (deployment, migration planning). Most TPS providers offer these separately.

The Perpetual License Question: "Can They Really Support It?"

Yes. Here's why:

Broadcom doesn't own the intellectual property to vSphere 7, vSAN 7, NSX-T 3, etc., in the way you might think. These are mature, stable platforms. TPS providers have:

• Deep internal expertise (many staff are ex-VMware engineers with 10+ years tenure).
• Access to publicly available security research and patch repositories.
• Relationships with hardware vendors and ecosystem partners.
• Direct customer feedback loops that often detect issues before Broadcom's internal teams.

They don't need Broadcom's source code to support perpetual licenses effectively. In many cases, TPS is more responsive than Broadcom support for vSphere 7.x and earlier.

04. The True Cost of Staying With Broadcom

Let's be concrete about what subscription-based VMware support actually costs:

VCF Forced Bundling

Broadcom's ideal scenario: you move to VCF at renewal. Pricing:

• Per-core licensing (now the standard): $120–$180/core/year for VCF Advanced or Premier.
• Per-socket legacy pricing (still available but discouraged): $4,000–$8,000/socket/year.
• Bundled features: vSphere + NSX + vSAN + Aria Operations + Kubernetes Tanzu (whether you use it or not).

The Per-Socket to Per-Core Shift

This is where Broadcom's math explodes. A typical server: 2 sockets × 10 cores/socket = 20 cores per socket × 1,000+ servers = 20,000+ cores to license. At $150/core/year, that's $3M for what might have been $500K under per-socket perpetual licensing.

Annual Subscription Lock-In & True-Up Exposure

Broadcom employs aggressive true-up clauses:

• Contracts include audit rights for 3–5 years post-signature.
• Any miscalculation in core counts triggers back-true-up charges (often at 130–150% of standard rates).
• VMware's license audits are among the most aggressive in the industry. Expect them.
• Annual price increases: typically 3–5%, sometimes higher for renewals.

Real Example: 5-Year Cost Comparison

This is not an outlier. This is the median mid-market story. Broadcom's business plan depends on perpetual holders accepting subscription economics or exiting.

05. The Legal Position: Your Perpetual License Rights

This section matters because Broadcom's sales team will tell you your perpetual licenses are "worthless" without active support. They're wrong, and here's why:

What Perpetual Licenses Actually Grant

A perpetual license grants you unlimited use rights for that version in perpetuity. Check your licensing agreement:

• You own use rights. Not the code, but the right to run it.
• They don't expire. Your vSphere 7.0 perpetual license is valid 30 years from now.
• Support is separate. Use rights and support contracts are distinct line items in your original purchase order.
• You can transfer them. Some perpetual licenses are transferable (check your purchase agreement).

EULA Analysis: What Broadcom Can—and Can't—Do

Broadcom's end-user license agreement (EULA) tries to blur this boundary. Common clauses:

• "Support is required for security updates." — False for perpetual licenses. CVEs can be addressed through patches you obtain separately.
• "Use of unsupported versions violates the EULA." — Broadly rejected by enterprise legal teams. You have use rights; how you manage security is your responsibility.
• "Broadcom may revoke licenses of customers in non-compliance." — This claim is unenforceable for perpetual licenses. You paid outright.

The EULA is a contract written to discourage perpetual license holders from using TPS. It's not a technical mandate.

The Compliance Argument vs. The Real Risk

Broadcom's pressure: "Running vSphere 7 without Broadcom support puts you in violation of compliance frameworks (PCI, HIPAA, ISO)."

The reality: Compliance frameworks require documented security practices and patch management. You can document third-party support as your patch authority. Most regulators accept this. Some (large financial services, healthcare) have stricter vendor stability requirements, but even they typically allow TPS with proper SLAs and audit trails.

06. Security Without Broadcom Support

The biggest fear: "If we don't have Broadcom support, how do we stay secure?"

This is a reasonable question. Here's how TPS addresses it:

How TPS Providers Handle CVEs for VMware Products

• Vulnerability monitoring: TPS providers subscribe to security research feeds (NVD, VMware's own disclosures, CISA, academic sources) and alert customers to relevant CVEs.
• Patch analysis & sourcing: For perpetual-licensed versions, TPS provides patches from Broadcom's public repositories, community sources, or develops targeted mitigations.
• Testing & validation: Before deployment, patches are tested in representative customer environments (often shared labs with multiple customers, so cost is distributed).
• Emergency response: Critical 0-days trigger 24/7 response. Most TPS providers guarantee sub-4-hour response for Severity 1 CVEs.
• Audit trail: Everything is documented—patch applied, date, testing results, customer approval. This satisfies compliance auditors.

Broadcom's "Critical Patch Access Requires Active Support" Claim

Broadcom claims that critical security patches are exclusive to active support customers. This is false for perpetual-licensed versions.

Here's the distinction:

• Broadcom subscription products: VCF, vSphere 8 subscription, etc. These require active support for patches. Fair enough—you're on a subscription model.
• Perpetual-licensed versions: vSphere 7, vSAN 7, NSX-T 3, etc. These have documented CVEs. Broadcom publishes patch advisories publicly. TPS providers access the same public advisories and patches your Broadcom account would provide—sometimes faster, because they're not gated by Broadcom's slow patch release cadence.

Example: VMware released CVSS 9.8 advisory for vSphere 7.0 in Q4 2024. Broadcom took 8 weeks to publish a patch. A major TPS provider had a mitigation deployed to 40+ customers in 10 days. Which is more secure?

Regulatory Compliance Without Vendor Support

Major frameworks (and how TPS satisfies them):

• DORA (Digital Operational Resilience Act): EU financial services. Requires documented incident response and vendor management. TPS with 24/7 SLA meets this. Broadcom support may not (slower response, higher costs reduce practical resilience).
• NIST Cybersecurity Framework: Requires asset management, vulnerability management, patch management. Third-party support with documented patch procedures satisfies this.
• ISO 27001: Requires change management and patch controls. TPS-supported stacks can achieve this certification.
• PCI DSS: Requires regular security testing and vendor stability. TPS with long-term support commitments (usually multi-year contracts) provides stability. Broadcom's perpetual license abandonment creates uncertainty.

In practice: major financial institutions run perpetual VMware stacks on TPS. Their compliance teams have cleared it with auditors.

07. Evaluating Your VMware Escape Options

You have three realistic paths forward. Let's evaluate each:

Option A: Accept VCF Subscription

When this makes sense:

• You're a small shop (< 50 VMs). The absolute cost is low, and management overhead is minimal.
• You have heavy reliance on VMware's ecosystem (Tanzu, NSX+ advanced features, Aria cloud).
• You're already on vSphere 8 and willing to move forward aggressively with Broadcom's roadmap.

When it doesn't:

• You operate 500+ VMs. The per-core math is brutal ($3M+ for 5 years).
• You run stable, mature stacks (vSphere 7, vSAN 7). You don't need new features. You need reliability and cost management.
• Your budget is fixed. Subscription models make budgeting unpredictable (annual increases, audit surprises).

Option B: Migrate to Alternative Hypervisor

Real alternatives exist:

• Microsoft Hyper-V + Azure Stack HCI: Strong if you're a Windows/SQL Server shop. Licensing is simpler (per-core, but lower rates). No aggressive audit culture. Multi-year roadmap clarity.
• Proxmox VE: Open-source, perpetual licensing model. Lighter resource footprint. No vendor lock-in. Smaller ecosystem, but growing.
• Nutanix: Hyper-converged with strong management. Subscription model (also a con). Better vendor stability than VMware post-Broadcom. Good for greenfield deployments.
• OpenStack (KVM): For highly technical teams. Complete control, no licensing fees, but heavy operational burden.

Migration costs (rough estimates):

• Professional services: $200K–$1M depending on scale.
• Downtime/testing: 3–6 months project timeline.
• Staff retraining: 2–4 weeks per engineer.
• Payback: 2–4 years if your VMware renewal savings exceed migration costs.

Option C: Hybrid (The Smart Play)

This is what most mid-market enterprises choose:

• Year 0–2: Stay on perpetual VMware + move to third-party support. Save 60–70% on support costs. Reduce Broadcom renewal shock.
• Year 2–3: Selective migration. Move non-critical workloads to Hyper-V or Proxmox. Keep VMware for business-critical apps that require specific ecosystem dependencies.
• Year 3–5: Re-evaluate. If migration is successful, consolidate on the alternative. If it's costly, continue hybrid with TPS indefinitely.

Financial example: 500-VM shop, currently paying $600K/year to Broadcom (VCF). Switch 150 VMs to Hyper-V over 2 years ($150K in migration costs). Remaining 350 VMs on TPS ($250K/year). Result: break-even in 12 months, then $350K/year in savings long-term. Option C doesn't require a big-bang migration or risk.

5-Question Decision Framework for CIO/CFO

1. What's your current VMware stack size (VMs, clusters)? If < 100 VMs, VCF may be acceptable. If > 500, alternatives become ROI-positive.
2. How dependent are you on VMware-specific features? Tanzu, NSX advanced, Aria? If heavy, hybrid approach. If light (just hypervisor + basic mgmt), full migration is viable.
3. What's your 3-year CapEx budget for infrastructure? Can you absorb migration cost? If yes, plan for it. If no, TPS buys you time.
4. How risk-averse is your organization? Hypervisor migrations are low-risk operationally (proven tech) but high-risk politically (fear of change). Hybrid spreads risk over time.
5. What's your Broadcom renewal date? If it's 6 months out, TPS is the immediate play. If it's 18+ months out, plan a 3-year hybrid transition.

08. How to Transition to VMware Third-Party Support

If you decide to move to TPS, here's the 4-phase process:

Phase 1: Assessment (Weeks 1–4)

• Audit your current VMware environment: vSphere versions, VM count, vSAN clusters, NSX deployments, Aria usage.
• Identify what's truly perpetual-licensed vs. subscription.
• Document support expectations: response time, coverage scope, escalation paths.
• Evaluate TPS providers (usually 2–3 bids). Ask for references from similar-sized customers.

Phase 2: Agreement (Weeks 4–8)

• Negotiate TPS contract. Key terms: SLA, pricing, scope (include training/consultation?), renewal terms (should be multi-year to lock in pricing).
• Clarify what Broadcom support you're ending. Usually, terminate Broadcom at contract anniversary, don't overlap.
• Agree on transition planning: do you need Broadcom support for 30–60 days post-TPS start to ensure continuity?

Phase 3: Technical Onboarding (Weeks 8–12)

• TPS provider accesses your environment (remote, read-only initially).
• Deep discovery: performance baselines, known issues, custom configurations, integrations.
• Knowledge transfer with your team. TPS folks learn your stack. Your team meets the support engineers.
• Test case: run a non-critical issue through TPS support to validate process and response time.
• Finalize escalation paths, on-call rotation, compliance documentation.

Phase 4: Steady State (Week 12 onwards)

• TPS is primary support. You may keep Broadcom for a grace period, but stop using it.
• Quarterly business reviews with TPS provider: utilization, emerging issues, cost optimization.
• Annual planning: capacity forecasts, planned upgrades, compliance audits. TPS advises on strategic decisions.

What Broadcom's Account Team Will Say (and How to Respond)

Broadcom: "Third-party support isn't certified. You'll void your license."

Response: "Perpetual licenses don't require certification of support. My use rights are separate from who provides support. This is documented in my original purchase agreement."

Broadcom: "If you get hacked and the root cause is an unsupported VMware version, you're liable."

Response: "I'm hiring a third-party provider to manage security patching. This is documented, auditable, and compliant with PCI/NIST/ISO frameworks. I'm taking responsibility for security, which is my job regardless of who the support vendor is."

Broadcom: "We can match TPS pricing if you commit to VCF."

Response: "Show me the math on per-core licensing for my stack. If Broadcom can match TPS pricing on perpetual licenses, we'll talk. But historically, Broadcom's 'matching' offers require subscription commitments and don't account for hidden costs (audit, true-up, annual increases)."

Timing: When to Make the Move

Best times to transition:

• 90 days before renewal. Switch to TPS before your next Broadcom renewal. Avoids paying for two years of Broadcom support.
• Mid-contract. If you're 18 months into a 3-year Broadcom deal, early exit may cost less than staying. Calculate: remaining contract value vs. TPS cost for same period.
• Avoid: Switching immediately after you just renewed Broadcom. You'll eat a wasted contract cost.

09. Frequently Asked Questions