No more typing reviews! Try our Samantha, our new voice AI agent.

AWS Step Functions vs AutoSys Workload Automation comparison

Why PeerSpot?
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 Scheduler
Sponsored
Ranking in Workload Automation
3rd
Average Rating
8.8
Reviews Sentiment
6.5
Number of Reviews
46
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.8
Number of Reviews
15
Ranking in other categories
Business Process Management (BPM) (12th)
 

Mindshare comparison

As of September 2026, in the Workload Automation category, the mindshare of JAMS Scheduler is 3.4%, up from 2.0% compared to the previous year. The mindshare of AutoSys Workload Automation is 6.4%, down from 10.0% compared to the previous year. The mindshare of AWS Step Functions is 2.1%, up from 1.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation Mindshare Distribution
ProductMindshare (%)
JAMS Scheduler3.4%
AutoSys Workload Automation6.4%
AWS Step Functions2.1%
Other88.1%
Workload Automation
 

Featured Reviews

LV
Principal Data Base And Infrastructure Engineer at a outsourcing company with 501-1,000 employees
Automation has replaced nightly monitoring and delivers reliable, unified job scheduling
We have really enjoyed working with JAMS in terms of notifications, alerts, and streamlining. There used to be a process with Automate, which is another product from Fortra, but even before that, the other division of the company that we were merging with had a tool that was built in-house called a file handler or file distributor. It was an in-house developed tool, but it was not as streamlined or as efficient as JAMS is. We literally had to have a dedicated nighttime person monitoring. Although we are 24/7, the divisions of the company that we were using JAMS for have been small scale. While we have automated it, we have streamlined it in such a way that notifications go out and alerts go out, but if there is anything, then we get paged and alerted, and if anything needs to happen at midnight, we can wake up. On the other hand, with the tool I mentioned, the file handler and distributor, we used to have a dedicated nighttime person that had to be sitting and monitoring it to see when a file arrived, whether it met the conditions, and then execute the next particular job. By using JAMS, we have gained a lot more efficiencies in terms of all of those to streamline it, and there is no necessary need for having an overnight engineer just keeping an eye on all of this.
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.
YM
Senior Software Engineer at a tech services company with 10,001+ employees
Central orchestration has streamlined complex data workflows and now drives timely aviation alerts
The best features AWS Step Functions offers include the ability to deploy it via code. It helps us orchestrate anything that we want. Even if we have Glue jobs for another use case or Lambda that we are currently looking forward to, we are using Lambda to take DynamoDB data for real-time sales monitoring, then it goes to our S3 bucket. We have multiple workflows that are orchestrated by AWS Step Functions, and at the core, the main functionality is based on different frameworks. We have an Athena complete workflow, Glue job-based workflow, and a separate Lambda-based workflow. All of these are separately handled in AWS Step Functions. This is a good point and again with the inbuilt facilities of it, including how we can construct those workflows and add up a catch state or roll back or do multiple iterations using the Map state, that is very helpful for us.The Map state feature has specifically helped my team create a rollback state of the data since we were dropping some of our data assets. In case we want them back, we just wanted to do this. We took a particular layer and provided the data list, including the tables list, and using the Map state, we iterated over this list and one by one we did the backups of this data at the concurrency of five tables in a single execution. The Catch state, on the other hand, allows us to identify any error immediately. If we encounter an error, the Catch state immediately picks it up and we integrated webhooks or email notifications. That is how we are able to identify immediately if we face any error. At the core of our data engineering platform, AWS Step Functions sit at the topmost core of whatever pipelines we have. It is a main orchestration tool for us and helps us save costs. It is a key component of our engineering platform.

Quotes from Members

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

Pros

"This feature helps my team day-to-day by running hundreds and hundreds of jobs on JAMS in a timely fashion, which is extremely important and sensitive, providing a lot of reporting to the entire firm and beyond."
"The planning capabilities are most valuable."
"JAMS has improved my organization by taking a myriad of manual processes and allowing us to automate them. It enables our folks to focus more on tasks that require their human intelligence and their creativity and less on just mundane tasks. It increases efficiency, accuracy, and consistency."
"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."
"I find the historical tracking feature of JAMS invaluable for reviewing past events."
"The scheduling and execution of jobs are the most valuable features. The scheduling is important because if there is a task we want to execute at 4:00 AM, there's no way we will have someone who can manually run the job. In addition, we execute 100 to 200 jobs per day, and manual intervention is not an option."
"It has definitely drastically improved our capabilities to scale our automation. Before JAMS, there were a lot of manual processes. We had a couple of operators who spent all day doing that. A lot of the time with human intervention and human processes, it is as good as the person who may be following a procedure and human error is a big problem."
"In summary, this product is top class."
"Autosys is one of the oldest products in the market, and it has been around for quite a long time, close to 20 to 25 years."
"The actual scheduling of our jobs has helped us tremendously, as before it was all done manually and we have totally automated the whole functionality, so there is no longer a case where somebody did not run something and it is 100 percent reliable."
"​We run millions of jobs through it every day using it for financial transactions, banking, credit cards, PeopleSoft, payroll, etc."
"It is a lot more powerful and a lot more secure."
"The tool can probably handle way bigger stuff than what we are doing."
"We're able to monitor a complex workload, easily see where we're at in our batch flows, and take care of problems before they become bigger issues."
"We automate recurring processes, keeping track of IT processes controlled worldwide."
"Automation of patch process."
"The solution is stable...The solution is easy to scale."
"What I like the most about Amazon Step Functions is how easy it is to use."
"One can rate all the calls and that is a good feature."
"AWS Step Functions acts as a high-level layer, allowing us to seamlessly integrate with microservices."
"It's a general solution that you can adapt to your own needs and is simple to use. We like that it can be integrated with everything in the AWS suite, and that the creation of the pipeline can be done using the graphical user interface."
"The number of historical events is great."
"It's Amazon, it's scalable."
"The integration capability is easy, whereas building state machines is tricky."
 

