Try our new research platform with insights from 80,000+ expert users

ActiveBatch by Redwood vs AutoSys Workload Automation comparison

Sponsored
 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 28, 2025

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.9
Number of Reviews
38
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 (26th), Managed File Transfer (MFT) (15th)
AutoSys Workload Automation
Ranking in Workload Automation
5th
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 March 2026, in the Workload Automation category, the mindshare of JAMS is 2.8%, up from 1.8% compared to the previous year. The mindshare of ActiveBatch by Redwood is 3.0%, up from 2.2% compared to the previous year. The mindshare of AutoSys Workload Automation is 7.7%, down from 14.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation Mindshare Distribution
ProductMindshare (%)
JAMS2.8%
AutoSys Workload Automation7.7%
ActiveBatch by Redwood3.0%
Other86.5%
Workload Automation
 

Featured Reviews

reviewer2770605 - PeerSpot reviewer
Cloud Engineer at a financial services firm with 501-1,000 employees
Has streamlined complex job scheduling across scripting languages while reducing manual effort
JAMS could be improved with a web client that is accessible and as fast as a normal website, eliminating the need to RDP to the servers to access the JAMS client. A functionality running on the JAMS server to continuously check the JAMS agents would ensure they are working properly. If an agent is not responding, a feature to restart the service from the job server machine would be beneficial. The upgrade process, particularly when switching from V6 to V7, could be clearer in terms of documentation, ideally with screenshots showing exactly what needs to be done on each screen.
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 dashboard is intuitive."
"The interface is good, and it's very easy to define and create jobs. If a job is not running or there is an error, the solution will send an email. That's all very good and very useful."
"The feature or capability to import a job is most valuable. We can import an existing job from different platforms, and all the configurations get migrated as well without modifying the code, job schedule, etc."
"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."
"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."
"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."
"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."
"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."
"ActiveBatch by Redwood has positively impacted my organization by efficiently managing a significant volume of data and workflow between our database and applications on the web browser."
"The REST API adapters and native integrations for integrating and orchestrating the software stack are very flexible."
"ActiveBatch by Redwood has positively impacted my organization by efficiently managing a significant volume of data and workflow between our database and applications on the web browser."
"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."
"It can connect to a number of third-party/legacy systems."
"The Jobs Library has been a tremendous asset. For the most, that's what we use. There are some outliers, but we pretty much integrate those Jobs Library steps throughout the process, whether it's REST calls, FTP processes, or file copies and moves... That has helped us to build end-to-end workflows."
"ActiveBatch provides summary reports and logs for further analysis and improvements in monitoring servers, which is very handy."
"One of the most valuable features of this solution is the versatility of the prebuilt jobs."
"It's a dynamic product, it's been stable and we've never had a real outage with the product."
"Inherit Dependencies feature reduces scheduling errors for holiday processing."
"CA7 is very robust and one of CA's legacy products."
"Granular Security enables self-service role-based access."
"It can run an object on our Windows systems or our Unix systems, and then send messages to the other system when they are complete."
"​It allows you to automate tasks, and reduce headcount, prevent errors, self-heal."
"One of the biggest strengths is the stability of the product."
"The features that I have found most valuable with AutoSys are that it is scalable, easy to use, fast, and always available. That's very important because if it's not steady then it's a real problem. So, at this point, we are satisfied with it."
 

Cons

"JAMS could be improved with a web client that is accessible and as fast as a normal website, eliminating the need to RDP to the servers to access the JAMS client."
"The biggest area with room for improvement is the area that my organization benefits the most from using JAMS, and that is in custom execution methods. I happen to have a very good C# developer. Ever since we got JAMS, he has spent a lot of time talking to JAMS developers, researching the JAMS libraries, and creating custom execution methods. He's gotten very good at it. He is now able to create them and maintain them very easily, but that knowledge was hard-won knowledge. It was difficult to come by, and if I should ever lose this developer, then I would be hard-pressed to find anyone who could create JAMS custom execution methods quite as well as he can since there really isn't all that much help, such as documentation or information, available on how to create custom execution methods."
"There could be a better simulation for banning the termination. You have to simulate every one of the processes in order to have an idea for better planning. This kind of simulation is broken and needs improvement."
"The client is horrible. Every time JAMS puts out a survey on what they can improve, I always say, "The client: When you are setting up jobs, it is quite horrible." The response has been, "Well, we are just using the Windows foundation," and I am like, "Why isn't it only your product?" We can get around it now that we know its quirks, but it is not the most user-friendly of tools out there. The UI is completely unintuitive. We had to go and open up a support ticket with JAMS just to get something back. It is not user-friendly at all."
"For scalability, I would rate it as seven because when we have a huge volume, sometimes the tool is not so responsive."
"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."
"As an admin, I would like to have a web-based GUI instead of a client application that we have to install on our PCs."
"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."
"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."
"The interface is not that user-friendly and is a little tough to navigate."
"The user interface can be improved so that it is more appealing and accessible to new users."
"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."
"The reporting needs improvement. There is a real need for the ability to generate audit reports on the fly. It needs to be a lot easier than what I can do right now. This is a major item for me."
"ActiveBatch is a little complex."
"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."
"An area for improvement in ActiveBatch Workload Automation is its interface or GUI. It could be a little better. There isn't any additional feature I'd like to see in the tool, except for the GUI, everything looks good."
"There is a difference between a web interface and the thick client interface. We particularly like a thick client interface, and it has gone away."
"Pricing model for distributed should have an Enterprise option."
"SQL server clustering is not supported."
"It needs more complex scheduling capabilities on the end points."
"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.​"
"Documentation and cross-application externals could be improved."
"I think the interface could be unified in a better way."
"This product needs to improve its graphical user interface."
 

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."
"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 pricing of JAMS has not been an issue for us, as it has allowed us to save time."
"For what it does, the product is priced very well."
"JAMS is close to the lower end of the pricing models for enterprise scheduling solutions. They are much cheaper than Control-M, as well as some other products that I've used. I also don't know of another solution where you can actually get true, unlimited licensing, where you can have as many instances and as many agents as you want."
"The product is reasonably priced, and we don't have any add-ons."
"JAMS is priced competitively compared to similar solutions and offers flexible licensing options to cater to user needs."
"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."
"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 price was fairly in line with other automation tools. I don't think it's exorbitantly expensive, relatively speaking."
"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."
"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."
"It allows for lower operational overhead."
"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."
"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."
"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."
"There is an annual license to use AutoSys Workload Automation."
"The return on investment would be very high because doing things manually without this product would be extremely expensive."
"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."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
884,873 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Manufacturing Company
10%
Computer Software Company
10%
Insurance Company
5%
Financial Services Firm
12%
Manufacturing Company
8%
Performing Arts
7%
Insurance Company
7%
Financial Services Firm
40%
Manufacturing Company
9%
Insurance Company
5%
Retailer
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business12
Midsize Enterprise8
Large Enterprise19
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 do you like most about JAMS?
I find the historical tracking feature of JAMS invaluable for reviewing past events.
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 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 do you like most about AutoSys Workload Automation?
The most valuable aspects of AutoSys Workload Automation are its performance, scalability, and ease of getting starte...
 

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: March 2026.
884,873 professionals have used our research since 2012.