CA Automic Licensing Broadcom

CA Automic Automation under Broadcom in 2026 is one of the most metric-heterogeneous licensing environments in enterprise software. The product was developed by Automic Software, acquired by CA Technologies in 2016, then acquired again by Broadcom in 2018. Each transaction layered new licensing metrics on top of an existing customer base, and many customers in 2026 are operating under metric structures that bear only loose resemblance to the metrics Broadcom prefers to enforce. This article sets out exactly how Automic is licensed under Broadcom in 2026, how customers should identify their controlling metric, and how to defend Automic audits and renewals.

The Automic licensing landscape in 2026

The most striking feature of Automic licensing is that there is no single "Automic metric." Different customers, with different contract vintages, are licensed under different controlling metrics. Some customers have multiple metrics in parallel (covering different agent populations, different geographic regions, or different deployment phases). The metric heterogeneity reflects three layered acquisitions: the original Automic Software contracts, the CA Technologies-era contracts (2016-2018), and the Broadcom-era contracts (2018-present).

The principal licensing metrics observed in 2026 customers:

Agent-based licensing

The legacy Automic Software model: per Automic agent installed on a managed system. Each managed server, mainframe partition, or other endpoint with an Automic agent requires a licence. Common in contracts originated under Automic standalone (pre-2016) and preserved through subsequent renewals.

Capacity-based licensing

Some Automic deployments are licensed by capacity — defined variously as total managed CPU, total managed memory, or total managed job-execution capacity. The capacity definition is critical and varies materially between contracts.

Job-volume licensing

Some Automic contracts are licensed by the number of jobs scheduled or executed in a given period. Common metrics include daily job count, monthly job count, or peak hourly job-execution rate. Job-volume licensing was particularly common in later CA Technologies-era Automic renewals.

Named-user licensing

Less common but observed in some Automic deployments — per named administrator, operator, or developer user.

Hybrid models

Many enterprise Automic deployments are licensed under hybrid metrics: a base licence covering a certain capacity, with additional licences for agent counts beyond a baseline, or with separate metrics for different functional areas (workload automation versus release automation versus service orchestration).

Identifying the controlling metric

The most important step in any Automic licensing review is identifying which metric actually controls the customer's licensing position. This is not always obvious; it requires careful contract review:

• Original contract: the initial Automic Software or CA Technologies contract that established the customer's licence position. The metric in this contract is the baseline.
• Amendments and true-ups: each subsequent amendment may have introduced new metrics, modified existing metrics, or added scope under new metrics.
• Renewals: each renewal could have migrated the customer to a new metric structure. Customers should specifically read each renewal contract for metric changes.
• Letter agreements and side letters: less common but sometimes important. Customers should locate and review all related correspondence.

The objective is to identify the specific metric language in the controlling contract, with citation to clause and section. This language is the basis of the customer's defence against any Broadcom audit or renewal claim that asserts a different metric.

The Broadcom metric-migration pattern

Broadcom has consistently sought to migrate Automic customers to its preferred metric structure: typically a capacity-based or hybrid metric that produces higher revenue than the customer's legacy structure. The migration usually happens at renewal, where Broadcom proposes a "modernised" licensing structure that simplifies the customer's metric portfolio while raising the cost.

Customers should be cautious about accepting metric migrations without explicit understanding of the financial impact. Common patterns:

• Agent count to capacity migration: a customer with 5,000 agents is migrated to a capacity metric. The new metric may produce equivalent or higher cost than the original 5,000-agent licence, depending on capacity definition.
• Capacity expansion at renewal: the capacity threshold in the existing metric is raised at renewal, with a corresponding price increase. The expansion may not match the customer's actual capacity growth.
• Hybrid simplification: a customer with multiple parallel licences is migrated to a single hybrid licence. The simplification has commercial value but the price often more than compensates.

Pricing trends

Automic per-unit pricing has increased materially since the Broadcom acquisition. The pattern depends on the controlling metric:

