Broadcom CA Automic
Licensing Guide

1. 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.

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 (the legacy CA 7/CA Scheduler product), 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 on 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. The pattern mirrors what VMware customers experienced and what we document in our Broadcom Knowledge Hub.

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 (as reported by our clients), and a smaller professional services organisation. Enterprises that rely on Automic for mission-critical batch processing should evaluate whether the current support and development trajectory meets their operational requirements over a 3–5 year horizon.

2. The Automic Product Portfolio

The Automic platform comprises three primary products, each with distinct licensing models and use cases. Understanding the portfolio structure is essential for accurate licence management and cost optimisation.

3. 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. Understanding each metric is essential for accurate licence management.

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. If you have 500 servers with Automic agents, you need 500 endpoint licences — even if 200 of those servers only run one scheduled job per day.

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+ cores or enterprise database hosts) commands a higher per-server licence fee than Tier 2 (standard application servers) or Tier 3 (small servers or development systems). The tier classification can be subjective and is a frequent source of audit disputes — Broadcom may classify a server as Tier 1 based on its hardware specification even if the Automic workload running on it is minimal.

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 (Logical Partition) where the Automic agent runs. MIPS-based licensing is expensive and directly tied to mainframe capacity — any LPAR capacity increase automatically increases your Automic licence obligation.

MSU (Million Service Units). An alternative mainframe metric used in some Broadcom contracts. MSUs correlate with MIPS but use IBM’s service unit measurement. The conversion between MIPS and MSUs varies by processor model. Ensure your contract specifies which metric applies and how capacity is measured.

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. Named user counts are straightforward but often over-provisioned — enterprises licence users who accessed the system once during implementation but never returned.

Managed Nodes / Actions. Service Orchestration may be licenced by the number of infrastructure nodes managed or the number of orchestration actions executed per period. Action-based metrics create consumption-variable costs similar to cloud pricing models and require careful monitoring to avoid overage charges.

4. Automic Workload Automation Licensing

AWA is the primary cost driver in most Automic deployments. Its licensing structure has several nuances that directly affect commercial exposure.

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+ endpoints typically negotiate to $800–$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. This means decommissioned servers with residual agents, test environments with agents installed “just in case,” and disaster recovery hosts with standby agents all consume licence entitlements. Agent sprawl is the single largest source of over-licensing in AWA deployments.

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–$18M at list — making it one of the most expensive line items in the Broadcom mainframe portfolio.

Mainframe MIPS licensing creates an insidious cost escalation mechanism: every mainframe capacity upgrade increases your Automic licence obligation, even if the additional MIPS are consumed by other applications entirely. If your z/OS installation grows from 3,000 to 4,000 MIPS to support SAP HANA workloads, your Automic licence cost increases by 33% despite Automic’s workload remaining unchanged. This is the same dynamic that affects all Broadcom mainframe products and is a priority area for our Broadcom Advisory practice.

SAP and Oracle Integration Licensing

AWA’s SAP and Oracle integrations — which allow Automic to schedule and monitor jobs within SAP systems and Oracle databases — 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–$2,000 per SAP/Oracle instance. Review your contract to determine whether integration capabilities are included or separately metered. This is a common audit finding — Broadcom may claim that SAP integration usage exceeds your licenced entitlement even if you believed it was included in your base agreement.

5. Service Orchestration and Release Automation

Automic Service Orchestration licensing is typically based on managed nodes (infrastructure endpoints being orchestrated) or orchestration actions (the number of provisioning, configuration, or deployment operations executed). Pricing ranges from $50–$200 per managed node per year or $0.10–$0.50 per action depending on the contract structure. For infrastructure-heavy enterprises managing 2,000+ nodes, the annual cost can reach $200K–$400K.

The competitive pressure on Service Orchestration is intense. Ansible (Red Hat), Terraform (HashiCorp), and cloud-native tools (AWS CloudFormation, Azure ARM/Bicep) provide equivalent or superior orchestration capability at significantly lower cost — in some cases, at zero licensing cost for open-source editions. Before renewing Service Orchestration, evaluate whether these alternatives can replace Automic’s orchestration functionality for your specific use cases.

Automic Release Automation (ARA) licensing is based on named users and/or managed applications (the number of application stacks under release management). Pricing ranges from $500–$2,000 per named user per year or $5,000–$15,000 per managed application per year. ARA faces the strongest competitive pressure of any Automic product: Jenkins (free), GitLab CI/CD, Azure DevOps, and GitHub Actions provide release automation capabilities that have surpassed ARA in developer adoption and ecosystem integration. For organisations evaluating their Broadcom Automic spend, ARA is typically the first candidate for replacement.

