VMware HCX, Tanzu, and Aria Under Broadcom: Licensing Costs and Negotiation Strategy

The Bundle Pricing Problem

Broadcom's fundamental commercial decision post-VMware acquisition was to eliminate standalone product purchasing and require customers to buy VMware Cloud Foundation (VCF) as the primary licensing vehicle. VCF bundles vSphere, vSAN, NSX, Aria Suite, Tanzu, and HCX into a single per-core subscription. Enterprises that previously purchased only vSphere and vSAN — the vast majority of the VMware installed base — now pay for NSX, Aria, Tanzu, and HCX whether those products are deployed or not.

The commercial consequence is predictable and documented across hundreds of enterprise VCF renewals. Organisations that were spending $800,000 annually on vSphere and vSAN licences are now being quoted $2.5–3.5 million for VCF subscriptions covering identical hardware footprints. The delta is largely attributable to three components: HCX, Tanzu, and Aria. Understanding what those products actually do — and which organisations have a genuine use case for each — is the starting point for any negotiation strategy focused on reducing that delta.

VMware HCX: What It Is and What You're Paying For

VMware HCX (Hybrid Cloud Extension) is a workload mobility platform designed to move virtual machines between on-premises VMware environments and cloud destinations — including VMware-based cloud providers and public cloud platforms — with minimal downtime. Its primary use cases are data centre migrations, disaster recovery, and multi-site workload balancing across hybrid cloud environments.

HCX operates at the network layer, extending Layer 2 networks across sites and enabling live workload migration without requiring re-IP. For enterprises actively executing data centre migrations or operating genuine hybrid cloud architectures across multiple VMware environments, HCX is a compelling capability. For enterprises running a single on-premises VMware environment with no active migration project, HCX has essentially no immediate value.

HCX Licensing Within VCF

Within VCF, HCX Advanced is included at no additional charge per-core. HCX Enterprise — which adds additional capabilities including bulk migrations and application dependency mapping — requires a separate subscription layered on top of the VCF entitlement. Broadcom prices HCX Enterprise as a consumption-based add-on, typically quoted per workload or per concurrent migration stream, though enterprise agreements can negotiate fixed annual fees for HCX Enterprise entitlements.

The negotiation angle for HCX: enterprises that can demonstrate they have no active migration programme and no planned hybrid cloud expansion within the initial contract term can argue for HCX to be excluded from the per-core cost calculation at contract execution, with rights to add HCX entitlements later at pre-agreed rates. Broadcom will resist this — their bundling rationale is explicitly to prevent disaggregation — but it has been achieved in large deals where the customer had credible migration alternative modelling.

VMware Tanzu: Kubernetes Platform Included in VCF

VMware Tanzu is Broadcom's Kubernetes platform, enabling enterprises to build, run, and manage containerised applications alongside traditional virtual machine workloads on vSphere infrastructure. Tanzu Basic, included within VCF, provides Kubernetes cluster provisioning on vSphere, basic container registry, and Tanzu Mission Control Essentials for multi-cluster governance.

Tanzu Advanced and Tanzu Enterprise — which add capabilities including Tanzu Application Platform (TAP) for developer experience workflows, full Tanzu Service Mesh, and advanced observability — are not included in VCF and require separate subscription licences. Broadcom prices these add-on tiers per cluster or per developer, depending on the specific product component.

Who Actually Deploys Tanzu Within VCF?

The reality of Tanzu adoption within the broader VCF installed base is instructive for negotiation. Most traditional enterprise IT organisations purchasing VCF to replace their existing vSphere infrastructure are not running Kubernetes workloads on the same hardware. Their application workloads are predominantly legacy VMs, not containerised applications. Their development teams either use public cloud-native Kubernetes services (EKS, AKS, GKE) or have separate dedicated Kubernetes infrastructure outside the VMware estate.

This creates a genuine commercial argument: if your organisation can document that Tanzu Basic on VCF is not deployed and has no roadmap for deployment within the contract term, you have the basis for arguing the Tanzu component should not contribute to the per-core pricing baseline. The VCF licensing guide includes a framework for conducting this component utilisation analysis and presenting it as a negotiation brief.

Broadcom's standard response is to offer "educational credits" for Tanzu — essentially training and onboarding services — rather than price concessions for non-use. The counter-position is that educational credits for a product you have no plan to deploy are not commercial value, and the negotiation should focus on pricing adjustments rather than service substitutions.

VMware Aria: The Operations Suite in VCF

VMware Aria (formerly vRealize Suite) is Broadcom's cloud management and operations portfolio, comprising Aria Operations (infrastructure monitoring and capacity management), Aria Operations for Networks (network visibility and troubleshooting), Aria Operations for Logs (log analytics), Aria Automation (infrastructure provisioning and policy), and Aria Cost (multi-cloud cost management).

