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

AWS Step Functions vs AutoSys Workload Automation comparison

Sponsored
 

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

JAMS
Sponsored
Ranking in Workload Automation
3rd
Average Rating
8.8
Reviews Sentiment
6.9
Number of Reviews
38
Ranking in other categories
No ranking in other categories
AutoSys Workload Automation
Ranking in Workload Automation
5th
Average Rating
8.4
Reviews Sentiment
6.6
Number of Reviews
84
Ranking in other categories
No ranking in other categories
AWS Step Functions
Ranking in Workload Automation
11th
Average Rating
8.4
Reviews Sentiment
6.7
Number of Reviews
14
Ranking in other categories
Business Process Management (BPM) (10th)
 

Mindshare comparison

As of February 2026, in the Workload Automation category, the mindshare of JAMS is 2.8%, up from 1.7% compared to the previous year. The mindshare of AutoSys Workload Automation is 8.0%, down from 14.9% compared to the previous year. The mindshare of AWS Step Functions is 1.6%, up from 1.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation Market Share Distribution
ProductMarket Share (%)
JAMS2.8%
AutoSys Workload Automation8.0%
AWS Step Functions1.6%
Other87.6%
Workload Automation
 

Featured Reviews

reviewer2770605 - PeerSpot reviewer
Cloud Engineer at a financial services firm with 501-1,000 employees
Has streamlined complex job scheduling across scripting languages while reducing manual effort
JAMS could be improved with a web client that is accessible and as fast as a normal website, eliminating the need to RDP to the servers to access the JAMS client. A functionality running on the JAMS server to continuously check the JAMS agents would ensure they are working properly. If an agent is not responding, a feature to restart the service from the job server machine would be beneficial. The upgrade process, particularly when switching from V6 to V7, could be clearer in terms of documentation, ideally with screenshots showing exactly what needs to be done on each screen.
PK
Assistant VP at a financial services firm with 10,001+ employees
Experience significant automation with robust integration and user-friendly interfaces
There are areas of AutoSys Workload Automation that have room for improvement. They are implementing good enhancements in the R24 release. The web UI needs some improvement. Cloud integrations are limited to 25 or 30 configurable plugins and integrations to the cloud. They can improve in that area. They have separate tools, not AutoSys Workload Automation, such as Atomic and other SaaS-based solutions that can run inside the cloud. AutoSys Workload Automation can be configured in the cloud, but it requires a substantial number of VMs depending on the load. For on-premises deployment, it is a very good solution. They need to increase their footprint in the cloud and improve the web UI. They are making excellent progress in the R24 release.
reviewer2706945 - PeerSpot reviewer
Assistant Manager at a tech vendor with 10,001+ employees
Orchestration and integration simplify processes with seamless stability and reliability
I use the Visual Workflow Editor feature of AWS Step Functions. I mainly work through code and then improve it through the visual aspect. There are two ways to do orchestration: through code and through visual. My main task is to develop flows. I have only implemented AWS Step Functions with AWS services, not with any third-party tools. The integration between AWS Step Functions and other AWS services is excellent, working seamlessly with EventBridge, Glue jobs, and databases. I have not encountered any challenges with customers regarding AWS Step Functions that needed me to find a workaround. The pricing of AWS Step Functions is moderate and not particularly costly. AWS Step Functions is affordable for small, medium, and enterprise businesses as an orchestration tool. I have not used any documentation, manuals, or guides for AWS Step Functions as it's very simple to implement. When help is needed, I consult Stack Overflow or AI for commands. Overall rating for AWS Step Functions: 9 out of 10.

Quotes from Members

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

Pros

