- BFSIBanking, Financial Services & Insurance
- HealthcareComing soon
- ManufacturingComing soon
- Retail & E-CommerceComing soon
Automic Automation
Your batch runs on a mainframe, SAP and three clouds. Its schedule shouldn’t live in five tools — Automic Automation runs scheduled work from mainframe to microservices on one engine — on-premises, in your own Kubernetes or as Broadcom-run SaaS, with SAP jobs, file transfer and AI steps built in.
Buy through TechBag
Same software. Better outcome — at a lower cost.
How it’s rated
Full scoreboard ↓Quick answer
The Broadcom platform family
This page covers Automic Automation — the workload automation platform. The rest:
Quick facts
30-second orientation- Product
- Enterprise workload automation and orchestration, from mainframe batch to cloud and data pipelines
- Maker
- Broadcom Inc., Palo Alto; ex-Automic Software, bought by CA in 2017, which Broadcom bought in 2018
- Status
- V26.0.0 generally available since 9 April 2026; V24 remains supported, with Service Pack 4 (24.4.4)
- Price
- Not published; Broadcom quotes every licence, on-premises or SaaS, through sales and partners
- Licence
- Subscription; Broadcom publishes no licence unit, so ask which count your quote is built on
- Deployment
- On-premises, Kubernetes Edition on any cloud, or Automic SaaS run by Broadcom on Google Cloud
- Coverage
- Mainframe, distributed, virtual and cloud; SAP incl. RISE with SAP, Oracle, file transfer, Python
- Scale
- Broadcom’s 2026 brief cites up to 100,000 agents and 100 million jobs in a single instance
- India
- SaaS hosted in the US and Europe; self-hosted keeps data in India; offices in Bangalore, Hyderabad, Pune
- In India via
- TechBag — scheduler inventory, quote in INR with GST, first cross-platform workflow
Understand workload automation before you buy it
Most product pages skip this. We start here — so you buy a capability, not a buzzword.
What is workload automation?
One engine runs scheduled jobs on every platform and links them by dependency, not by start time.
Cron, scripts and a scheduler per platform vs one automation engine — the honest table
What consolidation actually replaces, dimension by dimension.
| Dimension | Cron, scripts, a scheduler each | Automic Automation |
|---|---|---|
| Where jobs are defined | Cron, Task Scheduler and one tool per app | One engine, with mainframe to cloud as objects |
| Cross-platform handoffs | Timed gaps and hopeful start times | Real dependencies between jobs on any host |
| A late upstream job | Found when the morning report is missing | Flagged on the dynamic critical path first |
| File movement | Scripts around FTP, restarted from zero | Managed transfer with checkpoint restart |
| Proving control to auditors | Screenshots and change tickets | Audit of every run and user action |
| What it is NOT | — | An RPA bot, a ticketing tool or a price list |
The cheapest test is one cross-platform workflow: a mainframe or SAP step, a file transfer and a cloud job, with an SLA deadline attached.
The five pieces of the platform
Vendors love diagrams; buyers need to know what they’re actually operating. Here’s the whole platform, demystified.
Engine
The Automation Engine keeps jobs, workflows, schedules and calendars in its database and hands work to agents; on Automic SaaS, Broadcom runs it in a Kubernetes cluster.
Agents
Agents on Windows, UNIX and z/OS hosts, and for applications such as SAP, run each job and report status back; even on SaaS, the customer hosts and manages them.
Interfaces
Operators design and watch workflows in the Automic Web Interface; developers code objects and promote them dev to test to prod, with token-based REST authentication since V24.2.
Analytics
AAI, a separate Broadcom product, gathers workload history across schedulers from more than one vendor, so trends and SLA risk can be read across a mixed estate.
One Automation Engine and its database — agents on every host, run by you on-premises, in Kubernetes, or by Broadcom as SaaS.
Nine capabilities. Orchestrate, integrate, govern.
Automic Automation runs every scheduled job, ERP batch and file transfer from one engine, wherever the work executes.
Mainframe to cloud in one flow
One workflow chains z/OS, distributed, virtual and cloud jobs, built from reusable objects that can be changed while they run.
Deadlines and the critical path
Set deadlines per process and see dependencies on a dynamic critical path, so a late upstream job shows before the SLA slips.
Push-button runs for the business
Staff start runs, pass parameters and track requests from the Automic service catalog or a third-party one, with no job editing.
SAP and Oracle job types
Adapters cover SAP on-premises, RISE with SAP and SAP BTP, plus Oracle on-premises and cloud, beside non-ERP steps in one flow.
Managed file transfer included
Transfers carry automatic character conversion, encryption, compression and checkpoint restart, so a broken copy resumes mid-file.
Integrations and action packs
The Automation Marketplace lists integrations for cloud services, ERP platforms and data-pipeline tools, plus action packs.
Every run and user action logged
Auditing covers all automated processing and user activity, and lifecycle tooling promotes policies from dev to test to production.
Upgrades without a maintenance window
Broadcom says versions and patches install with zero downtime; from V24, each major version carries a five-year support lifecycle.
AI steps under the same controls
V26 adds an AI Job type and an MCP client and server, so model calls run inside workflows under the same access rules and audit.
Watch Automic Automation in action
Orchestrating SAP beside the rest of a hybrid landscape (2026), and what changed in the v24 release (2024).
Automic Automation for SAP: Unify & Orchestrate Your Hybrid Landscape
How Automic runs SAP jobs, including RISE with SAP, beside the non-SAP steps of the same business process.
What's New in Automic Automation v24
The v24 release from 2024, still supported; V26 has since added AI job types and MCP on top of it.
Want a live, India-context walkthrough for your environment?
Book a guided demo →Every platform brings its own scheduler. Automic runs them all from one engine.
What earns Automic a shortlist place — and the limits to plan around.
One engine where there were five schedulers
Mainframe batch, SAP chains, Oracle jobs, cloud services and file transfers often each have their own scheduler. Automic puts them on one Automation Engine with real dependencies, so a late z/OS step holds an SAP job and a cloud load until it finishes.
Three ways to run the same product
Broadcom sells Automic on-premises, as a container-based Kubernetes Edition, or as Automic SaaS, with the same features in each. Workloads can move to SaaS in stages. On SaaS, Broadcom runs the engine and database; your agents stay on your own servers.
AI steps that obey the scheduler’s rules
V26, generally available on 9 April 2026, adds an AI Job type, an MCP client and server, plain-language workflow creation, Code Assist and native Python jobs. Broadcom says you can bring your own model, self-hosted included, so sensitive jobs avoid public LLMs.
Where it stops
No price list and no published licence unit, so budgets wait for a quote. Automic SaaS is hosted in the US and Europe, with no Indian region documented. Agents stay yours to patch: two 2025–26 UNIX-agent CVEs needed hotfixes. It is not an RPA or ticketing tool.
The numbers behind the platform
What your Automic Automation rollout looks like
Count every scheduler you run
List cron tables, Windows tasks, the mainframe scheduler and each app’s own jobs, with owners, run times and hand-offs.
Choose where the engine lives
Decide on-premises, Kubernetes Edition or Automic SaaS against your data-location rules; SaaS today means US or Europe.
Build one cross-platform chain
Install agents on a z/OS or SAP host and a cloud host, then model one real process with dependencies and an SLA deadline.
Run it beside the old scheduler
Run the new workflow in parallel through a month-end, compare start times and failures, and add file transfers.
Migrate in waves and retire
Move job groups one platform at a time, switch off the old schedulers they replace, and set an agent-patching routine.
The review scoreboard
Modelled on Gartner Peer Insights structure. *Counts and breakdowns are illustrative pending verified review collection.
Quick poll — what’s driving your evaluation?
Talk to an advisor“Month-end used to depend on three schedulers and an operator watching all of them. Now the mainframe step simply holds the SAP job.”
“The critical-path view told us at 1 a.m. that the 6 a.m. report would be late, which left time to fix the upstream load.”
“Checkpoint restart matters on our plant links. A file transfer that drops at 80% picks up where it stopped, not from zero.”
“We promoted job objects from test to production through the lifecycle tooling, and audit finally stopped asking for screenshots.”
“We moved to SaaS but still patch our own agents. Plan for that; the UNIX agent needed two hotfixes in a year.”
“Powerful, but the object model takes months to learn, and the renewal quote was hard to compare with last year’s.”
Where everyone sits — the grids
Analyst firms bury this view behind paywalls, and G2 retired its Grid. So here’s TechBag’s synthesis of the workload automation market — tap any vendor to see why it sits where it does.
TechBag Workload Automation Grid
Execution strength vs product vision — the classic market map, minus the paywall.
EMA Value Leader 2025; V26 added AI jobs and MCP in April 2026.
Deployment Choice × Estate Reach
The grid nobody publishes — how many ways the scheduler can be run and where its data can sit, India included, vs how much of a mixed estate it reaches.
On-prem, Kubernetes or SaaS; mainframe, SAP, Oracle, file transfer.
Positions are TechBag’s illustrative synthesis of public review-platform data and vendor documentation — not a reproduction of any analyst graphic. Verify before relying on it.
Automic Automation vs the workload automation field
Against BMC Control-M, Redwood RunMyJobs, Stonebranch Universal Automation Center, HCL Workload Automation and Apache Airflow — on deployment, estate covered, SAP, price, scale, AI and India.
| Dimension | Automic Automation | BMC Control-M | Redwood RunMyJobs | Stonebranch Universal Automation Center | HCL Workload Automation | Apache Airflow |
|---|---|---|---|---|---|---|
| What it is | Broadcom’s WLA platform | BMC’s orchestrator | SaaS-only scheduler | Hybrid automation hub | HCL’s scheduler line | Open-source orchestrator |
| Deployment | On-prem, K8s or SaaS | SaaS, self-host, hybrid | Managed SaaS only | On-prem or SaaS | On-prem or containers | Self-run or rented |
| Estate covered | Mainframe to cloud | z/OS to cloud services | Agentless, SAP-first | 150+ integrations | 80+ plug-ins, z/OS | Data pipelines first |
| SAP and ERP | RISE with SAP certified | RISE with SAP certified | SAP Endorsed App | SAP via integration | S/4HANA certified | No certified SAP job |
| Pricing model | Quote; unit unpublished | By execution volume | Quoted platform fee | By task executions | Pay per completed job | Free licence |
| Published entry price | Not published | $2,400/month | Quote only | Private offers only | Not published | $0; MWAA $0.49/hr |
| Included vs add-on | AAI sold separately | Starter is full-featured | Three pre-prod included | Not itemised publicly | Separate z edition | No vendor support |
| Scale | 100,000 agents (claim) | Not published | Not published | Not published | Millions a day (claim) | Depends on your setup |
| Security and governance | Audit, RBAC, OAuth 2.0 | Archive, jobs-as-code | Single-tenant instance | Not captured | Usage audit trail | Depends on deployment |
| AI and agentic features | AI Job + MCP (V26) | Jett + AI workflows | RangerAI, agentic flows | MLOps workflows | Not captured | ML pipelines in code |
| India data | No India SaaS region | Region not published | Region not published | Self-host in India | Indian parent, self-host | Wherever you run it |
| Support | 5-year lifecycle | 24×7 from Starter | 24×7 Sev-1 included | Not captured | Not captured | Community only |
| Lock-in and exit | Automic-specific objects | JSON jobs-as-code | SaaS-only exit | UAC-specific tasks | HCL-specific streams | Open-source Python |
| Best fit | Mainframe + SAP estates | Priced SaaS entry | SAP-centred, SaaS-happy | Hybrid, integration-led | Job-metered, India-based | Python data teams |
Which approach fits you?
Honest fit signals — because the fastest way to lose your trust is to pretend one product wins every scenario.
Choose Automic Automation if…
- ✓Mainframe batch, SAP or Oracle chains and cloud jobs must depend on each other, not run on separate schedulers with timed gaps
- ✓You want the same product on-premises, in Kubernetes or as SaaS, so data-location rules decide the hosting rather than the feature list
- ✓You plan to put LLM steps into production workflows and need them under the scheduler’s access rules and audit trail
Compare alternatives if…
- ✓You want a published starting price before any sales call — Control-M’s SaaS Starter Pack lists one
- ✓Your pipelines are mostly Python data work and your team can run the platform — Apache Airflow costs nothing to license
- ✓You want a scheduler that never touches your servers — Redwood RunMyJobs is managed SaaS only
Do not expect…
- ✓A rate card or a published licence unit for any Automic deployment
- ✓An Indian Automic SaaS region — Broadcom documents US and European data centres
- ✓Agent-free SaaS: on Automic SaaS you still host, upgrade and patch every agent
TechBag has no workload automation guide yet, so Automic Automation sits outside the category guides. Browse all products to compare it with the rest of the catalogue. →
What does scheduler sprawl cost you?
Drag the sliders (jobs in your schedule; operator-hour cost). Estimates model time spent rerunning failed jobs, chasing cross-platform hand-offs and editing calendars at an assumed 1.5 hours per job a year, with 70% of it removed by one engine with dependencies and SLA tracking. Both figures are assumptions. Illustrative.
Loaded cost = salary + overheads per productive hour. Illustrative only — your TechBag quote models your actual environment and modules.
Three ways to consume it
Not published: Broadcom lists no price and no licence unit for Automic Automation — on-premises, Kubernetes Edition or Automic SaaS, every deal is quoted. TechBag counts your schedulers, jobs, agents and environments first, then gets the quote itemised in INR with GST.
Automic SaaS
Best for teams retiring scheduler servers
- Quote-only subscription
- Broadcom runs engine and database
- Hosted in US or European data centres
+ Platform add-ons
Best for a broader rollout
- Scoped to your estate
- Add-on modules as needed
- Phased, right-sized deployment
On-premises or Kubernetes Edition
Best when job data must stay in India
- Quote-only; licence unit not published
- Full control of infrastructure
- Same feature set as SaaS
Buy it for less — TechBag pricing beats list
Whatever the list prices above, TechBag negotiates a significantly better deal — with GST-compliant INR invoicing and local support. Ask us for your discounted quote.
Get an India-ready quote
Tell us your requirements and current tools — we’ll model it against what you spend today.
The 8 questions to ask every vendor
Take this into your next vendor call — including ours.
Which schedulers, cron tables and app-specific job tools will Automic replace, and how many jobs does each run?
On-premises, Kubernetes Edition or SaaS? If SaaS, is US or European hosting acceptable for your job data?
What count is the quote built on — jobs, agents, executions or something else — and what happens when you grow?
Are you on SAP on-premises, RISE with SAP or BTP, and does the quote include the SAP agent you need?
Who patches agents? The UNIX agent needed hotfixes for CVEs in 2025 and 2026; plan a routine before go-live.
Will you start on V26 or V24, and when does the five-year support window for that major version close?
Do you need Automation Analytics & Intelligence for cross-scheduler reporting? It is a separate Broadcom product.
Is the quote itemised in INR with GST, with renewal terms and the number of non-production environments stated?
Questions buyers ask
Ready to evaluate Automic Automation?
Inventory your schedulers and cron tables first, or let a TechBag advisor scope a pilot that moves one SAP or file-transfer chain onto Automic.
Stats, ratings, review counts and pricing are illustrative and sourced from public materials; verify before purchase.