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

ActiveBatch by Redwood vs AutoSys Workload Automation comparison

Sponsored
 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 29, 2026

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
ActiveBatch by Redwood
Ranking in Workload Automation
14th
Average Rating
9.2
Reviews Sentiment
7.3
Number of Reviews
38
Ranking in other categories
Process Automation (22nd), Managed File Transfer (MFT) (14th)
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
 

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 ActiveBatch by Redwood is 3.1%, up from 2.4% compared to the previous year. The mindshare of AutoSys Workload Automation is 7.0%, down from 12.2% 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%
ActiveBatch by Redwood3.1%
Other86.9%
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.
AS
Application Administrator Lead at Bluestem
Manages thousands of jobs daily and reduces downtime through secondary node support
The current feedback I receive from my end users regarding ActiveBatch by Redwood highlights issues with the tabs or panes during job modification. When the next user monitors it, they need to close the pane or job and reopen it to see the changes reflected. If the end user makes an update, it will not be visible unless they start from the beginning again. Implementing a refresh button would be helpful for real-time updates when the end user needs to see changes immediately. We currently face issues with the web console of ActiveBatch by Redwood. When users operate through an RDP session, every user has their own ActiveBatch by Redwood application. However, on the web console, users encounter daily activity issues where the job instances do not appear or update correctly, and they cannot view the latest logs. This issue is only present on the web console, as the application itself works without any problems. ActiveBatch by Redwood can be improved by adding more features, as we are not currently handling cloud-based applications like S3 buckets and Azure. Connecting to these cloud platforms would be a helpful enhancement.
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.

Quotes from Members

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

Pros

"The ability to sequence jobs is excellent; it means we don't have to schedule them individually, and if one fails, it doesn't unwind the entire workflow."
"Previously, we manually managed file transfers by writing our scripts. The automated MFT feature is great for me and the company. It helps us know where the files are going and enables us to track errors if anything fails. It also makes the connection seamless for third-party vendors."
"The user-friendly and adaptable scheduler allows us to manage various scheduling scenarios."
"The overall product is fantastic. I love it. It has been a fantastic, solid product. If I have one tiny bit of a problem with it, the support team gets in touch with me right away. I don't know if I've had another service that has been as fantastic as the JAMS support team."
"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 product is easy to use."
"We also use the solution’s Interactive Agents. If we need to push something to our dealer portal, we can just drop a file in a folder and it goes. Running interactive tasks helps me users focus on business processes since I don’t have to take care of running the jobs manually."
"Our company is based on data. Everything we do is data-driven, so it has been very valuable having one place where we can process all of the data and do batch schedules with chunks of data."
"We are able to integrate it into multiple third-party tools like email, backup, tracking systems, SharePoint, Slack alerts, etc."
"Using ActiveBatch I have learned that the potential for reducing costs using an automation tool is huge, and that when the business becomes aware of it they really embrace the product."
"The product offers a centralized platform for managing activities across many environments, applications, etc."
"I found ActiveBatch Workload Automation to be a very good scheduling tool. What I like best about it is that it has very less downtime when managing many complex scheduling workflows, so I'm very impressed with ActiveBatch Workload Automation."
"The software offers real-time monitoring and reporting features that let IT teams keep tabs on the progress of their batch operations and workflows."
"It has improved our workflow completion rates by five hours per day, because we execute our workflows daily."
"The automation feature is a very valuable feature as the associates do not have to worry about performing repetitive tasks (i.e. endpoint security scans on a daily basis) that would take several hours to complete on a daily basis."
"Since I started using this product, I have been able to easily track everything as it mainly monitors, alerts, and looks after all the services - even across platform scheduling - which has helped me immensely."
"It allows you to automate tasks, and reduce headcount, prevent errors, self-heal, self-service type technologies."
"Now that we've got it and had it, it's very easy to use."
"We really like the product and its functions; it works, and we like its stability, scalability, and robustness."
"From an orchestrator perspective, it simplifies your workflow and job flow."
"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."
"The aggregator reporting utility which tells us our throughput in lag and latency."
"We did not have the visibility of the distributed jobs until we used ESP Workload automation and we can now schedule them together with our mainframe jobs."
"It's a dynamic product, it's been stable and we've never had a real outage with the product."
 

Cons

