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.7
Number of Reviews
41
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) (11th)
 

Mindshare comparison

As of April 2026, in the Workload Automation category, the mindshare of JAMS is 2.7%, up from 1.7% compared to the previous year. The mindshare of AutoSys Workload Automation is 7.1%, down from 12.7% compared to the previous year. The mindshare of AWS Step Functions is 1.7%, up from 1.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation Mindshare Distribution
ProductMindshare (%)
JAMS2.7%
AutoSys Workload Automation7.1%
AWS Step Functions1.7%
Other88.5%
Workload Automation
 

Featured Reviews

reviewer2816949 - PeerSpot reviewer
Database Analyst / Architect at a healthcare company with 1,001-5,000 employees
Automation has streamlined complex database refreshes and centralized cross-team job scheduling
The best features JAMS offers for our team include the ability to get information emailed to us in an automated fashion based on schedules we have set up with a lot of flexibility regarding when and how we run them. We include dependencies in many of these jobs, so one setup inside of JAMS does not execute a job unless there are certain dependencies. We also utilize the aspect of JAMS that allows us to time a job; if we know a job runs within a couple of hours, we can set limitations to prevent it from becoming a run-on job. If something hangs in the network or there is an error, we use that portion of JAMS to tell the system to proceed to the next step, realizing it is running beyond the normal standard time. JAMS helps centralize the management of jobs across all our platforms and applications, which is important because we have multiple teams using it. This centralization allows us to have a single point for management and reporting, so it has been very helpful in that regard. JAMS has handled and automated complex scheduling requirements, as we have multiple systems requiring dependencies and different criteria for when something executes and how long it is allowed to execute. That automation has been extremely helpful.
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

"What my team needs are tools to reliably execute all the jobs, minimize the risks, and support high-availability, and JAMS does the job."
"We can see all the batch execution status within the tool itself, which saves money, time, and cost, allowing us to handle everything in one single tool."
"The planning capabilities are most valuable."
"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."
"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."
"JAMS has been a beneficial monitoring tool for our project in terms of being able to deliver data that is essential for users."
"Being able to create a series of chained jobs, which are basically linked jobs is 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."
"It is a lot more powerful and a lot more secure."
"The most valuable feature of AutoSys Workload Automation is batch processing."
"I believe it's a mission-critical application that is required within the company because everything requires to be scheduled."
"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."
"CA7 is very robust and one of CA's legacy products."
"It is stable, it works, and it does what it is supposed to."
"It has helped to simplify cross-dependency between MVS and Open systems jobs."
"​We run millions of jobs through it every day using it for financial transactions, banking, credit cards, PeopleSoft, payroll, etc."
"The JSON app launched recently allows us to define data execution more easily."
"What I like the most about Amazon Step Functions is how easy it is to use."
"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."
"Overall, I would rate AWS Step Functions at least nine out of ten."
"The number of historical events is great."
"One can rate all the calls and that is a good feature."
"AWS Step Functions offers advanced workflows that save time and enhance efficiency by reducing delays and ensuring consistent orchestration among various services."
"It's Amazon, it's scalable."
 

Cons

"JAMS notifications for hung jobs could be improved."
"The monitoring of the JAMS product and its performance is an area of concern for me."
"With no programming experience, I find JAMS code-driven automation challenging due to the required PowerShell scripting."
"When looking at a folder in JAMS with many jobs, it would be good to have better information in the list display of what's inside those jobs. We get some information, but other important details are missing."
"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."
"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."
"JAMS lacks source control features. Our previous solution had job control language, but JAMS doesn't. When migrating between versions, JAMS doesn't migrate all the data, like job change history, etc. Also, the scheduler doesn't have a way to make jobs invisible, so you can temporarily turn a job off if you decide not to run it today."
"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 are not ready to go to the newest release (12.0)."
"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."
"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."
"We would like to see good improvement on the historical reporting capabilities."
"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."
"The lack of documentation, that is an issue."
"The job flow could use a little more improvement."
"There is room for improvement in terms of integration with other products. It would benefit from more integration with different applications or services."
"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."
"Setup took about one day. We had some errors to understand in the beginning, but now everything is working good."
"The solution's data size limit can be improved."
"If AWS Step Functions keeps adding more integrations, it would be even better."
"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."
"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."
"Fortra's JAMS pricing structure has deteriorated significantly since its acquisition by Fortra."
"Our licensing is pretty cheap because we have a state solution. So, we pay only $1,000 a year."
"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."
"JAMS is relatively inexpensive, with additional costs only incurred for tags, other services, and optional support renewals."
"In the end, you'll find that it's really worth the price. There is some sticker shock, but it's worth every dime."
"The pricing of JAMS has not been an issue for us, as it has allowed us to save time."
"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 is overpriced."
"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 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."
"I certainly think the pricing is worth the value."
"CA pricing has been a problem, and not looked upon favorably here at all."
"Validate how many agents you need beforehand."
"We paid to use the solution monthly."
"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.
889,955 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Construction Company
13%
Manufacturing Company
8%
Computer Software Company
7%
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 Enterprise10
Large Enterprise20
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 is your experience regarding pricing and costs for JAMS?
My thoughts on the pricing of JAMS are that I won't say it is cheap, but it is cost-efficient, and that should be acc...
What needs improvement with JAMS?
An area that has room for improvement is related to the AWS RDS and database part, where they said that is in progres...
What is your primary use case for JAMS?
My use case is in batch scheduling and managing the batch jobs.
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.
889,955 professionals have used our research since 2012.