CA Endevor: a dev tool priced on production capacity.

CA Endevor Software Change Manager is Broadcom (CA)'s source code and change management system for the mainframe, the controlled pipeline through which mainframe application source is versioned, built, promoted, and deployed across environments. For many large shops it is the system of record for everything that changes in the application estate, which makes it deeply embedded and hard to displace. That stickiness is exactly why its commercial terms deserve scrutiny: a product this entrenched is one a vendor can renew aggressively.

CA Endevor is licensed the way most of the Broadcom (CA) mainframe portfolio is: on capacity, typically the MSU rating of the machines or LPARs where the product is authorized, with older agreements still written in MIPS. It is a capacity entitlement carried under a multi year contract, not a metered monthly charge, so the figure you pay against is fixed to a capacity number rather than to how much source change management you actually do. Broadcom also offers Mainframe Consumption Licensing (MCL), a usage based subscription that bundles the portfolio under a committed baseline, as an alternative structure.

Directional, pattern level. Verify your own metric and authorized capacity against the contract schedules before modeling a renewal.

The dominant driver is authorized capacity, not usage. Because Endevor is priced to the MSU of the machines where it can run, a product used by a development group can carry a price built on the full production capacity of the estate. The second driver is the renewal mechanics commonly observed across Broadcom (CA) deals: per unit rate uplift and annual escalator clauses that raise cost independent of any change in your workload. The third is portfolio bundling, where Endevor sits inside a larger CA agreement whose total obscures what any single product, including Endevor, is really costing you.

Broadcom (CA) compliance exposure tends to sit in the gap between where a product is authorized and where it actually runs. Common traps we see at pattern level:

The price is built on capacity, so the levers are about right sizing the capacity and disciplining the renewal mechanics. The five that pay:

Endevor is deeply embedded as the system of record for source change, so displacement is a real program rather than a renewal threat. There are competing mainframe source change managers and modern Git based pipelines that bring mainframe source under distributed tooling, and some shops do migrate over time as part of a broader modernization. But the migration carries process, audit, and retraining risk, and a half credible switching threat tends to be priced as exactly that by the vendor. The more reliable lever for most estates is to rationalize the authorized capacity and discipline the renewal mechanics rather than to stake the negotiation on a displacement you are not actually ready to execute.