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 is easier to use and cheaper than our previous solution. The installation is more straightforward, and JAMS has a graphical user interface, so it's more accessible."
"Being able to create a series of chained jobs, which are basically linked jobs is valuable."
"The built-in triggers are great."
"We have over 50 jobs running daily to manage all the integration of our systems and we don’t have to monitor these jobs; they just run, JAMS centralizes the management of jobs in our environment, has streamlined our monitoring, saves us about four hours a week in troubleshooting time, and has helped free up about eight hours a week of IT staff time."
"I like how you can add new execution methods on the fly. It isn't overly complex to add Python script support to an execution method in the JAMS system. The scheduling is excellent. You can schedule a maintenance window and take that resource unit out of everything. It halts all of the jobs."
"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."
"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."
"Getting JAMS in place was a game changer for us back then."
"The central automation hub for scheduling and monitoring brings everything together under a single pane of glass by streamlining everything: It takes less time to run everything, it's less expensive because we no longer have the extra operator running jobs, there is less chance of an operator clicking the wrong button because we run both a test system and production system side by side, and it automatically will send an output where it needs to go in real-time."
"The software offers real-time monitoring and reporting features that let IT teams keep tabs on the progress of their batch operations and workflows."
"From a scheduling point of view, it is pretty good."
"ActiveBatch provides summary reports and logs for further analysis and improvements in monitoring servers, which is very handy."
"Using this tool, if there are any huge failures, we immediately get an email notification, and the proper team will be informed, at which time they can act accordingly."
"ActiveBatch can automate predictable, repeatable processes very well. There is no real trick to what ActiveBatch does. ActiveBatch does exactly what you would expect a scheduling piece of software to do. It does it in a timely manner and does it with very little outside interference and fanfare. It runs when it is supposed to, and I don't have to jump through a bunch of hoops to double check it."
"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."
"Error Handling is one of the best standout features of ActiveBatch."
"Scheduling workload across multiple platforms from a single point of contact and integration with ERP/ETL type platforms and products, such as Oracle and SEQUEL."
"It's a dynamic product, it's been stable and we've never had a real outage with the product."
"The CA workload agent has gotten much better. For our organization it's important for us to communicate in a secure fashion between the host and the other platforms, and we are able to do that with our CA product"
"Centralizing all this into a single workload automation tool using the CA product has really helped a lot of customers."
"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."
"It's very easy to work with. The learning curve is not that steep."
"It has been my go-to tool for 28 something years, and it has not failed me yet."
"The web UI is beneficial and the granular security policies allow us to cover all of our audit requirements."
 

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."
"For the most part, JAMS is very stable. Occasionally, if you leave multiple windows open over a period of time, it is necessary to end that task and restart."
"The documentation is not super... It's not as quick and slick as I'd like it to be."
"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 UI could be better. There were some things that were not quite intuitive, such as the search tool. When we tried to search for jobs, we had to clear the entire search and then go in and enter the new search query. That's something that wasn't intuitive for a new user."
"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."
"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 tabs in the JAMS file transfer could be clearer. It would help us demonstrate to our client that JAMS not only automates jobs but also does fast transfers, and it's an alternative that supports and filters different kinds of platforms. Filtering file transfers will be highly beneficial to them."
"Providing some detailed training materials could be very helpful for new users who have very limited technical information about the tool."
"A nice thing to have would be the ability to comfortably pass variables from one job to another."
"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."
"An area for improvement in ActiveBatch Workload Automation is its interface or GUI. It could be a little better."
"The thing I've noticed the most is the Help function. It's very difficult, at times, to find examples of how to do something. The Help function will explain what the tool does, but we're not a Windows shop at the data warehouse. Our data warehouse jobs actually run on Linux servers. Finding things for Linux-based solutions is not as easy as it is for Windows-based solutions. I would like to see more examples, and more non-Windows examples as well, in the Help."
"We haven't explored the cloud aspect of the solution because it's very costly."
"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."
"There are some issues with this version and finding the jobs that it ran. If you're looking at 1,000 different jobs, it shows based on the execution time, not necessarily the run time."
"It needs more complex scheduling capabilities on the end points."
"AutoSys Workload Automation could improve the integration."
"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."
"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."
"The installation process is complex, and is pretty archaic."
"Most AutoSys Workload Automation customers are moving because of cost; it is more cost intrusive."
"This is probably something you don't want to hear, but support seems to be getting worse over the years."
"The reliability issues need to be resolved."
 

Pricing and Cost Advice

"For what it does, the product is priced very well."
"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."
"JAMS is priced competitively compared to similar solutions and offers flexible licensing options to cater to user needs."
"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 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."
"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 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."
"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."
"It allows for lower operational overhead."
"Currently, we are paying approximately $7,000 yearly, which includes support."
"Validate how many agents you need beforehand."
"We paid to use the solution monthly."
"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."
"It is overpriced."
"CA pricing has been a problem, and not looked upon favorably here at all."
"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 return on investment would be very high because doing things manually without this product would be extremely expensive."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
892,868 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,868 professionals have used our research since 2012.