CA Automic licensing under Broadcom. What you count, and what the renewal costs.

CA Automic is licensed per node, which for most customers means per registered agent, or per successful job execution on Broadcom's newer subscription. The first Broadcom renewal usually costs far more than the CA contract did, and the savings come from counting and competition.

CA Automic Workload Automation is licensed by counting what the Automation Engine connects to: agents on servers, database connections, SAP systems, file transfer agents and mainframe LPARs. Broadcom has owned the product since it closed the CA Technologies acquisition in November 2018, and now sells it as Automic Automation.

Most CA Automic customers carried their contract through the Broadcom integration without reading the metric again. By the time the renewal arrived, the agent definition had tightened, volume limits were being enforced, and the uplift followed the pattern Broadcom set after buying Symantec and VMware.

Read this guide with the Broadcom knowledge hub, our Broadcom advisory practice, the VMware negotiation playbook, the Broadcom audit risk article and the Vendor Shield subscription. Product scope is described on the Broadcom Automic Automation product page.

How is CA Automic licensed under Broadcom?

On most existing contracts you pay per node, and for server workloads a node is an agent. The agent is the small component on each managed endpoint that executes the jobs. Every registered agent counts, whether it ran a job last quarter or not.

Broadcom's newer subscription, Automic Automation for Hybrid Cloud, drops the agent count and bills successful job executions instead. So the first thing to establish before any renewal is which metric your order form actually uses, and which version of Broadcom's product terms it references.

Which Automic editions and metrics are still in force?

Switching from CA terms to Broadcom terms removes the separate non production license type. If your test and quality assurance systems were licensed at a lower rate under CA, expect the renewal quote to price them at the production rate unless you negotiate otherwise.

How does Broadcom count each type of agent?

These counting rules come from the AI Edition product terms, which count OS agents one per agent, so three agents on one host are three nodes. CA era contracts license SAP by named user per Automation Engine system and client. Keep a copy of the product terms your order form cites, because that is the version you will argue from.

Why is the registered agent count usually too high?

Operations teams register agents on every host and leave them in place after the server is repurposed or retired. Broadcom counts every registered agent at audit time. The fix is a quarterly agent inventory and a documented decommission process.

The cost is easy to size. Say you hold 2,500 agents at $1.5M a year, which works out to $600 per agent. If 300 of them have not run a job in 90 days, removing them before renewal takes $180,000 a year off the base that every future uplift compounds on.

Does CA Automic have a Job per hour cap?

Broadcom's published product terms do not define an hourly cap. Volume is measured as distinct tasks per day on the CA era Task Edition, or successful job executions per month on the Hybrid Cloud subscription. If your order form sets a throughput tier, crossing its ceiling triggers a tier upgrade or a true up at the next renewal.

On the Hybrid Cloud subscription, a job execution is any job that ends in status 1900 (ENDED_OK) or 1904 (ENDED_ROLLBACKED). Failed jobs do not count. The license count is the highest monthly total, it covers production and non production alike, and Broadcom requires you to enable usage data collection so it can see that total.

Which events push the job count past your entitlement?

• Quarter end batch runs. A financial close window pushes volume well above a normal month.
• Year end reporting. Tax season and year end close routinely double the daily job count.
• Migration cutovers. A data migration or ERP cutover can saturate the count for a week, and if that week falls in one calendar month, it sets your license peak.
• Reruns after an outage. A scheduler restart that replays jobs adds every rerun that completes successfully. On the Task Edition, a task that runs several times in a day still counts once.
• Test cycles on shared instances. Non production workloads on the same instance count toward the total under current Broadcom terms.

Why should you size on the peak month instead of the average?

Capacity planning usually works from the steady state, while Broadcom measures the peak. That peak sits inside the financial close or a migration cutover. Model the busiest month you expect over the contract term, and plan large cutovers knowing which month will carry the extra volume.

What does a Broadcom renewal proposal for CA Automic look like?

Expect an opening uplift of 8 to 15 percent on the agent subscription, a push for a three year term and an attempt to attach other Broadcom products. It is the same approach Broadcom took after the Symantec and VMware acquisitions, which its financial and acquisition news tracks deal by deal.

Automic has changed owners twice. CA bought it in January 2017, and Broadcom's investor relations site records the November 2018 close of the CA deal. For Automic customers, the Broadcom proposal typically contains these elements.