"Being able to create a series of chained jobs, which are basically linked jobs is valuable."
"The most valuable aspect of JAMS is its robustness."
"The most valuable feature for us is that it's DR-ready. With respect to disaster recovery, it has the built-in capability for failover to our DR site. If all of the required ports are open, it can be done seamlessly."
"The most valuable feature of JAMS is its user-friendly interface, especially after upgrading from version six to seven."
"It makes everything that we want to do so much easier. We have had a number of instances in the past where we have had developers who have been working on a project, and even though we have had JAMS for all these years, they will create some SQL Server Agent job, or something like that, to run a task. When it is in code review and development is complete, the question always comes around, "Can JAMS do this?" The answer has always been, "Yes." Pretty much anything we have ever developed could be run by JAMS."
"We looked at other companies, like VisualCron, that were cheaper, but one of the main sticking points was the fact that they wouldn't have provided a central location for us to monitor across all servers. That was one of the biggest selling points of JAMS."
"JAMS is easier to use and cheaper than our previous solution. The installation is more straightforward, and JAMS has a graphical user interface, so it's more accessible."
"The interface is good, and it's very easy to define and create jobs. If a job is not running or there is an error, the solution will send an email. That's all very good and very useful."
"Without this product we would have to manually submit jobs and it would take longer. There would also be a much greater possibility of jobs running wrong and/or not at the right time."
"It gives a real-time view of all the batch processing that we have. Monitoring-wise, it is really good."
"This solution enables us to improve our daily processing times. We can do everything faster than before we used this solution."
"Running anything in crontab, you need to put a lot of logic into it to make it work. With this product, you don't have to worry about it. You have the schedule object where you put all the dates or holidays in it, and it does it for you."
"It has helped to simplify cross-dependency between MVS and Open systems jobs."
"Inherit Dependencies feature reduces scheduling errors for holiday processing."
"The most valuable aspects of AutoSys Workload Automation are its performance, scalability, and ease of getting started for new users."
"The most valuable feature of AutoSys Workload Automation is user-friendliness. If someone has some knowledge of the tool they can use it."
"The number of historical events is great."
"AWS Step Functions acts as a high-level layer, allowing us to seamlessly integrate with microservices."
"AWS Step Functions offers advanced workflows that save time and enhance efficiency by reducing delays and ensuring consistent orchestration among various services."
"AWS Step Functions was stable, and there were no problems that I can recall."
"It's Amazon, it's scalable."
"The JSON app launched recently allows us to define data execution more easily."
"The integration capability is easy, whereas building state machines is tricky."
"The solution is stable...The solution is easy to scale."
 

Cons

"I would like a simple web interface that I could give to my team to go in and kill jobs or see why jobs died so that we don't have to drill down deeper into the application and know everything about it. It would be good to have a really clean web engine that would say here are the jobs running. We can then click to see the time running and whether any of them fails and other similar things. I know they have one, but it's not very simplistic."
"If around 5,000 or more jobs run at a time, JAMS slows down, and we have to wait around five to 10 minutes or restart JAMS scheduler services."
"I want JAMS to implement a global search function."
"The search capability needs to be improved because when we try to search for a job, it's hard to do."
"The biggest area with room for improvement is the area that my organization benefits the most from using JAMS, and that is in custom execution methods. I happen to have a very good C# developer. Ever since we got JAMS, he has spent a lot of time talking to JAMS developers, researching the JAMS libraries, and creating custom execution methods. He's gotten very good at it. He is now able to create them and maintain them very easily, but that knowledge was hard-won knowledge. It was difficult to come by, and if I should ever lose this developer, then I would be hard-pressed to find anyone who could create JAMS custom execution methods quite as well as he can since there really isn't all that much help, such as documentation or information, available on how to create custom execution methods."
"I would like to see the ability to interface with Microsoft group-managed service accounts, but they're still in the research phase. They need to ensure everything's legit and safe. The report designer and dashboards could also be improved. We're running 7.3, so I don't know if they have updated the reporting in 7.5, but I think the reports and dashboards could be better."
"Improvements could be made in the service desk's knowledge and communication skills among engineers to better address customer needs and ensure issues are fully resolved."
"One thing that I know that the JAMS people said that they were working on that would be huge for us is a search capability so that you could search for tasks. It may be available in version 7 or in a future release of 7. I think that's on their roadmap. But right now, for us to do a search, we have to search through database queries."
"Reduce the number of operational files. This would make the job of a system programmer supporting ESP easier."
"An area for improvement in AutoSys Workload Automation is that it lacks advanced features or advanced built-in functionalities found in competitors, for example, an advanced workflow feature. Even the handling or notification from AutoSys Workload Automation isn't the best in the industry. Other products have very good workflow-related functionalities such as ActiveBatch that's missing in AutoSys Workload Automation, so I wish the tool had those features."
"It lacks support and integration with cloud computing platforms."
"AutoSys Workload Automation could improve in the Linux environment. The previous versions of the AutoSys Workload Automation let you take the profile of the user that you were using to run the tasks that you're going to automate, but in the latest versions, you can't do that, you need to make more definitions and it's a little bit difficult. It was easier in the previous versions."
"Since Broadcom acquired it, the prices have increased. Many companies feel the same way and are looking for alternate solutions to replace AutoSys Workload Automation."
"To make it a lot more user-friendly, in order to make it so other people can use it without having to do much training with it; the more user-friendly it is, the easier it is to work with."
"The graphical interface can be improved."
"They could do better supporting it. They have too many of the same type of products, so sometimes it doesn't get as much attention as it should."
"One area for improvement is the payload size. Currently, I sometimes have to save data as a file since I cannot pass it within Step Functions, necessitating caching in processes."
"Increasing the payload size would be beneficial."
"It is hard to coordinate the declaratory language."
"There is room for improvement in terms of integration with other products. It would benefit from more integration with different applications or services."
"If AWS Step Functions keeps adding more integrations, it would be even better."
"Setup took about one day. We had some errors to understand in the beginning, but now everything is working good."
"The solution's pricing could be cheaper. It is cheaper than Airflow."
"The pricing of the solution can be improved."
 

