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.4
Number of Reviews
45
Ranking in other categories
No ranking in other categories
ActiveBatch by Redwood
Ranking in Workload Automation
8th
Average Rating
9.0
Reviews Sentiment
7.2
Number of Reviews
42
Ranking in other categories
Process Automation (12th), Managed File Transfer (MFT) (10th)
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 August 2026, in the Workload Automation category, the mindshare of JAMS is 3.1%, up from 1.9% compared to the previous year. The mindshare of ActiveBatch by Redwood is 3.2%, up from 2.9% compared to the previous year. The mindshare of AutoSys Workload Automation is 6.6%, down from 10.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation Mindshare Distribution
ProductMindshare (%)
JAMS3.1%
AutoSys Workload Automation6.6%
ActiveBatch by Redwood3.2%
Other87.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.
Sai  - PeerSpot reviewer
Ai/Data Analyst at CSD
Automation has streamlined complex data workflows and now saves time on recurring reporting
To improve ActiveBatch by Redwood, the UI could be more modern and intuitive, and another thing that comes to mind is that it can feel overwhelming when workflows become large and complex. Troubleshooting can take extra time when there are multiple dependencies, jobs, and integrations running together. Better visualization of workflow relationships and easier debugging would really help. I would also appreciate seeing more simplified onboarding and documentation for newer users, as there is a learning curve at the beginning. Another improvement area could be smarter analytics or AI-driven recommendations, such as proactively identifying workflow bottlenecks, failed job patterns, or optimization suggestions instead of relying mostly on manual monitoring. From an operational perspective, faster configuration for integrations and cloud-based workflows would make implementation smoother, especially in environments working heavily with APIs and data pipelines. I have covered the main points regarding needed improvements. Overall, the platform is very capable and reliable for automation and workflow scheduling, especially in data-heavy environments. Most of the improvements I want are around making it easier for day-to-day use, such as a more intuitive UI, simpler troubleshooting for complex workflows, better onboarding for newer users, and more intelligent monitoring or optimization insights. The core functionality is strong, and the biggest opportunity is improving the overall user experience and simplifying operational management.
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 fact that we no longer need to use Excel spreadsheets is huge."
"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."
"Being able to create a series of chained jobs, which are basically linked jobs is valuable."
"JAMS has improved our productivity immensely because everything flows. I don't think we could operate at our current staffing levels without it."
"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."
"JAMS has helped save IT staff time by automating tasks previously performed with scripts, and its scheduling feature has been particularly useful."
"I didn't know about JAMS because I don't have a person with any challenges with the purchase administration. The feature or the user interface is user-friendly because of the readable icons or very descriptive icons. Though I'm a beginning user of JAMS, I had no issues using 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."
"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."
"One of the valuable features is the ability to trigger workflows, one after another, based on success, without having to worry about overlapping workflows. The ability to integrate our BI, analytics, and our data quality jobs is also valuable"
"We are able to integrate it into multiple third-party tools like email, backup, tracking systems, SharePoint, Slack alerts, etc."
"ActiveBatch has reduced work by providing automated workflows across several different applications."
"We see ActiveBatch as the Center of Excellence for all things related to automation for our business."
"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."
"The best feature that ActiveBatch by Redwood offers is the user interface."
"Over the years that I have used this, it has probably saved us several hundred hours of development time for other teams and my own."
"It streamlines processing really well, so we're able to cut down on our processing times."
"It has streamlined our scheduling and cut down our overall run time; not in half, but significantly."
"We get better reports than we use to have."
"It is very valuable for us when we are trying to arrange or orchestrate jobs into a system. It is helpful for triggering jobs for a scheduled task."
"From an orchestrator perspective, it simplifies your workflow and job flow."
"The most valuable feature is the ease of coding up schedules to run jobs in both the mainframe and distributed environments."
"Virtual machine usage: It helped us to schedule the job to run on multiple servers based on the workload."
"The aggregator reporting utility which tells us our throughput in lag and latency."
 

Cons

