Broadcom CA Automic Licensing: Models, Costs, and Negotiation Strategies

What Is CA Automic and Why Licensing Matters

CA Automic Automation (rebranded Broadcom Automic Automation, formerly UC4) is an enterprise workload automation and orchestration platform used by large financial institutions, manufacturers, retailers, and public-sector organisations to manage hundreds of thousands of automated job executions daily. The product spans batch scheduling, file transfer, SAP automation, cloud workflow orchestration, and IT process automation — making it central infrastructure for many enterprises.

When Broadcom acquired CA Technologies in 2018, it inherited Automic and began a multi-year process of restructuring the product's commercial model to align with Broadcom's recurring revenue strategy. The changes are material: customers who negotiated their last renewal under the legacy CA framework are entering a fundamentally different commercial environment today.

The Three Deployment Models and Their Licensing Implications

Broadcom Automic is available in three deployment configurations, each with distinct licensing mechanics that directly affect total cost of ownership.

In one engagement, a global financial services firm faced a Broadcom CA Automic true-up claim of $1.4M following a post-acquisition licensing audit. Redress identified three over-counted agent deployments and negotiated the settlement to $380,000. The engagement fee was less than 4% of the exposure.

On-Premises (Traditional)

The on-premises deployment was historically licensed on an agent-based or host-based model, where customers paid per automation agent deployed, per operating system type, or per server. Legacy CA customers often accumulated large agent inventories over years of organic growth, making their licence position difficult to audit and their renewal position complex to assess.

Under Broadcom ownership, on-premises Automic is increasingly offered only on a subscription basis. Broadcom has in most cases discontinued perpetual licence sales for new Automic deployments, pushing customers onto annual subscription agreements. Customers who hold legacy perpetual entitlements can continue using them, but support agreements — now a critical cost lever — have been restructured, and support cost increases of 3 to 5 times the previous annual maintenance fee are common at renewal.

Automic SaaS

The Automic SaaS offering moves the platform to a Broadcom-hosted, managed environment. Critically, the SaaS licensing metric is job executions rather than agents or hosts. Customers are allocated a defined number of job executions per contract period, applicable across production and non-production environments unless contractually separated.

The job execution model creates a new cost exposure. Enterprises that run frequent small automation jobs — common in retail batch processing, financial reconciliation, and SAP workloads — can exceed their contracted execution volume without realising it. Overage charges apply at rates that are typically 25 to 40 percent above the base per-execution rate. Broadcom's monitoring tooling will flag consumption, but customers often discover they are in overage only when Broadcom raises it at renewal.

Automic Automation Kubernetes Edition (AAKE)

The Kubernetes Edition is a container-native deployment of Automic designed for organisations running Kubernetes infrastructure. Licensing for AAKE is negotiated separately and often requires specialist commercial engagement with Broadcom's enterprise sales team. Core and node counts are the primary sizing metrics, and minimum thresholds apply.

The Shift to Execution-Based Pricing: What It Means in Practice

The migration from agent-based to job-execution-based pricing is the single most commercially significant change in Automic's licensing history. It requires organisations to fundamentally rethink how they measure and manage their automation footprint.

Legacy Agent Model: Predictable but Inflexible

Under the legacy model, an organisation knew its Automic cost at the start of each year: it paid for the number of automation agents deployed, regardless of how heavily or lightly each agent was used. This created shelfware risk (paying for agents that ran few jobs) but delivered budget predictability.

The model also meant that increasing automation intensity — running more jobs through existing agents — had no incremental licence cost. High-volume automation was effectively free once the agent licences were in place, which made Automic attractive for organisations with large-scale batch processing requirements.

New Execution Model: Variable but Transparent

The job execution model aligns licence cost with actual automation usage. In principle this is fairer: low-usage customers pay less, high-usage customers pay more. In practice, the transition has caught many enterprise customers off guard for two reasons.

First, few organisations had historically tracked execution volumes at the granularity now required. When Broadcom's commercial team presents execution data at renewal, customers often lack independent baseline data to validate the numbers. Second, the per-execution price at the volumes most enterprises generate is frequently higher in total than the agent-based equivalent — particularly for organisations running millions of executions monthly, which is common in banking, insurance, and manufacturing.

Non-Production Environments

A critical cost trap in the SaaS execution model is the treatment of non-production environments. Unless specifically negotiated, Automic SaaS contracts apply the job execution metric across all environments including development, test, and disaster recovery. Enterprises running robust CI/CD pipelines or parallel test environments can consume 30 to 50 percent of their execution allocation in non-production before a single production workload runs. Negotiating separate execution pools for non-production, or explicit carve-outs, is essential.

Support Costs: The Hidden Multiplier

Broadcom's support pricing is one of the most significant and least discussed cost factors in any Automic renewal. Support cost increases of 3 to 5 times the previous annual maintenance fee are typical for customers transitioning to Broadcom's new support structures. This is consistent with Broadcom's approach across its entire enterprise software portfolio, including VMware, Symantec, and CA Mainframe.

