CA Technologies Licensing Broadcom Guide

CA Technologies licensing under Broadcom in 2026 is one of the most opaque, contractually complex, and commercially aggressive licensing environments in enterprise software. The CA Technologies portfolio — comprising mainframe software (Endevor, IDMS, Datacom, the IDMS suite), distributed enterprise software (Automic Automation, Clarity PPM, Service Virtualization, the API Management portfolio formerly Layer 7), agile management (Rally, now CA Agile Central), and the deep mainframe management and tools stack — was acquired by Broadcom in 2018. Since the acquisition, the licensing model has evolved through several phases, and the licensing intelligence the customer needs to defend renewals and audits has continually been raised. This pillar guide is the complete reference for CA Technologies licensing under Broadcom in 2026: how the metrics work, how the renewal model has evolved, how the audit programme is structured, and what enterprise customers should do to maintain a defensible position.

The CA Technologies portfolio in 2026

Six years after the acquisition, the CA Technologies portfolio under Broadcom is structured around five product families:

1. Mainframe software

The original CA Technologies anchor business: mainframe software products that run on IBM Z and zSeries systems. Endevor (change management), IDMS (database), Datacom (database), the broader CA mainframe utilities suite, the security stack (ACF2, Top Secret), and the operations management tools. The licensing metrics here are largely MIPS-based or MSU-based, derived from IBM's mainframe capacity model.

2. Automic Automation

The enterprise workload automation platform (formerly UC4, then Automic, acquired by CA in 2016 and now under Broadcom). Workflow scheduling, job orchestration, and enterprise automation. Licensed by various metrics depending on contract vintage: agent-based, capacity-based, job-volume-based, or hybrid.

3. Clarity PPM (Project and Portfolio Management)

The CA Clarity product (formerly CA PPM, formerly Niku) for enterprise project portfolio management, financial management, and resource planning. Licensed by named user, with separate metrics for full users, view-only users, and administrators.

4. Rally (CA Agile Central)

The agile project management platform acquired by CA in 2015. Licensed by user, with editions covering team, programme, and enterprise scope.

5. API Management and Service Virtualization

The Layer 7 API gateway and policy management products, plus the CA Service Virtualization product (formerly LISA). Licensed by API call volume, server instance, or named user depending on product and edition.

Each family has its own licensing metric, its own contract template heritage, and its own audit risk profile. The CA Technologies licensing complexity is materially higher than the VMware or Symantec portfolios because the metrics are non-uniform and because the contract heritage spans decades of CA acquisitions.

What changed at the acquisition and after

Broadcom's acquisition of CA Technologies completed in November 2018 for $18.9 billion. The acquisition was the first of Broadcom's enterprise software platform moves; the playbook later applied to Symantec and VMware was developed during the CA Technologies integration.

The CA Technologies licensing model has evolved in three phases since the acquisition:

Phase 1 (2019-2020): integration and rationalisation

The early Broadcom years focused on integrating CA Technologies into Broadcom's commercial systems, consolidating customer-facing teams, and rationalising the product portfolio. Several CA Technologies products were end-of-lifed (CA Mobile App Analytics, CA Continuous Delivery Director in certain editions, parts of the API Management portfolio). Pricing during this phase was largely stable; the disruption was on the operational side — account team changes, support quality issues, and integration friction.

Phase 2 (2020-2023): commercial repositioning

From late 2020 onward, Broadcom began implementing the commercial playbook on CA Technologies renewals. List-price increases of 30-100% became common. Multi-year commitments shifted from optional to expected. Support and maintenance pricing was repositioned upward. Discounting discretion was centralised.

Phase 3 (2023-present): mature commercial posture

Since 2023, the CA Technologies commercial model has stabilised into Broadcom's standard posture: high list pricing, narrow discount tiers, term-length and volume incentives, and aggressive enforcement of compliance. The customer experience in 2026 is materially different from the customer experience under CA Technologies stand-alone, but it has been consistent for the last two to three years and is broadly predictable.

The mainframe software licensing model

CA Technologies mainframe software is licensed by capacity, with the principal metric being MSU (Million Service Units) of IBM Z capacity authorised to run the CA software. The capacity metric is the standard IBM mainframe pricing unit and is well-defined in the IBM context, though its application to CA software involves several customer-affecting choices:

