Try our new research platform with insights from 80,000+ expert users

AutoSys Workload Automation vs Red Hat Ansible Automation Platform comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

AutoSys Workload Automation
Average Rating
8.4
Reviews Sentiment
7.7
Number of Reviews
79
Ranking in other categories
Workload Automation (8th)
Red Hat Ansible Automation ...
Average Rating
8.6
Reviews Sentiment
7.3
Number of Reviews
68
Ranking in other categories
Release Automation (3rd), Configuration Management (1st), Network Automation (1st)
 

Mindshare comparison

AutoSys Workload Automation and Red Hat Ansible Automation Platform aren’t in the same category and serve different purposes. AutoSys Workload Automation is designed for Workload Automation and holds a mindshare of 15.5%, down 19.0% compared to last year.
Red Hat Ansible Automation Platform, on the other hand, focuses on Configuration Management, holds 16.0% mindshare, down 16.3% since last year.
Workload Automation
Configuration Management
 

Featured Reviews

Antony Askew - PeerSpot reviewer
Helps us manage complex workloads, reduce our workload failure rates, and save us time
The visibility and control features are somewhat limited. This is a recognized weakness, but thee vendor is currently revamping the user interface to address it. While the current UI is a bit outdated, it's undergoing improvement. AutoSys Workload Automation has some areas for improvement, particularly in housekeeping and product maintenance. These tasks are currently quite manual and labor-intensive for our team. Additionally, the reporting and forecasting functionalities could be more robust. One area for improvement with AutoSys Workload Automation is that it comprises several distinct tools configured to work together. This necessitates familiarity with multiple tools for effective solution management. Consequently, it can sometimes lack a sense of cohesiveness as a unified solution.
Surya Chapagain - PeerSpot reviewer
Easy to manage and simple to learn
We use Red Hat a lot. I open tickets for the Red Hat cases, however, with Ansible, I haven't opened any cases. My manager worked with them a bit. If we have a problem with some file and we need to get Red Hat to analyze the issue and the file is 100GBs, we'll have an issue since we need to provide a log file for them to analyze. If it is around 12GB or 13GB, we can easily upload it to the Red Hat portal. With more than 100GBs, it will fail. I heard it should cover up to 250GB for an upload, however, I find it fails. Therefore, Red Hat needs to provide a way to handle this.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"It's very easy to work with. The learning curve is not that steep."
"Automic Automation Engine provides us the ability to map logic using a scripting language."
"The features that I have found most valuable with AutoSys are that it is scalable, easy to use, fast, and always available. That's very important because if it's not steady then it's a real problem. So, at this point, we are satisfied with it."
"Integration with multiple services and applications across the enterprise."
"We use technical support all the time. We would be lost without them. They're fantastic. Really good job. We're able to reach the right person to help us out right away."
"The most valuable feature of AutoSys Workload Automation is batch processing."
"It streamlines processing really well, so we're able to cut down on our processing times."
"It has helped to simplify cross-dependency between MVS and Open systems jobs."
"The solution can scale."
"It allows control over thousands of servers, whether virtual or physical."
"The playbooks and the code the solution uses are quite useful."
"Installing it is a PIP command. So, it's pretty easy. It is a one liner."
"The Organizations feature, where I can give clear silos and hand them over to different teams, that's amazing; everybody says that it's their own Tower. It's like they have their own Tower out there."
"Ansible Galaxy is helpful for roles and Git Submodules: No dependency in managing playbooks. Also, fact caching in redis for host/role grp information speeds up execution. Finally, variable management is easy."
"Since it is in YAML, if I have to explain it to somebody else, they can easily understand it."
"The capacity to install products on the operating system is very valuable."
 

Cons