Broadcom consolidates support into a single premium tier (often referred to as Priority Support or Platinum-equivalent), eliminating the tiered support structure that CA Technologies maintained. Customers who previously paid for standard maintenance at 17 to 20 percent of licence value find themselves presented with support rates that are 35 to 55 percent of subscription value — a structural increase that compounds annually.

In negotiations, support is one of the levers where independent advisory generates the highest return. Broadcom has flexibility on support rate structures that it will not reveal in standard commercial conversations.

Automic vs. Competitive Alternatives

Any robust Automic renewal strategy requires understanding competitive alternatives and using them as genuine leverage, not just as a negotiating posture.

The primary competitors in the enterprise workload automation space include BMC Control-M, IBM Workload Scheduler, Redwood RunMyJobs, and Digital.ai Agility (for DevOps automation). Each offers migration paths from Automic and has actively engaged Broadcom's customer base since the acquisition.

Redwood RunMyJobs has emerged as a particularly active Automic replacement in the mid-market, offering execution-based SaaS pricing at rates that are often 20 to 40 percent below Broadcom's equivalent offering. BMC Control-M has also won displacement deals, particularly in financial services where its mainframe integration story is strong.

Broadcom is aware of this competitive activity and responds to credible migration threats during negotiations. The key word is credible: Broadcom's commercial team will probe whether the organisation has conducted a genuine proof of concept, obtained competitive pricing, and assessed migration costs. A vague reference to alternatives achieves little; documented competitive engagement achieves substantially more.

Key Negotiation Strategies for Automic Renewals

Having advised on more than 60 Broadcom workload automation renewals, the following strategies consistently deliver the best commercial outcomes.

Establish Your Execution Baseline Independently

Before entering any commercial conversation with Broadcom, extract your own job execution data from Automic's internal reporting. Do this for the preceding 12 months, broken down by environment (production, non-production, DR) and by time period. This independent baseline allows you to challenge Broadcom's sizing assumptions and negotiate the contracted execution volume on your terms rather than theirs.

Separate Non-Production Explicitly

As discussed, non-production execution consumption can account for a significant portion of total execution volume. Negotiate a contractual separation of production and non-production execution pools, with the non-production pool priced at a meaningful discount (typically 50 to 70 percent of the production rate in well-negotiated agreements).

Negotiate Multi-Year with Exit Provisions

Broadcom offers its best unit pricing on three-year agreements. However, a multi-year commitment without meaningful exit provisions is commercially dangerous given the pace of change in the automation market. Negotiate price caps for years two and three, termination for convenience provisions (with penalties capped at no more than one year's remaining subscription value), and technology access provisions that allow you to extract your automation scripts and configuration in standard formats upon exit.

Bundle Adjacent Broadcom Products Strategically

If your organisation uses other Broadcom software — whether CA Mainframe tools, Symantec products, or VMware infrastructure — there is significant negotiating benefit in coordinating renewal timing and bundling into a portfolio discussion. Broadcom offers incrementally better pricing when a customer is committing to a larger portfolio spend. If this is not currently the case in your organisation, the advisory function and procurement team need to align on a cross-vendor strategy before entering individual product renewals.

Challenge the Support Rate Directly

Support pricing is not fixed. Enterprise customers with significant execution volumes have successfully negotiated support rates to 22 to 28 percent of subscription value — substantially below Broadcom's opening position. The negotiation requires independent benchmarks, a clear alternative (including self-support with third-party maintenance providers), and willingness to escalate to Broadcom's enterprise account leadership rather than concluding commercially at the sales team level.

Alternatives Worth Evaluating

Even if you intend to remain on Automic, running a genuine competitive evaluation delivers two concrete benefits: it provides benchmarking data for your negotiation, and it ensures your organisation understands the true migration cost and timeline before committing to a multi-year Broadcom agreement.

Redwood RunMyJobs and BMC Control-M are the strongest functional comparators for most Automic use cases. For organisations primarily using Automic for SAP automation, Redwood's native SAP integration is particularly compelling. For organisations with heavy mainframe workloads, BMC's Control-M with IBM Z integration may offer superior economics given its mainframe-native pricing model.

In the virtualisation space, the broader Broadcom ecosystem shift has also driven organisations to evaluate Nutanix and Azure VMware Solution as alternatives to VMware infrastructure — demonstrating that Broadcom's customer base is actively seeking alternatives across the portfolio, creating leverage across all Broadcom product lines at renewal.

What to Expect at Your Next Automic Renewal

Organisations approaching their first Automic renewal under Broadcom ownership should anticipate an opening proposal that is materially higher than their previous CA Technologies agreement. Price increases of 50 to 150 percent year-over-year on the total contract value are not uncommon, driven by the combination of the transition to subscription, support restructuring, and execution volume growth.

The renewal process itself will be more structured and less flexible than the legacy CA approach. Broadcom's commercial terms are more standardised, audit rights are broader, and auto-renewal provisions are more aggressive. Starting the renewal process 12 to 18 months before contract expiry is essential to maintain negotiating leverage.

With the right preparation — independent usage data, competitive benchmarks, cross-portfolio coordination, and experienced advisory support — enterprise customers regularly achieve 20 to 35 percent reductions against Broadcom's opening position on Automic renewals.