"I would enhance the compatibility feature of JAMS because sometimes when the server is under high load, it does not inform us and we cannot get answers."
"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."
"JAMS has built-in reporting. I've never really used it. I tried using it a few years ago and I couldn't figure it out. It was wonky. It could be improved upon."
"Fortra is getting much better with documentation and examples, but there is still room for improvement."
"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."
"It does validations when you try to delete an object and if there are any dependencies in place, the deletion process will not proceed... there is no information provided as to what it was that caused the validation to fail... it's quite a tedious process to find which object is getting in the way."
"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."
"All my machines at work are Macs. JAMS client is a Windows-based thing."
"The UI could potentially offer a more refined and user-friendly experience, fostering smoother interactions and facilitating easier navigation for users engaging with the application."
"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."
"One thing I've noticed is that navigation can be difficult unless you are familiar with the structure that we have in place. If someone else had to look at our ActiveBatch console and find a job, they might not know where to find it."
"We have faced a couple of issues where we were supposed to log a defect with ActiveBatch. That said, the Active batch Vendor Support is very responsive and reliable."
"Some improvements can be made to the user interface."
"Regarding improvements, I think the setup of ActiveBatch by Redwood is a bit complex, and if they could simplify this process, then it would be better."
"The interface is not that user-friendly and is a little tough to navigate."
"I have faced struggles to understand, set up the tool, and implement it in my early days as a new user."
"We have to escalate through channels to get to somebody who knows what's going on. It takes time that we do not necessarily have.​"
"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."
"We received a 'Not active. "Scan Failed"; "The 'path/file' does not exist or not a directory" error message/email on one of our event level file triggers."
"This is probably something you don't want to hear, but support seems to be getting worse over the years."
"The lack of documentation, that is an issue."
"I am looking forward to more of their dashboard features."
"This product needs to improve its graphical user interface."
"There should be easier migrations from a different bus scheduler."
 

Pricing and Cost Advice

"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."
"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."
"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 product is reasonably priced, and we don't have any add-ons."
"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 is reasonable."
"It's expensive, to be honest, but it does the job."
"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."
"It allows for lower operational overhead."
"Currently, we are paying approximately $7,000 yearly, which includes support."
"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."
"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."
"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."
"The price was fairly in line with other automation tools. I don't think it's exorbitantly expensive, relatively speaking."
"If you compare ActiveBatch licensing to Control-M, you're looking at $50,000 as opposed to millions."
"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 price of this solution is reasonable and there is an annual license required."
"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."
"Validate how many agents you need beforehand."
"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."
"The pricing needs to be improved. Some of my client's complained that it was too expensive."
"It is overpriced."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
908,800 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Construction Company
12%
Manufacturing Company
8%
Comms Service Provider
7%
Financial Services Firm
11%
Construction Company
10%
Outsourcing Company
9%
Manufacturing Company
6%
Financial Services Firm
35%
Manufacturing Company
8%
Outsourcing Company
6%
Insurance Company
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business15
Midsize Enterprise14
Large Enterprise23
By reviewers
Company SizeCount
Small Business12
Midsize Enterprise13
Large Enterprise52
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 was not really involved in the pricing, setup cost, and licensing at that level. I am more involved in the technica...
What needs improvement with JAMS?
To improve JAMS, it should resolve the issues with the JD Edwards application and the need for the SSH client connect...
What is your primary use case for JAMS?
My main use case for JAMS is to install, set up, and configure for customers working with JD Edwards application. A s...
What is your experience regarding pricing and costs for ActiveBatch Workload Automation?
I was not directly involved in the pricing, setup cost, and licensing decisions for ActiveBatch by Redwood, so my exp...
What needs improvement with ActiveBatch Workload Automation?
ActiveBatch by Redwood could be improved with a more modern and intuitive user interface, faster performance for very...
What is your primary use case for ActiveBatch Workload Automation?
My main use case for ActiveBatch by Redwood is enterprise workload automation, job scheduling, and orchestrating busi...
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: August 2026.
908,800 professionals have used our research since 2012.