• Sub-capacity licensing. CA software can be licensed at the full LPAR capacity (where the customer pays for the maximum MSU the LPAR can use) or at sub-capacity (where the customer pays for the actual MSU used by the CA software). Sub-capacity is materially cheaper for customers whose CA software does not use the full LPAR capacity, but requires monthly reporting (typically via the IBM Sub-Capacity Reporting Tool or equivalent).
• Capacity events. Customers who add mainframe capacity must report it and true-up. Customers who reduce mainframe capacity sometimes have true-down rights, depending on contract terms; sometimes do not.
• DR and test capacity. Disaster recovery LPARs and test LPARs are often licensed at reduced rates, but the customer must specifically identify these in the contract; default assumption is full-rate.
• Edition and feature scope. CA mainframe products have editions (Endevor base, Endevor Plus, Endevor Workstation) with different feature sets and different prices.

Mainframe licensing audits are typically the highest-value CA Technologies audit category. Claim values frequently run $5M-$30M for a single audit. The audit defence requires deep mainframe capacity knowledge that most customer IT teams do not have in-house; external specialist support is usually essential.

Automic Automation licensing

Automic Automation has the most complex CA Technologies licensing history. The product was originally Automic Software, acquired by CA in 2016 with the existing Automic licensing metrics intact. CA migrated some customers to revised metrics; Broadcom has migrated additional customers since the acquisition. The result is that different Automic customers in 2026 are licensed under materially different metric structures:

• Agent-based licensing — per Automic agent installed on a managed system. Common in older contracts.
• Capacity-based licensing — per unit of managed capacity (defined variously by contract).
• Job-volume licensing — per scheduled job execution, sometimes with daily or monthly caps.
• Named-user licensing — per named administrator or operator user.
• Hybrid models — combining elements of the above, particularly in larger or more mature deployments.

The metric ambiguity means that Automic audits routinely produce findings that depend critically on which metric is in force for the specific customer. Customers who cannot identify their controlling Automic licensing metric are at severe disadvantage in audits; customers who have a clear contractual identification of their metric can usually defend the audit findings effectively.

Clarity PPM licensing

Clarity PPM is licensed by named user, with three principal user types:

• Full users — complete Clarity functionality, including project management, financial management, and reporting. Highest unit price.
• View-only users — restricted to read-only access. Lower price but the read-only restriction is enforced and audited.
• Administrators — full users with administrative scope. Sometimes counted as full users, sometimes priced separately.

Clarity audits commonly find that view-only licences are being used by users who actually have write access in the application, which Broadcom claims requires upgrade to full-user licences. The defence requires demonstrating the actual usage pattern, with reference to the Clarity permission model and the customer's role-based access design.

Rally (Agile Central) licensing

Rally is licensed by named user, with three edition tiers (Team, Programme, Enterprise) that have different feature scopes. The licensing audit risk on Rally is generally lower than other CA Technologies products because the metric is well-defined and the platform's user identity is clean. However, the renewal pricing is increasingly aggressive: per-user list prices have approximately doubled since the Broadcom acquisition, and discount discretion has narrowed considerably.

The Rally exit option has strengthened. Atlassian Jira (particularly with Advanced Roadmaps), Microsoft Azure DevOps Boards, and Linear have all become credible enterprise displacement targets. The displacement work is non-trivial — user training, workflow migration, integration re-engineering — but the multi-year cost differential frequently justifies the investment.

API Management and Service Virtualization

The Layer 7 API gateway products and the Service Virtualization (LISA) products are licensed under varied metrics: API call volume; server instance count; named user count; or hybrid combinations. The licensing complexity reflects the product evolution — Layer 7 acquired in 2013 has different contract history than newer Broadcom packaging.

These products are areas where customer exit is feasible. The API gateway market has multiple credible alternatives: Kong, Apigee (Google), AWS API Gateway, Microsoft Azure API Management, and Tyk. The Service Virtualization market also has alternatives, though the field is narrower (Parasoft, SmartBear). Renewal pricing on these products often produces the strongest displacement business cases.

The CA Technologies audit programme

Broadcom runs an active CA Technologies audit programme, with audits initiated on a calendar that customers should understand and prepare for. The audit-initiation patterns observable in 2026:

• Renewal-adjacent audits. Customers approaching renewal often receive audit notices 6-12 months before the renewal date. The audit findings then become the negotiating context for the renewal.
• Acquisition-driven audits. Both acquiring and acquired entities in M&A activity routinely receive audit notices in the 12-18 months following the transaction close.
• End-of-life audits. Customers running CA products that have reached end-of-support frequently receive audit notices, as Broadcom applies compliance scrutiny to environments approaching mandatory migration.
• Public displacement audits. Customers who publicly signal evaluation of CA alternatives sometimes receive audit notices within 6-12 months of the public signal.

Audit scope under typical CA contracts

CA Technologies audit clauses vary widely by contract vintage. Customers should identify the specific clause in force for each product family. Common elements:

• Notice period. Typically 30 days for CA-era contracts; 7-15 days in Broadcom-template renewals.
• Audit period. Typically 24-36 months of usage data.
• Auditor selection. Broadcom's preferred auditor (typically Deloitte, KPMG, or EY, with smaller firms used for some engagements) is standard but customers can sometimes negotiate alternative auditors.
• Customer cooperation. Reasonable cooperation is required; the definition of "reasonable" is contestable.
• Cost allocation. Findings over a percentage threshold (typically 5%) trigger customer responsibility for audit costs.

Defending a CA Technologies audit

The CA Technologies audit defence playbook applies the same general principles as Broadcom audits across the portfolio, with specific tactics for each product family.

Mainframe audit defence

Mainframe audit defence requires reconciliation between the customer's mainframe capacity records (LPAR definitions, IBM PR/SM reports, sub-capacity reporting data) and the CA software's actual usage of that capacity. Findings frequently rest on inflated capacity claims that the customer can challenge with proper records. The defence also requires careful attention to DR and test LPAR licensing — auditors often claim full-rate licensing for capacity that should be at reduced rate.

Automic audit defence

Automic audit defence centres on metric identification: which specific metric controls the customer's usage, what the metric's definition is, and what the customer's actual usage against that metric is. Audit findings often assume a metric that is more favourable to Broadcom than the customer's actual contract; the defence is to establish the contractual metric definitively.

Clarity audit defence

Clarity audit defence requires demonstrating the actual permission scope of each user. The audit will typically claim that any user with login access is a full user; the customer's defence is to show, through the application's role configuration, that some users are restricted in ways consistent with the view-only licence.

Rally audit defence

Rally audits are less common than other CA Technologies audits, but the defence focuses on user identification (whether claimed users are actually using the platform) and on edition feature usage (whether claimed features are actually deployed).

API Management and Service Virtualization audit defence

These audits often centre on usage volumes (API calls, server instances) that the customer must measure and document. The customer's monitoring systems are the basis of the defence; customers without their own monitoring data are dependent on Broadcom's data, which is often unfavourable.

The renewal model

CA Technologies renewals under Broadcom in 2026 follow the standard Broadcom playbook with product-specific variations:

Renewal pricing trends

List-price increases of 30-80% have been routine on CA Technologies renewals since 2022. Customers who renew with limited negotiation typically see actual increases of 20-50% over their prior contract; customers who negotiate aggressively typically see increases of 5-15% or, with credible alternatives, flat or reduced renewals.

Term-length pressure

Three-year commitments are standard; five-year commitments produce the deepest discount tiers but introduce significant commercial risk because the displacement options change over the term.

Bundle pressure

Broadcom typically offers consolidated CA Technologies "platform" deals that bundle multiple product families. The economics are mixed; customers should evaluate the bundle versus separate products carefully, and resist any bundle that includes products the customer is planning to displace.

Contract template changes

Each renewal moves the customer toward Broadcom's current contract template, which has materially less customer-favourable terms than the legacy CA Technologies templates. Customers should expect and negotiate against:

• Broader audit clauses (shorter notice, broader information requests).
• Statutory damages provisions on licensing breaches.
• Removal of true-down rights.
• Restriction of transfer rights in M&A scenarios.
• Expanded indemnity obligations on the customer.

The displacement question

Displacement is feasible for most CA Technologies products in 2026, though the economics vary significantly by product family:

• Rally — strong displacement options (Jira, Azure DevOps, Linear). Migration is operationally intensive but well-precedented.
• Clarity PPM — displacement options exist (Smartsheet, Planview, Microsoft Project for the Web, Workfront) but the platform is deeply integrated in many enterprises and displacement is multi-year.
• Automic — displacement options exist (Control-M, Stonebranch, AutoSys, the open-source ecosystem) but the workflow re-engineering is intensive and the migration timeline routinely runs 12-24 months.
• API Management — strong displacement options (Kong, Apigee, AWS, Azure, Tyk). Migration is technically demanding but well-bounded.
• Service Virtualization — some displacement options (Parasoft, SmartBear) but the field is narrower.
• Mainframe software — displacement is feasible (BMC, IBM, Rocket Software, and open-source mainframe products) but enormously complex. Mainframe displacement projects routinely run 3-5 years and cost tens of millions in transition.

The decision to displace or renew should be made product-by-product, not at the portfolio level. Each product's economics and operational situation differ, and a portfolio-wide displacement decision is rarely the right answer.

Building a defensible CA Technologies licensing position

Enterprises with material CA Technologies spend should maintain ongoing controls to defend renewals and audits:

