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 (27th), Managed File Transfer (MFT) (14th)
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 February 2026, in the Workload Automation category, the mindshare of JAMS is 2.8%, up from 1.7% compared to the previous year. The mindshare of ActiveBatch by Redwood is 2.9%, up from 2.3% compared to the previous year. The mindshare of AutoSys Workload Automation is 8.0%, down from 14.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation Market Share Distribution
ProductMarket Share (%)
JAMS2.8%
AutoSys Workload Automation8.0%
ActiveBatch by Redwood2.9%
Other86.3%
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

"It's a full-featured job scheduling tool. The part that I liked the best was the support team. This tool was new, and we were all learning it and setting up the different jobs that were complex in nature. Their support team was very responsive in helping us out through the setup and resolving the issues. They have been incredibly awesome."
"The dashboard is intuitive."
"The most valuable feature of JAMS is its user-friendly interface, especially after upgrading from version six to seven."
"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."
"JAMS has improved my organization by taking a myriad of manual processes and allowing us to automate them. It enables our folks to focus more on tasks that require their human intelligence and their creativity and less on just mundane tasks. It increases efficiency, accuracy, and consistency."
"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 most valuable aspect of JAMS is its robustness."
"The user-friendly and adaptable scheduler allows us to manage various scheduling scenarios."
"Approximately ~20 hours of manual effort have been reduced to ~5 hours with the help of ActiveBatch."
"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."
"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."
"ActiveBatch has reduced work by providing automated workflows across several different applications."
"From a scheduling point of view, it is pretty good."
"Easy to configure and simple to develop new features."
"ActiveBatch by Redwood has positively impacted our organization because we are able to process files very effectively."
"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."
"Integration with multiple services and applications across the enterprise."
"The most valuable feature of AutoSys Workload Automation is user-friendliness. If someone has some knowledge of the tool they can use it."
"It works constantly and is pretty seamless. You do not have to open up many support tickets."
"From an orchestrator perspective, it simplifies your workflow and job flow."
"It's very easy to work with. The learning curve is not that steep."
"Autosys is one of the oldest products in the market, and it has been around for quite a long time, close to 20 to 25 years."
"Running anything in crontab, you need to put a lot of logic into it to make it work. With this product, you don't have to worry about it. You have the schedule object where you put all the dates or holidays in it, and it does it for you."
"This solution enables us to improve our daily processing times. We can do everything faster than before we used this solution."
 

Cons

"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."
"Fortra is getting much better with documentation and examples, but there is still room for improvement."
"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."
"The search capability needs to be improved because when we try to search for a job, it's hard to do."
"The product does not allow the users to cut and paste the job names from the screen."
"The documentation is not super... It's not as quick and slick as I'd like it to be."
"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."
"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."
"There is this back and forth, where ActiveBatch says, "Your Oracle people should be dealing with this," and Oracle people say, "No, we don't know anything about ActiveBatch." Then, it all falls back on me as to what happens. Nobody is taking responsibility. This is the biggest failing for ActiveBatch."
"The documentation is very limited, and it can be improved."
"The interface is not that user-friendly and is a little tough to navigate."
"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 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."
"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."
"Except for the GUI, everything looks good."
"Providing some detailed training materials could be very helpful for new users who have very limited technical information about the tool."
"Some support issues need to be addressed, but not through email, through personal contact via phone or WebEx."
"​CA installation processes are never anything but complex.​"
"There is a slow response time by tech support. Unless, you say it's severity level one. That will give you a two hour timing window for them to call you. It doesn't really happen exactly in two hours, but they try."
"Quick search feature and job analysis could be improved."
"To make it a lot more user-friendly, in order to make it so other people can use it without having to do much training with it; the more user-friendly it is, the easier it is to work with."
"AutoSys Workload Automation could improve the integration."
"AutoSys Workload Automation could improve in the Linux environment. The previous versions of the AutoSys Workload Automation let you take the profile of the user that you were using to run the tasks that you're going to automate, but in the latest versions, you can't do that, you need to make more definitions and it's a little bit difficult. It was easier in the previous versions."
"I am looking forward to more of their dashboard features. I think it would be very valuable for us to have dashboard features that could be delivered to our customers in the form of a URL, and they could refresh that URL whenever they wanted to get up to date performance metrics out of our systems."
 

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."
"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."
"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 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 pricing of JAMS has not been an issue for us, as it has allowed us to save time."
"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."
"There are no additional costs other than the license for Fortra's JAMS which is affordable."
"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."
"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."
"If you compare ActiveBatch licensing to Control-M, you're looking at $50,000 as opposed to millions."
"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."
"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 was fairly in line with other automation tools. I don't think it's exorbitantly expensive, relatively speaking."
"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."
"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."
"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 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."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
882,410 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Manufacturing Company
11%
Computer Software Company
10%
Healthcare Company
5%
Financial Services Firm
14%
Insurance Company
7%
Performing Arts
7%
Manufacturing Company
7%
Financial Services Firm
42%
Manufacturing Company
9%
Retailer
5%
Insurance Company
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business11
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?
They recently switched to subscription-based pricing, which increased. The price is fair considering the functionalit...
What needs improvement with JAMS?
As far as we are using JAMS version 6, it looks good and there is nothing major to add about it. Everything is functi...
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: January 2026.
882,410 professionals have used our research since 2012.