Broadcom Automic Workload Automation: Licence Model and Cost Analysis 2026

Automic's Journey: From UC4 to Broadcom

Automic Workload Automation has one of the longer acquisition chains in enterprise software. Originally developed as UC4 (Universal Control 4) by the Austrian company UC4 Software, the platform was acquired by CA Technologies in 2014 and rebranded as CA Automic. When Broadcom acquired CA Technologies in 2018 for $18.9 billion, Automic passed into the Broadcom portfolio alongside products like Clarity PPM, Spectrum, and Rally Software.

The product itself is a sophisticated workload automation platform — enabling enterprises to orchestrate batch jobs, file transfers, application workflows, cloud automation tasks, and cross-platform process chains from a centralised scheduling engine. Its primary enterprise competitors are BMC Control-M, IBM Workload Automation (IWA), Redwood RunMyJobs, ActiveBatch, and to an increasing extent, native orchestration capabilities in platforms like Terraform, Apache Airflow, and Azure Logic Apps.

For enterprises running large-scale automation estates — financial services firms processing overnight batch runs, retail organisations managing supply chain workflows, healthcare providers handling claim processing cycles — Automic is deeply embedded infrastructure. The switching cost is high, which is precisely the commercial dynamic that Broadcom leverages in licensing negotiations.

The Licensing Model Shift: From Agent-Based to Execution-Based

Historically, Automic was licensed on a combination of server-based and agent-based metrics. Customers paid for the number of connected systems (agents) regardless of how frequently jobs ran on those systems. This predictable model meant that an enterprise with 500 agent connections could budget accurately — the cost was fixed to infrastructure footprint, not automation activity volume.

Broadcom's post-acquisition commercial strategy restructured this toward execution-based pricing for many customers — where the licensing metric is the number of job executions (job runs) per unit time, typically measured monthly or annually. This model is explicitly designed to capture value from automation growth: as enterprises automate more processes and execute more jobs, Broadcom's revenue grows proportionally.

The Cost Exposure Problem

Execution-based pricing creates genuine and difficult-to-predict cost exposure for enterprises with growing automation programmes. A financial services organisation that begins automating additional reconciliation workflows, or a retailer expanding supply chain automation, may find their Automic costs increasing 30–50% annually under execution-based pricing — not because their infrastructure footprint grew, but simply because they automated more processes using the existing Automic deployment.

The challenge is that the commercial incentive for the enterprise (automate more, reduce manual cost) directly conflicts with the commercial incentive for Broadcom (more automation = more job runs = more licence revenue). Enterprises building multi-year automation roadmaps under execution-based pricing must model the cost growth trajectory carefully or risk finding automation programmes that were financially justified under old licensing terms are no longer cost-effective under new terms.

The practical mitigation is to negotiate annual job run allowances as a committed annual quantity — similar to cloud commit models — with overage pricing capped at a pre-agreed rate. This structure preserves predictability while allowing Broadcom to participate in automation growth above the committed threshold. Getting this structure requires understanding both your current run volumes and a credible forecast of future growth. The Broadcom enterprise agreements strategic sourcing guide covers run volume forecasting methodology in the context of Automic commercial negotiations.

Automic SaaS vs On-Premises: Commercial Comparison

Broadcom has been consistently pushing the Automic SaaS deployment model since 2021. The SaaS offering — hosted on Broadcom's cloud infrastructure — delivers feature parity with on-premises deployments while eliminating the infrastructure management burden. Broadcom's commercial argument for SaaS is lower total cost of ownership through elimination of server hardware, database licensing, and operational overhead associated with self-managing the Automic server infrastructure.

When SaaS Is the Right Commercial Choice

For enterprises where the IT organisation does not have dedicated resources for Automic infrastructure management, SaaS genuinely reduces operational overhead. The automatic update model also ensures customers remain on current software versions without managing upgrade cycles — a significant administrative burden for complex Automic on-premises deployments that may be running multiple major versions behind current.

Broadcom's SaaS pricing for Automic typically includes a base subscription covering platform access, support, and infrastructure, with the execution-based component on top. The commercial structure makes direct on-premises versus SaaS price comparison non-trivial — on-premises customers must add server infrastructure, DBA resources, and operational overhead to the licence cost to produce a true TCO comparison. Enterprises that have not conducted this analysis rigorously often underestimate the true on-premises cost.