• An uplift on the agent line. Single digit to low double digit percentages, presented as modest.
• A three year term. Broadcom prefers it and discounts the multi year commitment.
• Bundle attachment. CA Service Operations Insight, CA Workload Automation iDash or wider Broadcom Software Group bundles, often under a Portfolio License Agreement.
• A narrower agent definition. Changes between renewals that raise the count without any new deployment.
• True up at list. Excess agents and volume overages settle at the published list price.
• Co termination. Broadcom pulls every product you hold onto one renewal date.

What have we seen in Broadcom CA and Automic renewals in 2024 and 2025?

Across roughly 20 to 30 Broadcom software renewals we advised in 2024 and 2025, after the CA and VMware acquisitions, the renewal quote bore little relation to the prior CA contract. Our 2024 to 2025 file holds 25 of these renewals. Three patterns came up again and again.

• First renewal quotes under Broadcom ran 40 to 120 percent above the legacy CA price for the same entitlement.
• Bundling pushed buyers toward portfolio agreements that included modules they did not run.
• Support and maintenance terms tightened, and co termination was used to pull every product onto one renewal date.

In that file, the median first quote came in 80 percent above the CA price, and the median reduction we negotiated back from the quote was 35 percent. The uplift line on the agent subscription looked moderate in most of these deals; the bulk of the increase came from bundles, term changes and support conditions.

Apply both medians to one hypothetical contract. A $400,000 CA renewal is quoted at $720,000. Taking 35 percent off the quote lands at $468,000, still 17 percent above the old price. That is why we negotiate from the price you paid before, and treat the Broadcom quote as a starting document only.

Broadcom inherited a workload automation contract that most customers had stopped reading, and the first renewal forces every one of them to read it again.

What does CA Automic cost over five years?

In our illustrative model for a 2,500 agent deployment, a Broadcom proposal runs from $2.4M in year 1 to $3.0M in year 5. Most enterprise deployments we review run between 1,000 and 5,000 agents and between 50,000 and 200,000 job executions a month.

Where a contract prices both agents and a volume tier, the two multiply on the order, so both need sizing. The table splits each cost line so that the fastest growing items stay visible.

Where do five year cost models go wrong?

Finance teams often model the agent line at flat growth. In practice the bundle attach line grows fastest, at 12 to 20 percent a year unless you decline it. Put each line on its own row with its own growth assumption, and the total stops hiding where the increase comes from.

How much does a 3 percent uplift cap save?

Take the agent line from the model above and compare the proposal path with a capped path over the same five years.

Close to a million dollars over the term comes from a single clause, before any agent is removed or any bundle declined. Put the cap in the order form at signing, where it binds every year of the term.

How does this change between a small and a large Automic customer?

• A few hundred agents, mostly Windows and Linux. Bundle exposure is limited and a mid market replacement such as ActiveBatch can be live in 6 to 12 months. A credible exit plan is cheap to build, so use it.
• Thousands of agents with SAP systems and mainframe LPARs. Replacement takes 15 to 24 months and fewer vendors can bid. Start earlier, and put more weight on the uplift cap, the definition freeze and the volume measurement terms.

Which terms should you negotiate on a CA Automic renewal?

Six terms decide most of the outcome. Customers who work all six usually hold the renewal close to inflation, while customers who work none accept the Broadcom uplift.

1. Cap the annual uplift. Lock the agent subscription uplift at 3 percent or below at signing.
2. Decommission idle agents. Document the agent inventory and remove unused agents before the renewal.
3. Forecast the peak volume. Size the volume tier on the peak month before Broadcom offers you the unlimited tier.
4. Decline the bundle. Keep the renewal to agents and volume, and decline the Broadcom Software Group attach.
5. Bid the workload out. Run a parallel bid with Stonebranch, Redwood RunMyJobs, BMC Control-M or ActiveBatch.
6. Write in an off ramp. Negotiate a contractual exit path with a migration window you control.

What contract wording should you ask for?

• Uplift cap. A fixed maximum on every renewal year, so the proposal path in the table above cannot recur.
• Definition freeze. The agent and node definitions of the product terms in force at signing apply for the whole term, so a narrower definition cannot raise your count mid contract.
• Volume measurement. Agreed exclusions for one off migration and cutover volume, so a single month does not set the license level for three years.
• True up pricing. Additional agents and volume priced at your contracted discount instead of the published list price.
• Non production rate. A reduced rate for test and disaster recovery systems, since current Broadcom terms give none.
• Reduction and exit rights. The right to drop agents or modules at renewal without repricing the rest, plus support continuation during a migration.