"CA Workload Automation is not part of CA's strategic vision going forward."
"The WCC could be improved."
"AutoSys Workload Automation could improve the integration."
"​A better graphical user interface, because we have a lot of people using the client utility, and we want to get them away from that.​"
"Some of the reports are either a bit hard to understand or don’t give you what you might expect to see."
"The solution does not have a friendly subscription model because it forces users to take a five-year subscription simultaneously, charging millions of dollars."
"It would be helpful to be able to monitor and manage workload windows so we could minimize downstream applications. This would allow us easier access to the applications."
"Ease of implementation for upgrades."
"Some of the modules in Ansible could be a bit more mature. There is still a little room for further development. Some performance aspects could be improved, perhaps in the form of parallelism within Ansible."
"What I would like to see is a refined Dashboard to see, when I log in: Here are all my jobs, here are how many times they've executed; some kind graphical stitching-together of the workflows and jobs, and how they're connected. Also, those "failed hosts," what does that mean? We have a problem, a failed host can be anything. Is SSH the reason it failed? Is the job template why it failed? It doesn't really distinguish that."
"Documentation could be improved. Many times, if I'm looking for something, I have to Google it in a lot of places, then figure out what the best approach will be. There are some best practices documents, but they don't give you the information."
"There are some options not available in the community edition of the solution."
"There needs to be improvement in the orchestration."
"The communication on it is not probably where it could be. We could use some real life examples where we could point customers to them and say, "This is what you are trying to do. If you follow these steps, it would at least get you started a bit quicker.""
"There could be more stuff in the workflows. I hope that if I have ten templates with different services on it, workflow could auto-populate all the template-based services."
"The scalability of the solution has some shortcomings."
 

Pricing and Cost Advice

"We paid to use the solution monthly."
"The return on investment would be very high because doing things manually without this product would be extremely expensive."
"There is an annual license to use AutoSys Workload Automation."
"CA pricing has been a problem, and not looked upon favorably here at all."
"People need to pay attention to how they use their ESP agents on the distributed platform. That's where some of the cost comes in, based on how many you need or how many you use."
"The pricing needs to be improved. Some of my client's complained that it was too expensive."
"Validate how many agents you need beforehand."
"The price of this solution is reasonable and there is an annual license required."
"I don't see the pricing or licensing features, but from what I understand, it is fairly reasonable."
"If you only need to use Ansible, it's free for any end-user, but when you require Ansible Tower, you need to pay per Ansible Tower server."
"We have to be mindful of how we use Ansible because of the licensing model. I am not saying that it is unfair or we do not find value in it. Because we are trying to automate so many different things, we have to be mindful of what we are doing and how we are doing it because we are trying to stay in compliance with it."
"The pricing for us is huge because we use twenty thousand nodes, so that is a huge infrastructure, but if someone is using a small infrastructure, then the pricing is not so much."
"The cost is determined by the number of endpoints."
"I am using the community edition of the solution which is free."
"The solution is inexpensive compared to other products."
"We're charged between $8 to $13 a month per license."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
831,265 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
47%
Manufacturing Company
12%
Computer Software Company
6%
Insurance Company
5%
Educational Organization
32%
Financial Services Firm
14%
Computer Software Company
10%
Manufacturing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

How does Control-M compare with AutoSys Workload Automation?
Control-M acts as a single, centralized interface for monitoring and managing all batch processes, which is helpful because nothing gets left unattended since it is all visible in one place, and th...
What do you like most about AutoSys Workload Automation?
The most valuable aspects of AutoSys Workload Automation are its performance, scalability, and ease of getting started for new users.
What is the difference between Red Hat Satellite and Ansible?
Red Hat Satellite has proven to be a worthwhile investment for me. Both its patch management and license management have been outstanding. If you have a large environment, patching systems is much ...
How does Ansible compare to Microsoft Endpoint Configuration Manager (SCCM)?
Microsoft Endpoint Configuration Manager takes knowledge and research to properly configure. The length of time that the set up will take depends on the kind of technical architecture that your org...
What do you like most about Red Hat Ansible Automation Platform?
The most valuable features of the solution are automation and patching.
 

Also Known As

CA Workload Automation, CA Workload Automation AE
Ansible
 

Learn More

 

Overview

 

Sample Customers

Gaumont, Mercantil do Brasil, CCEE, Hanwha Life
HootSuite Media, Inc., Cloud Physics, Narrative, BinckBank
Find out what your peers are saying about BMC, Redwood Software, Broadcom and others in Workload Automation. Updated: January 2025.
831,265 professionals have used our research since 2012.