• Per-agent pricing: typically up 40-100% since 2019.
• Per-capacity-unit pricing: typically up 30-80%.
• Per-job pricing: typically up 20-60%, with the lower range for high-volume customers and the higher range for low-volume customers.
• Named-user pricing: typically up 30-50%.

The increases compound across multi-year renewal cycles. Customers who have renewed twice since the acquisition are typically running at 1.8x-2.5x their pre-acquisition annual cost for equivalent deployment.

The Automic audit risk

Automic audits are common under Broadcom and routinely produce material findings. The audit risk concentrates in three areas:

Metric ambiguity

The auditor will typically apply the metric that produces the highest claim, citing whichever contract text supports that metric. The customer's defence is to establish the controlling metric with specificity, with reference to the original contract. Customers who cannot identify their controlling metric definitively are at severe audit risk.

Agent count overcounting

The Automic console produces an agent inventory that includes installed-but-unused agents, decommissioned systems, and duplicates. Auditors often use the raw console count as the licence requirement. The defence is reconciliation against active-system records, with documented removal of stale entries.

Capacity definition

Where the controlling metric is capacity-based, the capacity definition is critical. The auditor will typically use the broadest reasonable definition; the customer should hold to the specific definition in the contract.

Job-volume measurement

For job-volume metrics, the auditor will typically measure peak periods rather than average. The customer's defence is to establish the contractually appropriate measurement window and to provide documented evidence of usage within that window.

Defending an Automic audit: the structured approach

The Automic audit defence playbook has five steps:

Step 1 — Establish the controlling metric

Identify the specific contractual metric, with citation. Document the metric's definition, scope, and any explicit exclusions. Where multiple metrics apply (e.g., to different deployment phases or different geographic regions), document each separately.

Step 2 — Document the deployment

Produce an authoritative measurement of the customer's deployment against the controlling metric. For agent-based licensing, this is the active-agent count reconciled against an authoritative source-of-truth. For capacity-based, the actual capacity consumed. For job-volume, the job execution count over the contractual measurement window. The documentation should be defensible against the auditor's methodology.

Step 3 — Reconcile to entitlements

Compare the documented deployment against the entitlement chain. Identify any apparent gaps and their probable causes. Many apparent gaps are explainable through proper interpretation of the metric or proper handling of historical contract events.

Step 4 — Challenge methodology

Where the auditor's methodology differs from the contractually appropriate methodology, document the difference and challenge formally. The challenge should include the contract citation, the methodology comparison, and the impact on the apparent finding.

Step 5 — Negotiate settlement

Most Automic audits settle. The settlement should reflect the documented deployment and the controlling metric, not the auditor's initial claim. Settlements at 35-55% of the initial claim are common; settlements at 25-40% are achievable with strong defence work.

Automic at renewal: the structured negotiation

Automic renewals under Broadcom are negotiable, but the negotiation requires the same metric clarity that the audit defence requires. Customers should approach renewal with:

• Documented current usage against the controlling metric.
• Documented growth trajectory projecting usage through the proposed contract term.
• Evaluated alternatives — the Automic displacement options (Control-M, Stonebranch, AutoSys, the open-source ecosystem).
• Clear renewal objectives — what term length, what metric structure, what pricing range constitutes an acceptable outcome.

Customers who negotiate without this preparation routinely accept Broadcom's first proposal at or near headline. Customers who negotiate with this preparation typically achieve 20-40% reductions from the initial proposal.

The Automic displacement question

Automic displacement is feasible but operationally intensive. The principal alternatives in 2026:

BMC Control-M

The leading enterprise workload automation alternative. Strong functional parity with Automic, particularly for batch processing and enterprise scheduling. Per-job pricing is generally competitive. The migration involves workflow translation, integration re-engineering, and operator retraining.

Stonebranch Universal Automation Center

A pure-play workload automation vendor with strong functional coverage and competitive pricing. Often selected for cost-sensitive migrations.

Broadcom AutoSys

