Broadcom CA Automic Licensing Guide

Automic Under Broadcom: What Changed

Automic was founded as UC4, an Austrian workload automation company that built a strong European enterprise customer base. CA Technologies acquired Automic in 2016 for $650 million, integrating it into CA's broader automation portfolio. Broadcom then acquired CA Technologies in 2018 for $18.9 billion, bringing Automic under the same ownership that now controls VMware, Symantec, and the legacy CA mainframe portfolio. See our Broadcom Knowledge Hub for the full acquisition context.

Under Broadcom's stewardship, three significant changes have affected Automic customers:

Bundling into "Value Plans."

Broadcom consolidated CA's granular product catalogue into bundled subscription packages. Automic products are frequently included in broader automation bundles alongside CA Workload Automation, CA Continuous Delivery, and other tools. Customers who need only Automic Workload Automation may find themselves paying for an entire automation suite they don't use.

Price increases at renewal.

Post-acquisition renewal proposals have delivered increases ranging from 40% to over 300% compared to the previous term. Broadcom's approach follows the same playbook applied across all acquired product lines: eliminate discount programmes, consolidate into higher-priced bundles, and use audit findings as leverage for renewal pricing. This pattern mirrors what VMware customers experienced.

Reduced product investment.

Broadcom operates an efficiency-driven model that reduces R&D spending on acquired products. Automic has seen reduced feature development velocity, longer support response times, and a smaller professional services organisation.

The Automic Product Portfolio

The Automic platform comprises three primary products, each with distinct licensing models and use cases.

Automic Workload Automation (AWA)

The flagship product: enterprise job scheduling, batch processing, cross-platform workflow orchestration, and event-driven automation. Supports Windows, Linux, UNIX, mainframe, SAP, Oracle, and cloud platforms. The direct competitor to Control-M (BMC), Tidal (Redwood), and IBM Workload Automation. Key capabilities: cross-platform job scheduling, dependency management, SLA monitoring and alerting, file transfer automation, SAP and Oracle integration.

Automic Service Orchestration

Infrastructure and cloud orchestration: automated provisioning, configuration management, and multi-cloud deployment workflows. Competes with Ansible, Terraform, and cloud-native orchestration tools. Key capabilities: infrastructure provisioning, cloud orchestration (AWS, Azure, GCP), configuration management, self-service portals.

Automic Release Automation (ARA)

Application release pipeline automation: deployment orchestration, environment management, and release governance. Competes with Jenkins, GitLab CI/CD, Azure DevOps, and Octopus Deploy. Key capabilities: release pipeline orchestration, environment provisioning, deployment verification, rollback automation.

Licensing Metrics Explained

Automic licensing uses multiple metrics depending on the product, the platform it runs on, and the contract structure. This metric complexity is the primary source of compliance risk and cost confusion.

Managed Endpoints (Agents)

The most common metric for distributed (non-mainframe) AWA deployments. A managed endpoint is any server, virtual machine, or container host where an Automic agent is installed to execute jobs. Each endpoint requires a licence regardless of the volume of jobs executed.

Server Tiers

Some Automic contracts use a tiered server classification where the licence cost varies by server size or type. Tier 1 (large servers with 16 or more cores) commands a higher per-server licence fee than Tier 2 or Tier 3. The tier classification can be subjective and is a frequent source of audit disputes.

MIPS (Millions of Instructions Per Second)

The licensing metric for mainframe deployments. If AWA schedules jobs on IBM z/OS mainframe systems, the mainframe component is licenced by the MIPS rating of the LPAR where the Automic agent runs.

MSU (Million Service Units)

An alternative mainframe metric used in some Broadcom contracts. MSUs correlate with MIPS but use IBM's service unit measurement.

Named Users

Used for Automic Release Automation and some Service Orchestration licences. A named user is an individual who accesses the Automic interface to define, execute, or monitor automation workflows.

Managed Nodes / Actions

Service Orchestration may be licenced by the number of infrastructure nodes managed or the number of orchestration actions executed per period.

Automic Workload Automation Licensing

Distributed Platform Licensing

On distributed platforms (Windows, Linux, UNIX), AWA is typically licenced per managed endpoint. The list price ranges from $1,500 to $5,000 per endpoint per year depending on the server tier classification, contract vintage, and bundle structure. Enterprise agreements with 500 or more endpoints typically negotiate to $800 to $2,500 per endpoint depending on discount depth.

The critical licensing distinction: an endpoint licence is required for every server where an Automic agent is installed, regardless of whether the agent is actively used. Agent sprawl is the single largest source of over-licensing in AWA deployments. Decommissioned servers with residual agents, test environments with agents installed "just in case," and disaster recovery hosts with standby agents all consume licence entitlements.

Mainframe Licensing

Mainframe AWA licensing is priced per MIPS or MSU of the LPARs where Automic mainframe agents operate. List pricing ranges from $2,000 to $6,000 per MIPS per year. On a 3,000-MIPS mainframe deployment, the annual AWA mainframe licence can exceed $6M to $18M at list — making it one of the most expensive line items in the Broadcom mainframe portfolio.

Every mainframe capacity upgrade increases your Automic licence obligation, even if the additional MIPS are consumed by other applications entirely.