6. 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.

How to identify the trap: Request a line-item breakdown of your Value Plan showing the allocated licence value for each product. Compare the Automic-only allocation against standalone Automic pricing (request a standalone quote in parallel). If the standalone price is lower, the bundle is adding cost rather than value. If Broadcom refuses to provide a standalone quote — which is common — this itself is a signal that the bundle economics favour Broadcom, not you.

Counter-strategy: Negotiate the bundle down to only the products you use, or negotiate standalone Automic pricing by threatening to move Release Automation and Service Orchestration to open-source alternatives (which is commercially credible because the alternatives are genuinely competitive). See our Broadcom Knowledge Hub for the broader bundling counter-strategy across all Broadcom product lines.

7. Audit Risk Areas and Compliance Pitfalls

Broadcom’s audit activity has increased substantially since acquiring CA Technologies. Automic deployments carry specific compliance risks that differ from other software platforms.

Pre-audit preparation: Before Broadcom initiates a formal audit (or in advance of a renewal where audit findings may be used as pricing leverage), conduct an internal compliance review. Inventory every server with an Automic agent installed. Verify MIPS/MSU ratings against licenced capacity. Document non-production usage against contract provisions. Remove agents from decommissioned and inactive servers. This preparation reduces audit exposure and strengthens your negotiating position. Our Broadcom Advisory practice includes audit preparation and defence as a standard engagement component.

8. Cost Modelling: Three Enterprise Scenarios

9. Licence Optimisation: Reducing What You Pay For

Automic licence optimisation follows a five-step methodology that typically delivers 30–50% cost reduction without any change to operational capability.

Step 1: Agent rationalisation. Audit every server with an installed Automic agent. Remove agents from decommissioned servers, inactive test environments, and servers where scheduled jobs have been migrated to other platforms. In our advisory experience, 15–25% of Automic agents are removable without any operational impact. Each removed agent directly reduces your endpoint licence count.

Step 2: Mainframe sub-capacity optimisation. If your Automic mainframe agents run in dedicated LPARs with defined capacity, ensure your licence is based on the LPAR capacity, not the full CPC (Central Processor Complex) capacity. Broadcom’s default licensing may apply the full machine MIPS rating rather than the sub-capacity LPAR rating, inflating the licence by 2–5x. Verify the contractual basis and push for sub-capacity licensing if it is not already in place.

Step 3: Replace non-core products. Evaluate whether Automic Service Orchestration and Release Automation can be replaced with lower-cost or open-source alternatives. Ansible (free/Red Hat subscription) replaces Service Orchestration for most infrastructure automation use cases. Jenkins or GitLab CI/CD replaces Release Automation for most deployment pipelines. Replacing these two products can eliminate $200K–$1M annually from the Automic licence while improving capability through more widely supported, actively developed tools.

Step 4: Tier reclassification. If your contract uses server tier pricing, challenge the tier classification of every server. Servers classified as Tier 1 based on hardware specification but running minimal Automic workloads may be reclassifiable as Tier 2 or Tier 3 at lower per-server rates. The tier definition in your contract should specify the classification criteria — if it is ambiguous, negotiate explicit definitions that favour lower classifications for low-utilisation servers.

Step 5: Consolidate Automic automation engine instances. Enterprises with multiple Automic automation engine (AE) instances across environments or regions may be able to consolidate to fewer instances, reducing infrastructure costs and simplifying licence management. Consolidation also reduces the number of agents by eliminating redundant deployments where multiple AE instances manage overlapping server populations.

10. Third-Party Alternatives and Exit Strategies

Enterprises facing Broadcom’s Automic price increases have three categories of alternatives, each with different cost profiles and migration complexity.

Direct competitors (enterprise schedulers): BMC Control-M is the most established alternative, offering functionally equivalent cross-platform job scheduling with a mature mainframe integration. Redwood RunMyJobs provides cloud-native scheduling that competes directly with AWA for SAP workloads. Stonebranch Universal Automation Center offers a cost-effective alternative for enterprises without complex mainframe requirements. Each of these products requires migration of job definitions, dependencies, and workflows — a non-trivial undertaking for environments with 10,000+ job definitions. Budget 6–18 months and $500K–$2M for a full AWA replacement migration depending on scale and complexity.

Open-source and cloud-native alternatives: Apache Airflow, Prefect, and Dagster provide workflow orchestration capabilities that overlap with AWA’s distributed scheduling. These tools are particularly strong for data pipeline orchestration and cloud-native workloads but lack AWA’s mainframe scheduling depth and SAP integration breadth. They are best positioned as replacements for specific workload categories (data engineering, cloud automation) rather than complete AWA replacements. Partial migration savings: $100K–$500K/year by moving cloud and data workloads to open-source schedulers while retaining AWA for mainframe and SAP.