Cons

"The cost has definitely gone up tremendously. That is where I do know, as much as the feature sets are there, and if the newly acquired company is going to be doing a pushback, they might just say, 'Do we still need to pay this much? Or at that point, should we look into an alternative?'"
"The client is horrible. Every time JAMS puts out a survey on what they can improve, I always say, "The client: When you are setting up jobs, it is quite horrible." The response has been, "Well, we are just using the Windows foundation," and I am like, "Why isn't it only your product?" We can get around it now that we know its quirks, but it is not the most user-friendly of tools out there. The UI is completely unintuitive. We had to go and open up a support ticket with JAMS just to get something back. It is not user-friendly at all."
"With no programming experience, I find JAMS code-driven automation challenging due to the required PowerShell scripting."
"Sometimes the UI is not the most responsive I've ever used. But because it does its job, I don't complain."
"One area of improvement I see for JAMS Scheduler is making the user interface more intuitive for new users, especially when configuring complex job dependencies."
"If there were a softcover book on how to really take advantage of all of JAMS' tools, I would buy it. I do better with training books than online searching, so a book would be helpful."
"We have had a lot of people working from home who can't always connect to the JAMS server. We use VPN, as most companies do, and we have it set up so that everybody can access the JAMS server. But many times, our people cannot access it... JAMS could do a better job of telling you what the problem is when you try to log in to the server."
"One issue which can prevent jobs from running is when a script gets into a loop."
"Since Broadcom acquired this product, the technical support has not been as good. They should really be faster and more knowledgeable."
"The reliability issues need to be resolved."
"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."
"Some of the reports are either a bit hard to understand or don’t give you what you might expect to see."
"The job flow could use a little more improvement."
"There is a difference between a web interface and the thick client interface. We particularly like a thick client interface, and it has gone away."
"We see improvement possibilities in the processing provision of predefined evaluations or individual objects, or in the Self Service portal, which can be used by any user to monitor objects or start objects."
"I'd like to see automation pushed even further, giving us greater looks into other systems."
"Setup took about one day. We had some errors to understand in the beginning, but now everything is working good."
"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 wasn't easy to understand the licensing model. It's like if you use just a little, it's cheap, but it becomes more expensive as you use more. It's like a hook that ties you inside the Amazon ecosystem. So, it creates a dependency."
"If AWS Step Functions keeps adding more integrations, it would be even better."
"The price and support are areas with shortcomings where the solution needs to improve."
"The pricing of the solution can be improved."
"It is hard to coordinate the declaratory language."
 

Pricing and Cost Advice

"JAMS is close to the lower end of the pricing models for enterprise scheduling solutions. They are much cheaper than Control-M, as well as some other products that I've used. I also don't know of another solution where you can actually get true, unlimited licensing, where you can have as many instances and as many agents as you want."
"In the end, you'll find that it's really worth the price. There is some sticker shock, but it's worth every dime."
"It's expensive, to be honest, but it does the job."
"There are no additional costs other than the license for Fortra's JAMS which is affordable."
"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."
"The product is reasonably priced, and we don't have any add-ons."
"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."
"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."
"The pricing needs to be improved. Some of my client's complained that it was too expensive."
"Validate how many agents you need beforehand."
"It is overpriced."
"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."
"I certainly think the pricing is worth the value."
"The return on investment would be very high because doing things manually without this product would be extremely expensive."
"CA pricing has been a problem, and not looked upon favorably here at all."
"The price of this solution is reasonable and there is an annual license required."
"The solution's price is reasonable."
"The solution is expensive."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
913,806 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Construction Company
11%
Comms Service Provider
10%
Manufacturing Company
9%
Financial Services Firm
33%
Outsourcing Company
9%
Manufacturing Company
7%
Insurance Company
4%
Financial Services Firm
21%
Manufacturing Company
9%
Comms Service Provider
7%
Insurance Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business15
Midsize Enterprise16
Large Enterprise23
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise5
Large Enterprise79
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise2
Large Enterprise6
 

Questions from the Community

What is your experience regarding pricing and costs for JAMS?
I was not really involved in the pricing, setup cost, and licensing at that level. I am more involved in the technica...
What needs improvement with JAMS?
In terms of improvements, I believe JAMS can enhance its user interface for better user experiences. I would like to ...
What is your primary use case for JAMS?
My primary use case for JAMS is enterprise workload automation and batch job orchestration. I use it to schedule and ...
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 needs improvement with AutoSys Workload Automation?
There are areas of AutoSys Workload Automation that have room for improvement. They are implementing good enhancement...
What is your primary use case for Amazon Step Functions?
My main use case for AWS Step Functions is in our data platform where we are trying to generate alerts. For generatin...
What advice do you have for others considering Amazon Step Functions?
I rate AWS Step Functions a nine out of ten on a scale of one to ten. I chose a nine out of ten because it is basical...
What is your experience regarding pricing and costs for Amazon Step Functions?
AWS Step Functions helps us save costs as it is a self-managed service and is serverless. We look out for the inbuilt...
 

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: September 2026.
913,806 professionals have used our research since 2012.