Within VCF, Aria Operations and Aria Operations for Networks are included at the standard tier. Aria Automation and Aria Cost require additional subscription licences beyond the VCF entitlement, priced per managed object or per cloud account respectively.

Aria Value Versus Cost Reality

Unlike HCX and Tanzu, Aria has a clearer value proposition for the traditional VMware estate. Aria Operations replaces vCenter performance monitoring, capacity planning tools, and configuration management tooling that many enterprises were previously purchasing separately. For organisations that were paying for standalone vRealize Operations Manager licences pre-acquisition, the Aria inclusion in VCF represents genuine consolidation value.

The commercial risk with Aria is the upsell path. Aria Operations on its own — included in VCF — provides solid infrastructure visibility. But Broadcom's sales motion consistently pushes enterprises toward Aria Automation (previously vRealize Automation), which automates infrastructure provisioning via self-service catalogues and policy-driven governance. Aria Automation is a sophisticated product with genuine value for organisations that have mature DevOps and platform engineering practices. For the majority of enterprise IT shops, it represents significant implementation complexity and a multi-year deployment project, not a day-one capability addition.

The negotiation implication: when Broadcom quotes Aria Automation as part of an expanded VCF deal, the due diligence question is whether your organisation has the internal capability to deploy and operate it. Buying Aria Automation licences without the organisational readiness to deploy them is a classic SaaS shelfware scenario. For more on avoiding this, the Broadcom enterprise agreements strategic sourcing guide covers component-level utilisation analysis as a procurement practice.

VCF vs VVF: Choosing the Right Bundle

Broadcom offers two primary subscription bundles: VCF (VMware Cloud Foundation) and VVF (VMware vSphere Foundation). VVF is the lighter bundle — it includes vSphere, vSAN, and Aria Operations but excludes NSX, HCX, and Tanzu. For enterprises whose primary requirement is vSphere virtualisation with storage, VVF is frequently the more appropriate commercial choice at a meaningfully lower per-core price point.

The reason many enterprises end up in VCF rather than VVF is Broadcom's sales motion. Enterprise account teams default to quoting VCF because it generates higher revenue per transaction, and many procurement teams do not push back on the bundle upgrade because they are not aware that VVF is a legitimate and supported option. The Broadcom negotiation playbook includes a VCF versus VVF decision framework and the component analysis needed to make the right licensing choice for your environment.

Minimum core requirements are identical between VCF and VVF at 72 cores per CPU (updated from 16 cores per CPU as of April 2025). The per-core price differential between the two bundles is significant — VVF pricing is typically 35–45% below VCF at list. For enterprises without active NSX, HCX, or Tanzu deployment plans, the VVF calculation almost always produces a superior three-year TCO.

Negotiation Strategy for Bundle-Heavy VCF Deals

The core negotiation strategy for enterprises facing VCF quotes that include HCX, Tanzu, and Aria components they do not intend to use has three elements: documentation, alternatives, and timing.

Documentation means producing a written component utilisation assessment showing current and planned deployment of each VCF component. This document serves two purposes — it establishes the factual basis for a pricing discussion, and it demonstrates organisational seriousness to Broadcom's commercial team. Account teams who receive documented utilisation assessments treat the conversation differently from customers who simply ask for a lower price.

Alternatives means having a credible platform comparison ready, covering Nutanix AHV, Azure VMware Solution, and potentially Microsoft Hyper-V as the cost-competitive alternatives to VCF. The VMware alternatives 2026 comparison guide provides the TCO analysis framework. Broadcom responds to informed alternative cost models. They do not respond to unsubstantiated price objections.

Timing means entering the negotiation during Broadcom's fiscal year-end window (August–October) when account team incentives align with customer-friendly deal structures. Large VCF deals approved outside this window are less likely to receive the senior commercial approvals needed for bundle structure modifications or significant discounts on component-specific terms.

Our Broadcom VMware licensing advisory team regularly achieves VVF-equivalent pricing on VCF contracts for enterprises that engage with this three-element approach. The Broadcom audit risks guide explains why documenting your actual deployment also serves a compliance function — ensuring that if Broadcom ever queries your licence position, you have a contemporaneous record of intent and actual usage.

Author

Fredrik Filipsson is Co-Founder of Redress Compliance and a recognised authority on enterprise software licensing and contract negotiation. With 20+ years of experience across 500+ client engagements — including extensive work on Broadcom VMware VCF contracts since 2023 — Fredrik advises CIOs and procurement leaders on structuring infrastructure software agreements that align commercial spend with actual deployment plans. Connect on LinkedIn.