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
41
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
37
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

"JAMS has improved our productivity immensely because everything flows. I don't think we could operate at our current staffing levels without it."
"What my team needs are tools to reliably execute all the jobs, minimize the risks, and support high-availability, and JAMS does the job."
"The most valuable aspect of JAMS is its robustness."
"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."
"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."
"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."
"While I appreciate the other features, the agent stands out for its ease of installation and configuration for JAMS monitoring."
"I find the historical tracking feature of JAMS invaluable for reviewing past events."
"The breakthrough for us was when we were able to take completely different software tools and integrate them into one long flow of data."
"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."
"It can connect to a number of third-party/legacy systems."
"Easy to configure and simple to develop new features."
"It has helped with scheduling complex jobs with simple scripts."
"As far as centralization goes it's nice because we can see all these processes that are tied to this larger process. The commissions, FTP processing, the reporting, the file moves to the business users — all that is right there. It's very easy to read. It's easy to tie it together, visually, and see where each of these steps fits into the bigger picture."
"ActiveBatch helped us automate and schedule routine tasks such as data backups, file transfers, database updates, and report generation, which frees IT staff to focus on other studies."
"Since we are no longer waiting for an operator to see that a job is finished, we have changed our daily cycle from running in eight hours down to about five. We had a third shift-operator retire and that position was never refilled."
"CA7 is very robust and one of CA's legacy products."
"The most valuable feature of this solution is the functions are easy to use."
"We get better reports than we use to have."
"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."
"Inherit Dependencies feature reduces scheduling errors for holiday processing."
"It gives a real-time view of all the batch processing that we have, monitoring-wise it is really good, and it also gives us the ability to connect different software processes."
"The most valuable feature is the ease of coding up schedules to run jobs in both the mainframe and distributed environments."
"I prefer AutoSys over the other ones out there for ease of use, ease of understanding, and getting people to understand how the tool works."
 

Cons

"Fortra is getting much better with documentation and examples, but there is still room for improvement."
"All my machines at work are Macs. JAMS client is a Windows-based thing. It is all built on .NET, which makes perfect sense. However, that means in order for me to access it, I need to connect to a VPN, then log onto one of our Azure VMs in order to access the JAMS client. This is fine, but if for some reason I am unable to do so, it would be nice to be able to have a web-based JAMS client that has all the exact same functionality in it. There are probably a whole bunch of disadvantages that you would get with that as well, but that is definitely something that would make life easier in a few cases."
"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."
"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."
"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."
"It is important to receive notifications if a charged job fails and SQL is halted. JAMS does not provide halted notifications by default, which is a critical feature that needs to be added."
"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."
"The product does not allow the users to cut and paste the job names from the screen."
"One thing I've noticed is that navigation can be difficult unless you are familiar with the structure that we have in place."
"The only thing is that it does have a little bit of a learning curve because it is fairly complex."
"Except for the GUI, everything looks good."
"ActiveBatch is a little complex."
"An area for improvement in ActiveBatch Workload Automation is its interface or GUI. It could be a little better."
"I can't get the cleaning up of logs to work consistently. Right now, we are not setup correctly, and maybe it is something that I have not effectively communicated to them."
"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."
"Some improvements can be made to the user interface."
"I would like to see the Service Orchestrator, a B2B product, and maybe a process audit."
"Ease of implementation for upgrades."
"AutoSys Workload Automation could improve in the Linux environment."
"Pricing model for distributed should have an Enterprise option."
"We've had stability problems with the tool."
"I would like to see two-factor authentication, since you see a lot of companies in the news for security breaches. That is a really big thing for us."
"We would like to see good improvement on the historical reporting capabilities."
"When we started the new product and we introduced it, we started getting some new alarm types and the agent went offline."
 

Pricing and Cost Advice

"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."
"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."
"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."
"The pricing is very fair. We have seen very minimal to no price increases over the years. We are not banging down the door of support all the time either. I would imagine if we were a company that submitted a dozen support tickets a week for the last nine years, then it might be a little different because we would be eating up everybody's time. However, for what we get out of it, the pricing is extremely fair. Back when we were originally looking and brought in JAMS, we were looking at a couple of the other competitive products that were in this space, but the pricing from JAMS was far and away better than what the other competitors could offer for the same functionality."
"The pricing of JAMS has not been an issue for us, as it has allowed us to save time."
"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."
"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."
"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."
"It allows for lower operational overhead."
"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."
"If you compare ActiveBatch licensing to Control-M, you're looking at $50,000 as opposed to millions."
"The price of this solution is reasonable and there is an annual license required."
"There is an annual license to use AutoSys Workload Automation."
"Validate how many agents you need beforehand."
"The return on investment would be very high because doing things manually without this product would be extremely expensive."
"It is overpriced."
"I certainly think the pricing is worth the value."
"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 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."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
892,646 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
12%
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 Enterprise10
Large Enterprise20
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise13
Large Enterprise47
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise5
Large Enterprise77
 

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.
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.
892,646 professionals have used our research since 2012.