"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."
"The solution is good, it's reliable. But sometimes the UI is not the most responsive I've ever used."
"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."
"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."
"JAMS doesn't allow us to implement SOC controls. We are a company that trades stocks on the New York Stock Exchange, so all our transactions are audited. It has a feature that saves the file for only a month but doesn't segregate the data between finance and SOC-related compliance."
"The ACL or access permission area needs to be improved. When it comes to defining and providing security permissions, it's a bit confusing if you are new to JAMS. JAMS needs to improve the features for security access or permissions."
"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."
"It could be easier to provide dashboards on how many jobs are running at the same time; more monitoring."
"An area for improvement in ActiveBatch Workload Automation is its interface or GUI. It could be a little better."
"ActiveBatch is a little complex."
"There are some issues with this version and finding the jobs that it ran. If you're looking at 1,000 different jobs, it shows based on the execution time, not necessarily the run time."
"There are very few documents that provide us with detailed information on the troubleshooting of errors that occur during integration with the existing environment."
"It does have a little bit of a learning curve because it is fairly complex. You have to learn how it does things. I don't know if it's any worse than any other tool would be, just because of the nature of what it does... the learning curve is the hardest part."
"The thing I've noticed the most is the Help function. It's very difficult, at times, to find examples of how to do something."
"The interface is not that user-friendly and is a little tough to navigate."
"The cross-platform arena, where you can run work on multiple platforms, needs improvement."
"The reporting system, currently, could be better."
"We had a few issues, however, the issues were more on the infrastructure rather than with the application itself."
"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."
"Needs better documentation with fully explained examples for some of the job types."
"Initial setup is complex. It requires technical skills in various flavors of distributed/enterprise H/W, S/W, databases to implement, configure and develop high-availability options."
"This product needs to improve its graphical user interface."
"They can be a little complex. It's just a big complex product that takes a lot of evaluation."
 

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."
"This is a good product at a fair price."
"The pricing is reasonable."
"I haven't been involved in the financial side for several years, but we buy one host and unlimited agents, and we get a reasonable price for that. We're happy with the amount we pay and the scalability it provides."
"Our licensing is pretty cheap because we have a state solution. So, we pay only $1,000 a year."
"Take advantage of its scalability. You can start small. The initial cost is very reasonable. Once you have started picking up the tool and adopting it, then you can scale up from there and buy more agents."
"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."
"If you compare ActiveBatch licensing to Control-M, you're looking at $50,000 as opposed to millions."
"It allows for lower operational overhead."
"ActiveBatch is currently redesigning themselves. In the past, they were a low cost solution for automation. They had a nice tool that was very inexpensive. With their five-year plan, they will be more enhancement-driven, so they're trying to improve their software, customer service, and the way that their customers get information from them. In doing that, they're raising the price of their base system. They changed from one pricing model to another, which has caused some friction between ActiveBatch and us. We're working through that right now with them. That's one of the reasons why we're why we were evaluating other software packages."
"I like ActiveBatch Workload Automation's licensing model because they're not holding you down on an agentless model or agent model, where every server needs to have an agent. That's the main selling point of the solution and I hope they stay that way."
"The price was fairly in line with other automation tools. I don't think it's exorbitantly expensive, relatively speaking."
"I don't think we've ever had a problem with the pricing or licensing. Even the maintenance fees are very much in line. They are not excessive. I think for the support that you get, you get a good value for your money. It's the best value on the market."
"The pricing was fair. There are additional costs for the plugins. We have the standard licensing fees for different pieces, then we have the plugins which were add-ons. However, we expected that."
"Currently, we are paying approximately $7,000 yearly, which includes support."
"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."
"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."
"I certainly think the pricing is worth the value."
"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."
"Validate how many agents you need beforehand."
"CA pricing has been a problem, and not looked upon favorably here at all."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
895,272 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
11%
Construction Company
7%
Manufacturing Company
7%
Performing Arts
7%
Financial Services Firm
39%
Manufacturing Company
9%
Insurance Company
5%
Retailer
5%
 

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 Business11
Midsize Enterprise13
Large Enterprise48
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise5
Large Enterprise79
 

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...
What is your experience regarding pricing and costs for ActiveBatch Workload Automation?
My experience with pricing, setup cost, and licensing for ActiveBatch by Redwood has been great; we recently renewed ...
What needs improvement with ActiveBatch Workload Automation?
I believe ActiveBatch by Redwood could be improved because the UI could be modernized.
What is your primary use case for ActiveBatch Workload Automation?
My main use case for ActiveBatch by Redwood is file processing. I use ActiveBatch by Redwood for file processing for ...
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...
 

Also Known As

No data available
ActiveBatch
CA Workload Automation, CA Workload Automation AE
 

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
Informatica, D&H, ACES, PrimeSource, Sub-Zero Group, SThree, Lamar Advertising, Subway, Xcel Energy, Ignite Technologies, Whataburger, Jyske Bank, Omaha Children's Hospital
Gaumont, Mercantil do Brasil, CCEE, Hanwha Life
Find out what your peers are saying about ActiveBatch by Redwood vs. AutoSys Workload Automation and other solutions. Updated: April 2026.
895,272 professionals have used our research since 2012.