The SaaS Data Residency and Compliance Consideration

For enterprises in regulated industries — financial services, healthcare, government — Automic SaaS raises data residency and compliance questions that on-premises deployments do not. Automic SaaS processes job metadata, execution logs, and workflow definitions in Broadcom's cloud infrastructure. While Broadcom provides data residency options for major geographies, the contractual framework for data processing, retention, and security under SaaS requires careful review by legal and compliance teams.

The contract provisions to require in any Automic SaaS agreement include: data residency specification (jurisdiction where data is processed and stored), data processing agreement (GDPR DPA or equivalent), security audit rights (right to request SOC 2 Type II reports and security questionnaire responses), and data portability on exit (the right to export all workflow definitions, job metadata, and execution history in a standard format on contract termination). The Broadcom compliance guide covers the contractual framework requirements for Broadcom cloud-hosted products.

Competitive Landscape and Negotiation Leverage

The workload automation market has several credible alternatives to Automic that enterprise buyers can use as genuine competitive alternatives in negotiation, rather than merely as threat options. Understanding the strengths and weaknesses of each is essential for constructing a credible evaluation.

BMC Control-M

Control-M is the most direct Automic alternative and is frequently perceived as the premium alternative for complex enterprise batch orchestration. Control-M's licensing model is also experiencing post-acquisition changes (BMC is owned by KKR), but its per-job or per-task pricing is generally better understood by enterprises than Automic's execution-based model. Control-M's broader cloud integration capabilities — native integrations with AWS, Azure, and GCP workflow services — make it a credible alternative for enterprises with hybrid automation environments. Enterprise deals above $1 million annually typically achieve 20–30% discount from BMC list pricing.

Redwood RunMyJobs

Redwood RunMyJobs has established itself as the cloud-native alternative to both Automic and Control-M, with pricing that many enterprises find more predictable and commercially transparent than either incumbent. Redwood's strength is in SAP integration — it is the preferred workload automation tool for many SAP S/4HANA environments — which creates a natural evaluation path for enterprises running SAP workloads alongside other automation requirements.

Redwood's commercial positioning as a challenger to Broadcom Automic is well-understood by Automic account teams. Presenting a credible Redwood RunMyJobs evaluation — including a proof-of-concept for a representative subset of your Automic workflows — creates the competitive tension that opens Broadcom's commercial flexibility. This approach is consistent with the broader negotiation strategy outlined in the Broadcom negotiation playbook: credible competitive evaluation, not performative threat.

Timing Your Automic Renewal

Broadcom's fiscal year ends October 31. Automic renewals that land in August through October create the commercial conditions where Broadcom account teams have the incentive and authority to offer meaningful concessions. Enterprises whose natural renewal dates fall outside this window should consider whether bringing forward a renewal — with a modest early termination of the current term — into the October fiscal year-end window is justified by the commercial improvement achievable.

The three priorities for any Automic renewal negotiation are: conversion from pure execution-based pricing to a committed annual allowance with capped overage rates; multi-year pricing stability through an annual escalator cap of 3–5%; and for on-premises customers, explicit right to migrate to SaaS at no additional cost uplift during the contract term. For SaaS customers, the equivalent provision is the right to repatriate data and workflows to on-premises or an alternative platform at contract expiry without additional charges.

The VCF licensing guide provides context on Broadcom's broader commercial strategy — understanding how Broadcom approaches licensing across its product portfolio helps enterprise buyers anticipate negotiation positions and prepare accordingly. Our Broadcom enterprise software advisors regularly support Automic contract negotiations and can advise on current benchmark pricing for comparable enterprise accounts.

Author

Fredrik Filipsson is Co-Founder of Redress Compliance with 20+ years of enterprise software licensing expertise across infrastructure, operations management, and automation software. Fredrik has advised on Automic/CA Automic contract negotiations across financial services, retail, and healthcare verticals, helping enterprises structure execution-based pricing commitments that support automation growth without unlimited cost exposure. Connect on LinkedIn.