Broadcom VMware Support Pricing

The pre-acquisition VMware commercial structure separated licence and support cleanly. Customers held perpetual licences and paid annual SnS (Support and Subscription) at roughly 20-25% of the perpetual licence value. Support could be priced, compared, and negotiated as a discrete commercial line. The post-acquisition Broadcom structure consolidates everything into a subscription bundle in which support is not separately priced and not separately negotiable below a baseline.

This article explains how Broadcom VMware support is priced under the subscription model, what the support tiers actually include, where there is genuine negotiating surface, and what to plan for in your renewal cycle.

Support is embedded in subscription

The subscription price for every Broadcom VMware SKU includes a baseline level of production support. Production support means business-hour coverage for production-impacting incidents, with severity-1 (production-down) cases attracting after-hours response under documented SLAs. The included support is what most customers receive by default and is the support tier the subscription price implies.

Customers cannot subscribe without support; there is no licence-only purchase under the post-acquisition catalogue. The pre-acquisition option of dropping SnS to reduce cost is not available; the equivalent decision under Broadcom is to not subscribe at all, or to migrate to an alternative platform.

The embedded support component is approximately 20-30% of the headline subscription price by Broadcom's internal accounting, though this composition is not disclosed to customers. The customer-facing view is a single subscription price covering licence and support together.

The support tiers

Beyond the included production support, Broadcom offers premium support tiers for customers requiring enhanced coverage. The tiers are not as numerous as the pre-acquisition VMware structure (which had Basic, Production, Production for Mission-Critical Apps, Business-Critical, and others) but are simpler.

Production Support (included)

Production Support is included in every subscription. It provides business-hour coverage with after-hours response for severity-1 cases. Response times for severity-1 are documented (typically 30-60 minutes); response times for lower-severity cases are slower (typically same-business-day for severity-2, next-business-day for severity-3). The named contact list typically allows three to six customer-designated technical contacts authorised to open cases.

Premium Support (uplift)

Premium Support is an uplift tier providing 24x7 coverage across all severity levels, faster response times across the severity matrix, named technical account manager (TAM) involvement, and an expanded named-contact list (typically 10-15 authorised contacts). Premium Support is priced as an uplift on the underlying subscription, typically in the 15-25% range above the subscription baseline.

Premium Plus Support (further uplift)

Premium Plus Support adds named technical account manager engagement with regular service reviews, proactive operations health checks, on-site engagement options, and prioritised escalation paths. The uplift over the subscription baseline is typically 30-45%, depending on the deal scope and customer-specific scope of the TAM engagement.

Mission-Critical Support (enterprise-only)

Mission-Critical Support is a bespoke tier offered to customers with the largest VMware deployments and the most demanding support requirements. The tier includes embedded TAM and engineering resources, severity-1 response measured in minutes rather than tens of minutes, and direct engineering escalation paths. The pricing is bespoke and negotiated as part of the strategic-account commercial; there is no published list price.

What the uplift actually buys

The premium-support uplifts buy specific things; understanding the specifics matters because the value of the uplift to a particular customer depends on the customer's actual support consumption pattern.

Coverage hours

The baseline Production Support coverage is business hours in the customer's primary region, with after-hours for severity-1 only. Premium Support extends after-hours coverage to all severities. Customers operating production VMware deployments outside of standard business hours (e.g., global operations, 24x7 trading platforms, retail back-office overnight processing) require the after-hours coverage; customers running production strictly during business hours often do not.

Response time

The premium tiers tighten the response-time SLAs across severity levels. For severity-1, the baseline 30-60-minute response moves to 15-30 minutes under premium. For severity-2, the baseline same-business-day response moves to 2-4 hours. Customers with operational incidents that genuinely benefit from the faster response (e.g., critical infrastructure with revenue exposure to downtime) extract more value from the uplift than customers whose incidents typically tolerate longer response windows.

Named-contact expansion

The baseline allows three to six designated technical contacts to open support cases. Premium Plus expands this to 10-15. Customers with large operations teams who need broader case-opening capability (e.g., 24x7 operations teams with multiple shifts) benefit from the expansion; customers with concentrated technical-support functions do not.

TAM engagement

The premium tiers include named technical account manager engagement. The TAM provides regular service reviews, proactive health checks, advice on product roadmap and adoption, and escalation paths within Broadcom's engineering organisation. The value depends on the scope of the TAM engagement (hours-per-quarter commitments) and the customer's ability to use the TAM time productively.

The negotiable surface on support

While the embedded support component of the subscription baseline is not separately negotiable, the support uplifts and several adjacent commercial elements are.

