Broadcom CA Mainframe Software Pricing 2026What’s Changed

Broadcom’s CA Technologies mainframe software portfolio remains one of the most commercially aggressive licensing environments in enterprise IT. Since Broadcom acquired CA in 2018, the playbook has been consistent: simplify the product portfolio, shift from perpetual to subscription licensing, impose annual price increases, and leverage the extreme switching costs inherent in mainframe software to extract maximum value at renewal.

For CIOs and IT procurement leaders managing mainframe estates in 2026, the pricing dynamics require proactive management. This guide breaks down what has changed, how the three licensing models work, what the 2025–2026 pricing increases mean for budgets, and what negotiation strategies remain available when Broadcom controls software that is deeply embedded in your most critical systems.

The Broadcom Acquisition Playbook: CA, Symantec, VMware

Broadcom’s approach to acquired software portfolios follows a well-documented pattern. After acquiring CA Technologies in 2018 for $18.9 billion, Broadcom applied the same strategy it later used on Symantec (2019) and VMware (2023): reduce R&D spending to focus on core products, eliminate lower-margin product lines, consolidate licensing into simplified (and more expensive) bundles, shift customers from perpetual to subscription models, and enforce aggressive annual price escalation.

The pattern matters because it is predictive. Enterprises that saw what Broadcom did to CA pricing should not have been surprised when the same approach was applied to VMware. And enterprises currently under multi-year Broadcom mainframe agreements should expect that the next renewal will follow the same trajectory: higher prices, bundled products, reduced flexibility, and limited willingness to negotiate on commercial terms unless the customer demonstrates credible alternatives.

The Broadcom Mainframe Portfolio: Five Categories

Broadcom organises its mainframe software into five strategic categories, each containing products that originated from CA Technologies and subsequent acquisitions. Understanding the portfolio structure is essential for procurement, because Broadcom increasingly pushes customers toward portfolio-level deals rather than individual product licensing.

1. AIOps & Automation

Operational intelligence, monitoring, and workload automation products. Key products include SYSVIEW (mainframe performance monitoring), OPS/MVS (event management and automation), CA 7 Workload Automation (batch job scheduling), WatchTower (integrated observability platform using machine learning), and NetMaster (network management). These products compete primarily with BMC’s MainView/AMI Ops suite and IBM’s OMEGAMON family.

2. Cybersecurity & Compliance

Mainframe security and access control products. Key products include ACF2 and Top Secret (the two external security managers that compete with IBM’s RACF), Trusted Access Manager (privileged access management), Compliance Event Manager (security event monitoring), and the Mainframe Security Suite (zero-trust security capabilities). ACF2 and Top Secret are among the most deeply embedded Broadcom products in customer environments, with migration to RACF typically requiring 12–24+ months of dedicated effort.

3. Database & Data Management

Db2 tools and data management products. Key products include the Db2 Administration Suite, Db2 Performance Suite, Db2 Utilities Suite, Db2 Backup and Recovery, CA 1 Tape Management, Vantage Storage Management, and CA 1 Flexible Storage (hybrid cloud storage). These compete with IBM’s Db2 Tools family and BMC’s AMI Data suite.

4. DevX & DevOps

Application development and delivery products. Key products include Endevor (source control and change management — the dominant mainframe SCM), Code4z (VS Code extension for mainframe development), Test4z (mainframe testing), HostBridge (API enablement for CICS applications), and InterTest (debugging). Endevor, like ACF2/Top Secret, represents extreme lock-in — it manages the entire mainframe source code lifecycle and is exceptionally difficult to replace.

5. Foundational & Open Mainframe

Core infrastructure and open-source integration products. Key products include Chorus Software Manager (software deployment and maintenance), Common Services, and Zowe contributions (the open-source mainframe framework). These foundational components are often prerequisites for other Broadcom mainframe products and are typically included in portfolio-level agreements.

Annual Price Increase History: The Compounding Effect

Broadcom publishes annual worldwide pricing announcements for its mainframe software portfolio. These published increases apply to list prices and typically flow through to existing customers via contractual annual uplift clauses. The compounding effect over a multi-year contract is substantial.

The compounding effect is the hidden cost that many organisations underestimate. A 6% annual increase compounded over a 5-year contract period means your Year 5 pricing is 33.8% higher than Year 1. Over a 7-year period (common for mainframe software), the compounded increase reaches 50.4%. An organisation paying $5 million annually for Broadcom mainframe software at 6% compound uplift will pay $6.69 million in Year 5 and $7.52 million in Year 7 — an additional $2.52 million per year compared to the original baseline, with no additional products or capacity.

The Three Licensing Models: How Pricing Actually Works

Broadcom offers three primary licensing models for its mainframe software. Understanding which model you are on — and whether an alternative model would be more cost-effective — is the first step in any negotiation.