The other CA-era workload automation product, now under Broadcom. Sometimes considered as a within-Broadcom migration but this rarely produces material savings (since the commercial parent is the same) and is functionally a more limited platform than Automic.

Open-source alternatives

Apache Airflow, Prefect, and other open-source workflow orchestration platforms have grown into credible enterprise options for some Automic use cases — particularly newer data-pipeline workloads. Less suitable for the deep enterprise scheduling and batch processing scenarios that traditional Automic deployments cover.

Automic displacement projects typically run 12-24 months end-to-end for large enterprises. The displacement business case must justify both the migration cost and the operational disruption; it does so frequently for customers facing material Automic renewal increases.

Common Automic licensing mistakes

1. Not identifying the controlling metric. Customers who cannot point to specific contractual metric language are vulnerable to whatever metric Broadcom asserts.
2. Accepting metric migration without analysis. Broadcom's preferred metrics produce higher revenue. Customers should price both the legacy metric and any proposed migration before accepting.
3. Trusting the console inventory. Automic console inventories overcount routinely. Reconciliation against active-system records is essential.
4. Late renewal preparation. The Automic renewal negotiation requires substantial preparation. Late starts produce poor outcomes.
5. Skipping the displacement evaluation. Even customers committed to renewing benefit from evaluating displacement; the alternative creates leverage and the documentation is reusable in subsequent cycles.

Building an Automic licensing baseline

Enterprises with material Automic deployments should maintain a structured baseline of licensing-relevant data:

• Current contractual metrics, with specific clause references.
• Current deployment measurements against each metric, refreshed quarterly.
• Historical deployment trends, sufficient to project forward through the next renewal cycle.
• Configuration documentation: which Automic features are deployed, on which systems, with what edition.
• Integration documentation: where Automic connects to enterprise systems and what the migration impact would be.
• Vendor alternative awareness: refreshed every 18-24 months.

The baseline supports both audit defence and renewal negotiation. The investment is modest — typically 0.5-1 FTE plus periodic external review — and the returns at audit or renewal time are consistently large.

Final word

Automic licensing under Broadcom is the most metric-heterogeneous environment in the CA Technologies portfolio. The complexity is the customer's enemy — it produces ambiguity that auditors and renewal negotiators exploit. The complexity is also the customer's opportunity: customers who establish their controlling metric definitively, and document their deployment against it, hold a defensible position even against aggressive audit findings. The work is unglamorous but rewarding: a few months of careful contract review and deployment documentation, refreshed annually, prevent claim values that routinely run into seven and eight figures. For enterprises with material Automic spend, this discipline is not optional.

Automic licensing — frequently asked questions

How do we identify our controlling Automic licensing metric?

Start with the original Automic Software or CA Technologies contract. Trace through every subsequent amendment, renewal, and side letter. The most-recent contract that addresses the metric explicitly is typically controlling; earlier contracts may be superseded but should be retained for reference. Where ambiguity exists, external legal review is appropriate.

Should we migrate to Broadcom's preferred metric at renewal?

Only after explicit pricing analysis. Price both the current metric (with realistic growth projections) and the proposed Broadcom metric across the proposed contract term. Migration is appropriate if the proposed metric produces lower cost for the customer's specific situation, which is sometimes but not always the case.

What is the typical Automic audit claim?

For a mid-size Automic deployment (1,000-5,000 agents or equivalent capacity), audit claims typically run $1M-$6M at notice. For larger deployments, $5M-$20M is common. Settlement values after structured defence typically run 25-50% of the initial claim.

Is Automic still being developed?

Yes. Broadcom continues to release new Automic versions with regular cadence. The investment level is lower than under Automic Software standalone, but the product is not in maintenance mode.

What is the most credible Automic alternative for displacement?

BMC Control-M is the most direct functional alternative for most enterprise Automic deployments. Stonebranch is the strongest cost-leadership alternative. Open-source alternatives are suitable for newer data-pipeline workloads but typically not for deep enterprise scheduling. The right choice depends on the customer's specific Automic use cases.