SAP and Oracle Integration Licensing

AWA's SAP and Oracle integrations may require additional licensing beyond the base endpoint licences. Some contracts include SAP/Oracle integration as part of the base AWA licence; others treat them as separately licenced add-ons at $500 to $2,000 per SAP/Oracle instance.

Service Orchestration and Release Automation

Automic Service Orchestration licensing is typically based on managed nodes or orchestration actions. Pricing ranges from $50 to $200 per managed node per year. For infrastructure-heavy enterprises managing 2,000 or more nodes, the annual cost can reach $200K to $400K.

The competitive pressure on Service Orchestration is intense. Ansible (Red Hat), Terraform (HashiCorp), and cloud-native tools (AWS CloudFormation, Azure ARM) provide equivalent or superior orchestration capability at significantly lower cost.

Automic Release Automation (ARA) licensing is based on named users and managed applications. Pricing ranges from $500 to $2,000 per named user per year. ARA faces the strongest competitive pressure: Jenkins, GitLab CI/CD, Azure DevOps, and GitHub Actions provide release automation capabilities that have surpassed ARA in developer adoption.

Broadcom's Bundling Strategy — The Value Plan Trap

Broadcom sells its automation products through Enterprise Licence Agreements (ELAs) and Value Plans that bundle multiple products into a single subscription. While bundling can simplify procurement, Broadcom's bundles are designed to maximise revenue extraction rather than customer value.

Broadcom's "Value Plan" bundles Automic products with other CA automation tools you may not need: CA Workload Automation (legacy CA 7), CA Continuous Delivery Director, CA Service Virtualization, and others. The bundle price appears competitive compared to the sum of individual list prices — but if you only use Automic Workload Automation, you are paying a premium for a bundle whose incremental products deliver no value. Always calculate the cost of licensing only the products you use versus the bundle price.

Audit Risk Areas and Compliance Pitfalls

The most common Automic audit risk areas:

• Agent sprawl on decommissioned servers (endpoints licenced but inactive)
• Mainframe LPAR capacity increases that trigger automatic licence metric growth
• SAP/Oracle integration usage disputed as separately licenced vs included in base
• Server tier misclassification (Broadcom may reclassify Tier 2 servers as Tier 1)
• Named user counts exceeding licenced entitlements
• Unlicenced use of ARA in additional environments beyond the contracted scope

Cost Modelling — Three Enterprise Scenarios

Small Enterprise (100 endpoints, no mainframe)

Annual AWA cost approximately $120K to $250K depending on tier mix and discount. Total Automic suite if ARA and Service Orchestration are included: $200K to $400K.

Mid-Market (500 endpoints, 1,000 MSU mainframe)

AWA distributed: $400K to $1.2M. AWA mainframe: $2M to $6M. Total Automic exposure: $2.5M to $7.5M annually.

Large Enterprise (2,000 endpoints, 3,000 MSU mainframe)

AWA distributed: $1.6M to $5M. AWA mainframe: $6M to $18M. Total exposure: $8M to $23M annually.

Licence Optimisation — Reducing What You Pay For

Key optimisation levers:

• Audit and remove inactive agents on decommissioned servers (30 to 50% reduction common)
• Consolidate agents where multiple lightweight jobs can be relocated to fewer hosts
• Evaluate whether mainframe workloads can be re-platformed to distributed infrastructure
• Challenge tier classifications with documented server utilisation data
• Benchmark third-party alternatives (Control-M, Redwood Tidal) to create negotiation leverage
• Exit ARA in favour of Jenkins/GitLab CI/CD where release automation is primarily code-centric

Third-Party Alternatives and Exit Strategies

Workload Automation competitors

BMC Control-M, Redwood Tidal (formerly JAMS), IBM Workload Automation, Stonebranch UAG. All offer enterprise-grade capabilities with competitive pricing relative to post-Broadcom AWA renewal demands.

Service Orchestration competitors

Red Hat Ansible, HashiCorp Terraform, cloud-native tools (AWS CloudFormation, Azure Bicep/ARM). Open-source editions at zero licence cost.

Release Automation competitors

Jenkins, GitLab CI/CD, Azure DevOps, GitHub Actions, Octopus Deploy.

Negotiating Broadcom Automic Renewals

• Start 18 months before the contract expiry date
• Build documented migration plans for AWA (even if you don't execute them) to establish credible leverage
• Obtain competitive pricing from Control-M, Tidal, or Stonebranch before opening renewal discussions
• Resist the "Value Plan" bundle unless every included product has demonstrated use and value
• Negotiate annual uplift caps (3 to 5% is achievable for multi-year commitments)
• Challenge MIPS/MSU baseline if mainframe capacity has declined
• Negotiate extension clauses giving you 12 to 24 months at current pricing if negotiations stall

For independent advisory support on your Broadcom Automic renewal, contact our Broadcom advisory team or explore the Broadcom Knowledge Hub.

Third-Party Support for Automic

Third-party Automic support providers offer maintenance and support at 30 to 50% below Broadcom's pricing. These providers cover bug fixes, security patches, and operational support for the same Automic product versions you currently run. This is a viable strategy for organisations locked into Automic for the near term but unwilling to accept Broadcom's support pricing escalation.