What will the Broadcom account team say, and how should you answer?

Which alternatives compete with CA Automic in 2026?

Four vendors bid on the same workload at competitive pricing. The workload automation market matured between 2018 and 2026, and a replacement bid is now a realistic option for large Automic customers as well as small ones.

Two of the four belong to Redwood, so a bid that includes RunMyJobs and ActiveBatch is really one competitor. Pair one Redwood product with Stonebranch or Control-M. Robotic process automation tools come up in these discussions, but they automate screen work and are licensed per robot; our UiPath negotiation guide covers that side.

Why we would not sign a portfolio agreement for the headline discount

The usual advice on Broadcom renewals is to accept a portfolio agreement because consolidation simplifies vendor management and brings a large headline discount. We disagree. In most CA and Automic renewals we reviewed, the bundle carried products the buyer did not use, and the discount was measured against an inflated list instead of the price paid before.

Baseline the entitlement you consume, refuse to be priced on portfolio list, and renew only the modules in production. Broadcom's model rewards bundling because unused modules become next year's expansion pitch.

How long does it take to move off Automic?

Between 6 and 24 months, depending on how many agents, SAP systems and mainframe LPARs you run. Most of that time goes on converting job definitions, calendars and dependencies, then running both schedulers in parallel.

If the migration will outlast your renewal date, ask Broadcom for a one year extension on current terms. That keeps you out of a new three year commitment halfway through the migration.

How does Broadcom audit CA Automic, and how do you check first?

Broadcom inherited the audit clause in the CA master agreement and runs audits itself or through an independent third party. The audit reads the registered agent count and the peak job volume. On the Hybrid Cloud subscription, the usage data you are required to send means Broadcom already sees both numbers each month.

If your order form cites Broadcom's current end user terms, an audit comes with 30 days' written notice and any shortfall is bought at the then current list price. An underpayment of 10 percent or more also makes you pay Broadcom's reasonable audit costs. Older CA agreements may say something different, so read the clause your order form references.

Your defense is a quarterly internal inventory and a reading of the contract against what is deployed. These are the places to look.

• License overview in the system client. Shows licenses used per platform and category. An agent that cannot draw a free license will not start and logs a no valid license error, which tells you the pool is full.
• Agent license settings. The category in each agent's properties in client 0000 and the LICENCE_CLASS parameter in the agent's INI file show which license pool it draws from.
• Agents list in the Automic Web Interface. The Administration perspective lists every defined agent, so you can match it against hosts that still exist.
• Telemetry usage data. Active technology, application and mainframe nodes, plus monthly successful job executions. If company policy blocks automatic collection, Broadcom expects you to collect and submit it manually.
• Job statistics. Monthly counts of jobs ending in status 1900 or 1904, which is the figure an execution based license uses.
• Your contract file. Order forms, the product terms version they cite, and license keys from the Broadcom support and download portal.

A license key that allows an agent to start is not proof the agent is entitled, so reconcile the key against the order form. Our SAM guide for Broadcom software and Broadcom audit defense service cover the wider process.

What to do next

We run Broadcom engagements inside Vendor Shield, the Renewal Program, the Benchmark Program and the Software Spend Assessment, and Broadcom commercial work is led by the founders. See our benchmarking, about us and locations pages, or contact us directly. For any CA Automic renewal, start with these seven steps.

1. Inventory the agents. Pull the registered agent count by OS, database, SAP, file transfer and cloud category.
2. Decommission idle agents. Remove agents that have not run a job in the last 90 days.
3. Model the peak volume. Pull the busiest month from the financial close and year end windows, and note any planned migration.
4. Read the master agreement. Confirm the agent definition, the volume terms, the uplift clause and the audit clause.
5. Open the renewal 12 months out. Start your own process before the Broadcom proposal arrives.
6. Bid the workload out. Run a parallel bid with at least two alternatives from different vendors.
7. Bring in an independent advisor. Someone who models the cost, reads the contract and negotiates the renewal, with no Broadcom commission.

Frequently asked questions