Pricing and Cost Advice

"The licensing model for JAMS is straightforward and based on the number of agents, not the number of jobs you run. It's cheap and fairly simple."
"Definitely check how many single processes you want to run and count them as jobs. That is how you would work out your pricing on JAMS. For example, if you're running a number of commands and you can put them all into one script and run that script, you can count that as one job."
"The product is reasonably priced, and we don't have any add-ons."
"For what it does, the product is priced very well."
"All licensing models are a little overpriced, but JAMS offers a good value, especially given their support response times and ability to handle unforeseen issues like the SFTP transfers. I hope to find more use cases to get a better bang for our buck."
"It's certainly a lot cheaper than Tivoli and Control-M. In comparison to them, you get a lot more bang for your buck. You get pretty much the whole functionality and more, in some cases, when compared to Control-M, but at a fraction of the price."
"There are no additional costs other than the license for Fortra's JAMS which is affordable."
"It was $10,000 for the first year. Then, there is a maintenance cost for licensing every year that we get billed $5,000 for every year."
"The price of this solution is reasonable and there is an annual license required."
"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."
"There is an annual license to use AutoSys Workload Automation."
"I certainly think the pricing is worth the value."
"Validate how many agents you need beforehand."
"It is overpriced."
"The solution is expensive."
"The solution's price is reasonable."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
882,744 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Computer Software Company
11%
Manufacturing Company
11%
Healthcare Company
5%
Financial Services Firm
42%
Manufacturing Company
9%
Retailer
5%
Insurance Company
5%
Financial Services Firm
26%
Manufacturing Company
10%
Computer Software Company
7%
Insurance Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise8
Large Enterprise19
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise5
Large Enterprise77
By reviewers
Company SizeCount
Small Business7
Midsize Enterprise2
Large Enterprise5
 

Questions from the Community

What do you like most about JAMS?
I find the historical tracking feature of JAMS invaluable for reviewing past events.
What is your experience regarding pricing and costs for JAMS?
They recently switched to subscription-based pricing, which increased. The price is fair considering the functionalit...
What needs improvement with JAMS?
As far as we are using JAMS version 6, it looks good and there is nothing major to add about it. Everything is functi...
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 b...
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 starte...
What do you like most about Amazon Step Functions?
The integration capability is easy, whereas building state machines is tricky.
What is your primary use case for Amazon Step Functions?
My customer's usual use cases for AWS Step Functions that I've been working with include orchestration, flows, diagra...
What advice do you have for others considering Amazon Step Functions?
I use the Visual Workflow Editor feature of AWS Step Functions. I mainly work through code and then improve it throug...
 

Also Known As

No data available
CA Workload Automation, CA Workload Automation AE
Amazon Step Functions, Step Functions
 

Interactive Demo

Demo not available
Demo not available
 

Overview

 

Sample Customers

Teradata, Arconic, General Dynamics, Yum!, CVS Health, Comcast, Ghiradelli, & Boston’s Children’s Hospital
Gaumont, Mercantil do Brasil, CCEE, Hanwha Life
Alpha Apps, The Guardian, SGK, Bigfinite
Find out what your peers are saying about AWS Step Functions vs. AutoSys Workload Automation and other solutions. Updated: January 2026.
882,744 professionals have used our research since 2012.