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

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.6
Number of Reviews
43
Ranking in other categories
No ranking in other categories
AutoSys Workload Automation
Ranking in Workload Automation
4th
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
10th
Average Rating
8.4
Reviews Sentiment
6.7
Number of Reviews
14
Ranking in other categories
Business Process Management (BPM) (12th)
 

Mindshare comparison

As of May 2026, in the Workload Automation category, the mindshare of JAMS is 3.0%, up from 1.9% compared to the previous year. The mindshare of AutoSys Workload Automation is 7.0%, down from 12.2% compared to the previous year. The mindshare of AWS Step Functions is 1.9%, up from 1.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation Mindshare Distribution
ProductMindshare (%)
JAMS3.0%
AutoSys Workload Automation7.0%
AWS Step Functions1.9%
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.
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

"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."
"The alerting in it is really targeted... you can set specific alerting so that if jobs in a given folder fail, certain people are alerted. You can also set security at the folder level, so that only people in those areas can go set them. That means that the alerting and security can be set at a very granular level."
"I like how you can add new execution methods on the fly. It isn't overly complex to add Python script support to an execution method in the JAMS system. The scheduling is excellent. You can schedule a maintenance window and take that resource unit out of everything. It halts all of the jobs."
"Fortra's JAMS helped us centralize job management across our platforms and applications. This is critical because we schedule tasks across multiple applications and operating systems, using triggers and start dates to coordinate their execution."
"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."
"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's a full-featured job scheduling tool. The part that I liked the best was the support team. This tool was new, and we were all learning it and setting up the different jobs that were complex in nature. Their support team was very responsive in helping us out through the setup and resolving the issues. They have been incredibly awesome."
"JAMS has been a beneficial monitoring tool for our project in terms of being able to deliver data that is essential for users."
"The benefits I have seen from AutoSys Workload Automation are significant; I would say it is about ease of administration."
"The customized views that each individual can create, and views that can be made free-form, makes this very popular with the programmers."
"It's very stable, it's highly redundant, it's very recoverable within the batch work, and it's easy to use."
"From an orchestrator perspective, it simplifies your workflow and job flow."
"There are certain batch jobs that need to run on a regular basis in order for our customers to receive reports and updates, and CA-7 provides that for us."
"Its stability and reliability, that it's been there for 20 years and 30 years, and it's always been the number one scheduler."
"It's a dynamic product, it's been stable and we've never had a real outage with the product."
"The initial setup is easy."
"Overall, I would rate AWS Step Functions at least nine out of ten."
"The integration capability is easy, whereas building state machines is tricky."
"AWS Step Functions offers advanced workflows that save time and enhance efficiency by reducing delays and ensuring consistent orchestration among various services."
"It has enabled my organization to create workflows with a lot of different AWS services; it's a general solution that you can adapt to your own needs and is simple to use."
"It is a scalable solution."
"One can rate all the calls and that is a good feature."
"The JSON app launched recently allows us to define data execution more easily."
"It's Amazon, it's scalable."
 

Cons

"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."
"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."
"JAMS handles exceptions fairly well but there are some areas where it might improve a little bit. It has to do with being able to automatically handle exceptions, out-of-the-box, rather than having to code them."
"Right now there's not much of an Azure integration with JAMS at the moment directly because we run separate pipelines."
"There could be a better simulation for banning the termination. You have to simulate every one of the processes in order to have an idea for better planning. This kind of simulation is broken and needs improvement."
"JAMS notifications for hung jobs could be improved."
"With no programming experience, I find JAMS code-driven automation challenging due to the required PowerShell scripting."
"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."
"Since Broadcom acquired this product, the technical support has not been as good. They should really be faster and more knowledgeable."
"We would like to see good improvement on the historical reporting capabilities."
"Deploying those solutions and integrating with them was a little challenge at this point of time."
"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."
"I am not sure whether it is our limitation or a tool limitation because we haven't yet explored it, but whenever we look for different types of reporting, we have some limitations in getting those. It could be because of the way we have set it up internally in our enterprise, but it would be helpful if we can customize the reporting features and some of the alerts that can go out. When we connect enterprise systems, each one looks for a different use case, and if we can get different types of reporting, it will be helpful."
"We are trying to see if we can use this from a cloud perspective with AWS, Azure, and other clouds, but it seems that there is no cloud integration in this product. We would like to see cloud integration. We are very pleased with this solution, but we are moving our application to the cloud, and we found out that it doesn't support any cloud features. So, we are trying to find a replacement."
"The WCC could be improved."
"I'd like to see automation pushed even further, giving us greater looks into other systems."
"The price and support are areas with shortcomings where the solution needs to improve."
"The interface can sometimes feel limited, as we're unable to see what AWS is running behind the scenes."
"I would like to see more data transformation features in Amazon Step Functions like additional operators and logic."
"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."
"It is difficult to suggest improvements at the moment."
"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."
"If AWS Step Functions keeps adding more integrations, it would be even better."
"The solution's pricing could be cheaper. It is cheaper than Airflow."
 

Pricing and Cost Advice

"The product is reasonably priced, and we don't have any add-ons."
"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 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."
"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."
"Fortra's JAMS pricing structure has deteriorated significantly since its acquisition by Fortra."
"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."
"There are no additional costs other than the license for Fortra's JAMS which is affordable."
"We paid to use the solution monthly."
"I don't have information on the exact licensing cost of AutoSys Workload Automation because that's managed by the tools and financing teams. For agents, it's close to $4,00, but for the server setup, it's usually a one-time license initially, and it's AMC which is paid every year and comes close to $8,000 to $10,000."
"It is overpriced."
"The price of this solution is reasonable and there is an annual license required."
"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."
"Validate how many agents you need beforehand."
"There is an annual license to use AutoSys Workload Automation."
"The pricing needs to be improved. Some of my client's complained that it was too expensive."
"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.
894,830 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Construction Company
12%
Manufacturing Company
8%
Healthcare Company
6%
Financial Services Firm
39%
Manufacturing Company
9%
Insurance Company
5%
Retailer
5%
Financial Services Firm
26%
Manufacturing Company
10%
Insurance Company
7%
Computer Software Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise14
Large Enterprise19
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise5
Large Enterprise79
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise2
Large Enterprise5
 

Questions from the Community

What is your experience regarding pricing and costs for JAMS?
I believe the pricing and licensing were fair. I was not here when that process took place and do not know exactly, b...
What needs improvement with JAMS?
When it comes to improvements for JAMS, I think upgrading and migrating some of the current processes could benefit f...
What is your primary use case for JAMS?
Our main use case for JAMS is to automate our data pump backups for our PeopleSoft Oracle system, as well as run a my...
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 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: April 2026.
894,830 professionals have used our research since 2012.