MCL sounds appealing—cloud-like consumption, unlimited dev/test, no R4HA spikes—but it is also Broadcom’s most effective lock-in mechanism. Once you are on MCL, there is no per-product pricing visibility, no ability to remove individual products to reduce costs, and no competitive leverage at the product level. Evaluate MCL carefully against your actual workload patterns before committing. For organisations with stable workloads and effective R4HA management, traditional sub-capacity licensing may remain more cost-effective and more flexible.

What Has Changed in 2025–2026

Aggressive Renewal Tactics at Scale

The most significant change is not the published annual increase (which has been 5–7% for several years) but the escalation in renewal demands when legacy contracts expire. Broadcom’s post-VMware-acquisition commercial posture has become more aggressive across all software divisions, including mainframe. Organisations whose multi-year mainframe agreements are expiring in 2025–2026 are reporting initial renewal demands that are 2–3× the expiring contract value. Broadcom’s negotiating position is strengthened by the extreme switching costs inherent in mainframe software: migrating from ACF2 to RACF, Endevor to another SCM, or CA 7 to BMC Control-M requires 12–36 months of project work, significant budget, and operational risk.

Forced Bundling Across Broadcom Portfolios

Broadcom increasingly demands that mainframe software renewals be bundled with VMware and/or Symantec products. The UnitedHealthcare complaint specifically alleged that Broadcom “demanded that any renewal of licenses and services with respect to the CA and VMware software be bundled with other add-on software and services that UHC does not want or need.” This cross-portfolio bundling tactic limits the customer’s ability to negotiate each product line independently and inflates the total deal size.

MCL as the Default Renewal Model

Broadcom is actively steering customers toward MCL at renewal, positioning it as the modernised, “cloud-like” licensing model. For customers on legacy per-product sub-capacity agreements, Broadcom may present MCL as the only renewal option or may make per-product renewal prohibitively expensive relative to MCL. While MCL has genuine advantages for certain workload profiles, the shift eliminates per-product cost transparency and makes it structurally more difficult to competitively evaluate or replace individual Broadcom products.

Mandatory SCRT Reporting and Compliance Enforcement

Broadcom requires monthly submission of IBM SCRT reports (specifically the N7 ISV section) for all mainframe environments running Broadcom software. Non-compliance with reporting requirements can trigger contractual penalties, including loss of MCL rollover benefits or conversion to full-capacity pricing. Broadcom’s enforcement of reporting compliance has intensified, with more systematic follow-up on late or missing SCRT submissions.

IBM z16/z17 Capacity Upgrades Create Automatic Price Increases

Mainframe software pricing is tied to machine capacity. Organisations upgrading from IBM z15 to z16 (or the forthcoming z17) typically see capacity increases that directly flow through to Broadcom software costs, even if workload volumes remain unchanged. A hardware upgrade that increases rated MSU capacity by 20% will increase Broadcom software costs by approximately 20% under capacity-based licensing, on top of the annual published price increase. Budget for both when planning hardware refreshes.

Budget Modelling: What Broadcom Mainframe Software Actually Costs

To illustrate the financial dynamics, consider an organisation with a mid-range mainframe estate: 2,000 MSU of production capacity, running a typical Broadcom portfolio of 15–20 CA products spanning security (ACF2), workload automation (CA 7), monitoring (SYSVIEW), Db2 tools, and source control (Endevor). At current market rates, this environment typically carries an annual Broadcom mainframe software cost of $3–6 million, depending on licensing model, negotiated discounts, and contract vintage.

Under a traditional sub-capacity agreement with a 6% annual uplift, the 5-year cost trajectory is stark. A $4 million Year 1 baseline becomes $4.24M in Year 2, $4.49M in Year 3, $4.76M in Year 4, and $5.05M in Year 5. The cumulative 5-year spend reaches $22.54 million — $2.54 million more than a flat-rate scenario. If the contract then expires and Broadcom’s renewal demand is 2× the original baseline (consistent with reported market behaviour), the Year 6 cost jumps to $8 million, creating an immediate budget shock that many organisations are unprepared for.

Under MCL, the economics differ. A 2,000 MSU production environment with an MCL baseline of approximately 1.2 million MSU hours annually (based on typical utilisation patterns) might carry a fixed annual fee of $4.5–5.5 million, covering the entire Broadcom stack including unlimited dev/test. The trade-off is clear: MCL provides budget predictability and eliminates R4HA spike risk, but the floor is higher than an optimised sub-capacity arrangement, and there is no mechanism to reduce cost by removing individual products.

The hardware upgrade multiplier compounds both models. An IBM z15 to z16 migration that increases rated capacity by 20% adds approximately 20% to the software cost base, turning a $4M annual spend into $4.8M before any contractual uplift is applied. When the hardware capacity increase and the annual price increase compound together, a single year can see a 27–28% cost increase (20% capacity + 6% price uplift + compounding). This is the scenario that catches finance teams by surprise and underscores the importance of modelling ISV software costs as part of every hardware refresh business case.

The Legal Landscape: Lawsuits and Precedents