Premium-tier uplift percentage

The premium-tier uplift over the subscription baseline is negotiable, particularly in larger enterprise deals. The published uplift bands above are typical first-proposal levels; the negotiated levels for larger deals frequently sit 20-30% below the first-proposal level.

TAM scope and inclusion

The TAM engagement scope (hours-per-quarter, on-site days, joint planning cadence) is negotiable within the premium-plus structure. Customers should specify the scope they actually need rather than accepting the default scope, which is sometimes set to satisfy a customer profile that does not match the customer's actual operations.

Multi-product support consolidation

Customers with multiple Broadcom product entitlements (VMware plus Symantec plus CA Technologies) can frequently consolidate the support relationship into a single premium-support contract covering all the products, with associated discount on the consolidated commercial. The consolidation also typically improves the day-to-day support experience by reducing the number of distinct support relationships.

Multi-year support commitment

The premium support tier is committed for the contract term. Multi-year commitment to premium support sometimes attracts incremental discount on the premium uplift, though the standard discount machinery on the underlying subscription is the principal lever.

Geography-specific support arrangements

Customers operating in specific geographies (e.g., data sovereignty requirements requiring support delivered from a specific region, or language requirements requiring support delivered in a specific language) can sometimes negotiate geography-specific support arrangements as part of the premium tier without additional uplift, particularly if the requirement is well-defined and tied to a substantive deployment in the geography.

How the support experience has changed

Customer-reported support experience under Broadcom has shifted materially from the pre-acquisition VMware experience. The shifts are not uniformly negative but are uniformly real.

Response times generally hold

Reported response times against documented SLAs have generally held since acquisition close. Severity-1 cases consistently receive response within the documented windows; severity-2 and severity-3 cases occasionally slip, but the slippage is not dramatically different from the pre-acquisition pattern. The headline support-experience concern is not response time.

Senior engineer access has tightened

Access to senior engineering staff for complex cases has tightened. The pre-acquisition VMware practice of routing complex cases relatively quickly to senior engineering or to the product engineering team has shifted toward more triage at junior tiers before escalation. Customers reporting frustration with the support experience typically describe this dynamic rather than the response-time dynamic.

TAM relationships have changed

The TAM workforce has changed substantially since acquisition close, with significant turnover and reassignment. Customers with long-established TAM relationships have frequently found those relationships discontinued. New TAM assignments have varied in quality; the customer experience depends heavily on the specific TAM assigned.

Roadmap engagement has shifted

The pre-acquisition VMware practice of detailed roadmap engagement with enterprise customers has shifted toward more general communication and less detail on near-term product direction. Customers requiring detailed roadmap visibility (e.g., for internal architecture planning) have found this dynamic challenging.

What to do about it

The support changes are commercial-and-operational facts that customers need to plan around. Several specific responses work.

Validate the TAM scope before committing

If the customer is purchasing premium-plus support with TAM engagement, validate the TAM assignment, the TAM's scope, and the customer's expected use of the TAM time before committing the uplift. A TAM the customer cannot use productively is wasted cost.

Build internal expertise to reduce support dependency

Customers can reduce the operational impact of the support-experience shift by building stronger internal VMware expertise. The investment in training, certification, and operational tooling that reduces the volume of support cases produces better operational outcomes and reduces the dependency on the premium support tier.

Use third-party support for specific contexts

For workloads on perpetual entitlement that the customer is not converting to subscription (e.g., during a migration-to-alternative-platform transition), third-party support providers offer continuation support outside the Broadcom subscription. See our third-party support article for the detailed discussion.

Document support-experience expectations

Where premium support is purchased, document the expected service levels, the TAM scope, and the escalation paths explicitly in the commercial. The documented expectations support the renewal discussion if the experience does not match the commitment.

Support and the cost-modelling discipline

The customer's pricing calculator should include the support tier and the associated uplift as a parameterised input. The cost of premium versus baseline support across a multi-year term is non-trivial and should be modelled explicitly rather than included as a default assumption.

For a 1,000-core enterprise deployment at the mid of the VCF Advanced band with the standard discount stack, the baseline-included support corresponds to an effective annual cost of approximately $350K. A premium-support uplift at 20% adds approximately $70K annually, or $210K over three years. Premium-plus at 35% adds $122K annually, or $367K over three years. The cumulative impact of the support-tier decision is material enough to deserve explicit analysis.

Related reading

For deeper detail, see the Broadcom VMware pricing pillar, support tier details, third-party support alternatives, discount structures, our pricing calculator methodology, and support contract terms.