Third-party support (see Section 12): Continue running the current Automic version with third-party support from Rimini Street or Spinnaker Support at 50–60% less than Broadcom’s support fees. This approach requires no migration, no operational change, and no retraining — only a change in support provider. It is the fastest path to cost reduction for enterprises not yet ready to migrate away from Automic.

11. Negotiating Broadcom Automic Renewals

Broadcom’s Automic renewal negotiations follow a pattern that is consistent across their entire portfolio. Understanding the pattern enables you to counter it.

The pattern: Broadcom sends a renewal proposal 60–90 days before expiration at a significantly increased rate (40–300% above current). The proposal bundles products you may not use. The timeline creates urgency. The implicit message: accept the increase or risk losing support and maintenance on mission-critical batch processing infrastructure. This is a negotiation tactic, not an ultimatum.

Counter-strategy 1: Start early. Begin renewal preparation 12 months before expiration. Conduct the licence optimisation programme in Section 9 during months 12–8. Evaluate alternatives and obtain competitive pricing during months 8–4. Enter Broadcom negotiation during months 4–2 with documented alternatives, a right-sized licence position, and clear leverage.

Counter-strategy 2: Unbundle. Reject the Value Plan bundle and request standalone AWA pricing. If Broadcom insists on the bundle, identify the products you don’t use and negotiate their removal from the agreement with corresponding price reduction. Every product you remove reduces the total deal value and your cost.

Counter-strategy 3: Right-size before you negotiate. Remove inactive agents, correct tier classifications, and verify mainframe MIPS before presenting your renewal requirements to Broadcom. Presenting a right-sized entitlement request (400 endpoints instead of 500) immediately reduces the negotiation baseline by 20%. Broadcom cannot charge for endpoints you have verifiably decommissioned.

Counter-strategy 4: Use competitive displacement credibly. Obtain written proposals from BMC Control-M and/or Redwood RunMyJobs before engaging Broadcom. Present the competitive proposals explicitly: “We have evaluated Control-M at $X/year with migration services included. To remain on Automic, we need pricing that is competitive.” Broadcom’s deal desk has competitive displacement pricing authority that is not available for standard renewals. Activating this authority requires a credible competitive threat — not a vague statement that you are “evaluating options.”

Counter-strategy 5: Negotiate reduction rights. Secure 15–20% annual reduction rights on endpoint counts and MIPS/MSU allocations. As you migrate workloads to alternatives, consolidate environments, or move to the cloud, your Automic footprint should decrease. Without reduction rights, you are locked into the renewal quantity for the full term. This is the same principle applied in all Broadcom negotiations and across other vendors like Salesforce.

12. Third-Party Support for Automic

Third-party support has emerged as a powerful cost-reduction tool for Automic, following the same model that enterprises use for VMware, Oracle, and SAP. Third-party providers offer ongoing technical support, security patching, and break-fix assistance for the current Automic version at 50–60% below Broadcom’s support pricing.

How it works: You continue running your current Automic software version (AWA 12.x, 21.x, or whatever version is deployed). The third-party provider delivers 24/7 technical support with defined SLAs, develops and distributes security patches independently of Broadcom, and provides configuration guidance and troubleshooting. Your production environment is unchanged — same software, same configurations, same operational procedures. Only the support provider changes.

What you give up: Access to new Automic version upgrades. If Broadcom releases AWA v23, third-party-supported customers cannot upgrade to it. For enterprises running stable, mature Automic environments where the current version meets all operational requirements, this trade-off is highly favourable. The cost savings of 50–60% far outweigh the value of incremental feature updates in a product whose development velocity has slowed under Broadcom ownership.

When third-party support makes sense: Your Automic deployment is stable and mature. You are not planning major version upgrades. Your primary concern is cost reduction, not new features. You want to maintain full operational capability while reducing Broadcom dependency. You want contractual flexibility — third-party support typically offers annual terms versus Broadcom’s 3–5 year commitments.

When it does not make sense: You require mainframe Automic features that are only available in newer versions. You have a contractual obligation to run a specific version that requires Broadcom support. You are actively migrating away from Automic and need Broadcom’s cooperation during the transition (though this is negotiable).

For enterprises where the annual Automic spend exceeds $500K, the optimisation and negotiation strategies in this guide typically deliver savings that justify engaging independent advisory support. Our Broadcom Advisory practice maintains benchmark pricing data for Automic across all licensing metrics and deployment scales, providing the comparative data that transforms your renewal negotiation from a reactive defence into a proactive cost-optimisation programme.