• Entitlement reconciliation: documented chain of CA Technologies entitlements, including original contracts, amendments, true-ups, and renewals. Updated annually.
• Usage documentation: ongoing measurement of actual usage against each contract metric, with documented methodology.
• Configuration documentation: documented edition and feature deployments, with explicit reconciliation against entitlements.
• Renewal calendar: identified renewal dates for each contract, with internal preparation milestones leading up to each.
• Alternative-vendor evaluation: maintained awareness of credible displacement options, with formal evaluations refreshed every 18-24 months.
• External advisory relationship: established relationship with an independent licensing advisor who can be engaged rapidly when audit notices arrive.

The total cost of these controls for a mid-size enterprise with material CA Technologies spend is typically $300,000-$700,000 annually. The savings produced against audit claims and renewal pricing routinely run 5-15x this investment.

Common CA Technologies licensing mistakes

Five mistakes are seen routinely across enterprises:

1. Treating CA Technologies as a single licensing area. The portfolio's metric heterogeneity requires product-by-product attention; one-size-fits-all approaches produce poor outcomes.
2. Underestimating mainframe licensing complexity. Mainframe customers without specialised licensing expertise routinely overspend by 20-40% on CA mainframe licences.
3. Failing to identify Automic's controlling metric. Customers who cannot point to a specific contractual metric for their Automic deployment are exposed to whatever metric Broadcom asserts at audit.
4. Accepting renewal at headline. Broadcom's first renewal proposal is rarely the final proposal. Customers who accept without negotiation routinely overpay by 20-40%.
5. Late displacement planning. Customers who decide to displace within the renewal window typically end up renewing for one more cycle. Displacement planning must start 18-24 months before the renewal date.

The board-level view

For enterprises where CA Technologies represents a material annual spend ($5M+), the topic merits board-level awareness. The board should understand: the total annual CA Technologies spend, the renewal-cycle trajectory, the major audit risks, the displacement options under consideration, and the controls in place to manage the relationship. Annual board-level reporting on the CA Technologies relationship is appropriate; quarterly reporting is appropriate for customers with very large CA Technologies footprints.

The board's role is not to manage the licensing detail but to ensure that the licensing strategy reflects the enterprise's strategic objectives. Customers who treat CA Technologies as a routine IT spend often underinvest in licensing discipline; customers who treat it as a strategic vendor relationship typically achieve materially better outcomes.

Final word

CA Technologies licensing under Broadcom in 2026 is structurally more expensive and more contentious than it was under CA Technologies stand-alone. The structural changes are real and durable. The customer outcomes, however, remain highly variable: customers who maintain ongoing discipline produce defensible audit positions and reasonable renewal outcomes; customers who do not, do not. The difference between the two postures is the willingness to invest the modest annual cost of licensing discipline. For enterprises with material CA Technologies spend, that investment is the most reliable lever available. The audits are real; the renewal increases are real; the displacement options are real. None of these is fatal. They are managed problems.

CA Technologies licensing — frequently asked questions

How is CA Technologies licensing different from VMware licensing under Broadcom?

CA Technologies licensing is metric-heterogeneous: different products use different metrics, and individual customers often have different metrics for the same product depending on contract vintage. VMware licensing under Broadcom has consolidated around the VCF per-core metric. The CA Technologies environment requires product-by-product analysis; the VMware environment can often be analysed at the portfolio level.

What is the typical audit claim for a CA mainframe customer?

For a customer with material CA mainframe spend (50,000+ MSU across the CA portfolio), audit claims routinely run $10M-$30M at notice. The settlement value after structured defence typically runs 30-60% of the claim — the gap reflects the methodology and capacity-reconciliation work applied during the response.

Is Automic still being actively developed?

Yes, Automic remains an actively developed product under Broadcom, with regular release cadence. The investment level is lower than under Automic standalone or under CA Technologies, but the product is not in maintenance mode.

What happens to legacy CA Technologies contracts at renewal?

Legacy contract terms are typically replaced by Broadcom's current template at renewal. Customers who renew without negotiation see a wholesale terms change. Customers who negotiate can sometimes preserve specific legacy provisions (true-down rights, audit-clause limits, transfer rights) but the default is a full template change.

Should we plan to displace all CA Technologies products?

No. Each product should be evaluated on its own merits. Some products (Rally, API Management) have strong displacement cases. Others (CA mainframe security, specific Automic workflows) have weak displacement cases. A portfolio-wide displacement strategy is rarely the right answer; a product-by-product evaluation is.

Can we negotiate the audit clause out of CA Technologies contracts?

Not entirely. The audit clause is a core Broadcom contractual position. However, specific provisions within the clause are negotiable: the notice period, the scope of data requested, the auditor identity, the cost-allocation thresholds, and the timing constraints. Customers who negotiate these specifics produce materially better positions than customers who accept the default template.