The UnitedHealthcare lawsuit (filed April 2025 in Minnesota federal court) is the most significant legal challenge to Broadcom’s mainframe pricing practices, but it follows a pattern established by AT&T’s 2024 VMware lawsuit in New York. The AT&T case — which alleged substantially similar practices regarding VMware software — resulted in a confidential settlement after the court signalled its intent to issue a preliminary injunction blocking Broadcom from cutting off AT&T’s access. That outcome established an important practical precedent: courts are willing to intervene to prevent Broadcom from using software cutoff threats as a negotiation lever.

UHC’s complaint specifically alleges that Broadcom demanded “hundreds of millions of dollars more” for the same CA mainframe software, forced cross-portfolio bundling with VMware products, and threatened to terminate access at the contract renewal date. UHC seeks both injunctive relief (preventing the software cutoff) and monetary damages for breach of contract. The lawsuit is ongoing, and its outcome will have significant implications for how Broadcom approaches mainframe renewals with other large customers.

For CIOs, these legal developments provide both a reference point and a strategic tool. While litigation should always be a last resort, the existence of these lawsuits — and particularly the AT&T settlement outcome — establishes that Broadcom’s renewal tactics are not beyond legal challenge. Organisations should ensure their existing contracts contain clear renewal pricing protections, extension rights, and dispute resolution mechanisms. Review these provisions with legal counsel well before the renewal window opens.

Competitive Alternatives: Building Negotiation Leverage

Broadcom’s pricing power derives from switching costs. Reducing those switching costs — or at least creating the credible perception that switching is possible — is the most effective negotiation lever available.

The competitive landscape reveals a critical pattern: IBM’s RACF (included at no additional cost with z/OS) is the strongest competitive alternative for security, but migration from ACF2 or Top Secret to RACF is a major project. BMC’s Control-M is the strongest workload automation alternative and has the advantage of supporting hybrid (mainframe + distributed) scheduling. For Db2 tools, IBM’s own toolset is competitive and benefits from being the database vendor’s own product.

The most significant gap is in source control: Endevor has no direct like-for-like competitor on the mainframe, making it the single most locked-in product in the Broadcom portfolio. Organisations using Endevor have limited competitive leverage for that specific product — though Broadcom’s push toward portfolio-level MCL pricing means Endevor lock-in effectively locks in the entire stack.

Negotiation Strategies for 2026 Renewals

Start 18 Months Before Expiry

Broadcom’s negotiating leverage increases as you approach contract expiry. The UHC lawsuit illustrates what happens when negotiations run to the wire: Broadcom threatened to cut off access to mission-critical software, forcing the customer to seek emergency court intervention. Begin renewal planning at least 18 months before contract expiry, allowing time to assess alternatives, build migration plans, and negotiate from a position of strength rather than desperation.

Build Documented Migration Plans for Key Products

For each major product category, develop a documented, costed migration plan with timelines and resource requirements. A migration plan for ACF2/Top Secret to RACF, CA 7 to BMC Control-M, or SYSVIEW to IBM OMEGAMON does not need to be executed — it needs to be credible enough that Broadcom believes it could be executed. Include budget allocations, consulting partner quotes, and internal resource commitments. Present these plans during negotiations as evidence that you have alternatives, not as a threat.

Resist Cross-Portfolio Bundling

Broadcom’s attempt to bundle mainframe software with VMware and Symantec renewals should be firmly resisted. Insist on separate contracts, separate renewal dates, and separate negotiation tracks for each product line. Bundling benefits Broadcom by increasing the total deal size (which makes walking away harder) and obscuring per-product pricing. If Broadcom insists on bundling, demand transparent per-product pricing within the bundle and the contractual right to remove individual products at renewal.

Negotiate Annual Uplift Caps

Multi-year agreements should include contractual caps on annual price increases. Broadcom’s standard position is 5–7% annual uplift. Push for 0–3% — particularly if you are committing to a 3–5 year term. The longer the commitment, the lower the annual uplift should be. Include a clause that ties the uplift cap to a published index (such as CPI) if possible, to prevent Broadcom from increasing the cap unilaterally at the next renewal.

Evaluate MCL on the Numbers, Not the Narrative

If Broadcom proposes MCL, demand a detailed comparison against your current sub-capacity costs using 12 months of SCRT data. Model three scenarios: baseline consumption (current level), 10% growth, and 10% reduction. If MCL is more expensive in the reduction scenario (which it usually is, because the minimum commitment still applies), negotiate reduction rights — a contractual mechanism to reduce the MCL baseline if your workload decreases. Also negotiate the overage rate: this is often the most important number in an MCL deal, because it determines the cost of any consumption above baseline.

Negotiate Extension Clauses

Include a contractual right to extend the agreement for 3–6 months at prorated fees if renewal negotiations are ongoing at contract expiry. This prevents Broadcom from using the threat of software cutoff as a negotiation lever — the tactic alleged in the UHC lawsuit. An extension clause preserves your access to software and support while you continue negotiating or executing a migration.

Frequently Asked Questions