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

"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."
"While I appreciate the other features, the agent stands out for its ease of installation and configuration for JAMS monitoring."
"By using JAMS, my company has seen benefits such as getting to know about Google products and the latest features that are newly launched by Google, and they help me in building my projects portfolio and engaging with knowledge."
"Because we have gone from a lot of manual processes to automated processes with JAMS, we have been able to free up IT staff time, and for just the Technical Operations Center team that I manage, it has saved about 20 hours a week."
"The most valuable feature is the easily accessible data in the database because we run a lot of SQL scripting against the database."
"In summary, this product is top class."
"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."
"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."
"This is a very good tool and I'm really missing it in my new company because I don't have a robust enterprise-wide scheduling tool and a really good tool for automating end-to-end."
"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."
"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."
"We look at different products and this is definitely a very good one."
"ActiveBatch has allowed us to move forward quickly with our modernization effort, to get off of the mainframe and to move that data to a distributed environment."
"One of the most valuable features is the job templates. If we need to create an FTP job, we just drag over the FTP template and fill out the requirements using the variables that ActiveBatch uses. And that makes it reusable. We can create a job once but use it for many different clients."
"The most valuable feature is its stability. We've only had very minor issues and generally they have happened because someone has applied a patch on a Windows operating system and it has caused some grief. We've actually been able to resolve those issues quite quickly with ActiveBatch. In all the time that I've had use of ActiveBatch, it hasn't failed completely once. Uptime is almost 100 percent."
"ActiveBatch by Redwood has positively impacted our organization because we are able to process files very effectively."
"It has improved our organization by automating processes in a centralized platform, making us more productive and enabling us to provide better value to the business."
"The flexibility in solving job scheduling challenges allows us to successfully integrate an acquired business’ fiscal close with our own, even though there is a lot of variance as to when they run in the calendar month."
"Automic Automation Engine provides us the ability to map logic using a scripting language."
"Easy configuration and integration with SAP."
"The actual scheduling of our jobs has helped us tremendously. Before it was all done manually, and we've totally automated the whole functionality, so there's no longer a case where somebody didn't run something."
"AutoSys significantly reduces manual effort."
"The capabilities of the product to schedule on multiple platforms, multiple operating systems."
"The most valuable feature is the ease of coding up schedules to run jobs in both the mainframe and distributed environments."
 

Cons

"The documentation is not super... It's not as quick and slick as I'd like it to be."
"The solution is good, it's reliable. But sometimes the UI is not the most responsive I've ever used."
"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."
"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."
"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."
"All my machines at work are Macs. JAMS client is a Windows-based thing."
"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 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."
"The technical support was difficult if you wanted to escalate the issue, it takes a little bit longer to escalate."
"Whenever there is an overload, we are seeing crashes happening."
"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."
"Some improvements can be made to the user interface."
"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."
"ActiveBatch is a little complex."
"A nice thing to have would be the ability to comfortably pass variables from one job to another. That was one of the things that I found difficult."
"A cloud option is not provided as a free feature, making it a costly solution for smaller organizations."
"Some support issues need to be addressed, but not through email, through personal contact via phone or WebEx."
"The lack of documentation, that is an issue. When we do need to bring it down for maintenance, it is always a scary moment for us because we have never had it crash."
"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."
"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."
"Upgrades to the GUI interface would be probably one of the biggest things they could do to improve."
"A couple of key features would be really being able to support a scheduler that, instead of a centralized scheduler, maybe a distributed one, so where a scheduler doesn't come down; not everything stops all at one time and so on."
"I think the interface could be unified in a better way."
"Analytics seems to be a problem, so a couple of stars deducted for that, but it's probably one of the easiest tools that I manage."
 

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."
"JAMS is relatively inexpensive, with additional costs only incurred for tags, other services, and optional support renewals."
"This is a good product at a fair price."
"Our licensing is pretty cheap because we have a state solution. So, we pay only $1,000 a year."
"The pricing is reasonable."
"The product is reasonably priced, and we don't have any add-ons."
"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."
"For what it does, the product is priced very well."
"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."
"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."
"Currently, we are paying approximately $7,000 yearly, which includes support."
"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."
"If you compare ActiveBatch licensing to Control-M, you're looking at $50,000 as opposed to millions."
"It is overpriced."
"CA pricing has been a problem, and not looked upon favorably here at all."
"We paid to use the solution monthly."
"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 price of this solution is reasonable and there is an annual license required."
"I certainly think the pricing is worth the value."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
892,943 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%
Retailer
5%
Insurance Company
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise11
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?
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.
892,943 professionals have used our research since 2012.