No more typing reviews! Try our Samantha, our new voice AI agent.

ActiveBatch by Redwood vs AutoSys Workload Automation comparison

Why PeerSpot?
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 Scheduler
Sponsored
Ranking in Workload Automation
3rd
Average Rating
8.8
Reviews Sentiment
6.5
Number of Reviews
46
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
41
Ranking in other categories
Process Automation (12th), Managed File Transfer (MFT) (10th)
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 September 2026, in the Workload Automation category, the mindshare of JAMS Scheduler is 3.4%, up from 2.0% compared to the previous year. The mindshare of ActiveBatch by Redwood is 3.2%, up from 2.8% compared to the previous year. The mindshare of AutoSys Workload Automation is 6.4%, down from 10.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation Mindshare Distribution
ProductMindshare (%)
JAMS Scheduler3.4%
AutoSys Workload Automation6.4%
ActiveBatch by Redwood3.2%
Other87.0%
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 key benefits about JAMS is having the ability to run long running jobs on-premise as compared to products like Azure Data Factory."
"JAMS has been a beneficial monitoring tool for our project in terms of being able to deliver data that is essential for users."
"The built-in triggers are great."
"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."
"The product is easy to use."
"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."
"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."
"JAMS has helped save IT staff time by automating tasks previously performed with scripts, and its scheduling feature has been particularly useful."
"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."
"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."
"For developers, it is easy to orchestrate the workflows and the integration has been very easy."
"ActiveBatch by Redwood has positively impacted my organization by improving efficiency through reducing manual intervention and minimizing downtime, which made operations significantly smoother."
"The user interface is really incredible."
"The product offers a centralized platform for managing activities across many environments, applications, etc."
"From a scheduling point of view, it is pretty good."
"Virtual machine usage: It helped us to schedule the job to run on multiple servers based on the workload."
"We definitely can count on it being up all the time."
"It's a dynamic product, it's been stable and we've never had a real outage with the product."
"The integration that it provides and the auditing features are the most valuable to us."
"​We run millions of jobs through it every day using it for financial transactions, banking, credit cards, PeopleSoft, payroll, etc."
"CA Workload Automation automates across multiple platforms, enables you to tie into audit systems, gives you a lot of visibility as far as workload goes, and allows you to automate it as well."
"The actual scheduling of our jobs has helped us tremendously, as before it was all done manually and we have totally automated the whole functionality, so there is no longer a case where somebody did not run something and it is 100 percent reliable."
"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."
 

Cons

"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."
"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."
"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."
"Improvements could be made in the service desk's knowledge and communication skills among engineers to better address customer needs and ensure issues are fully resolved."
"The error messages from JAMS often need clarification, hindering our ability to resolve issues swiftly."
"The monitoring of the JAMS product and its performance is an area of concern for me."
"One issue which can prevent jobs from running is when a script gets into a loop."
"One thing that I know that the JAMS people said that they were working on that would be huge for us is a search capability so that you could search for tasks. It may be available in version 7 or in a future release of 7. I think that's on their roadmap. But right now, for us to do a search, we have to search through database queries."
"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."
"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."
"Between version 10 and version 12 there was a change. In version 10, they had each object in its own folder. But on the back end, they saw it at the root level. So when we moved over to version 12, everything was in the same area mixed together. It was incredibly difficult and we actually had to create our own folders and move those objects—like schedules, jobs, user accounts—and manually put those into folders, whereas the previous version already had it."
"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."
"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."
"The monitoring dashboard could have been more user-friendly so that in the monitoring dashboard itself we can see the total number of jobs created in the system and how many were currently active/scheduled/chained."
"The technical support was difficult if you wanted to escalate the issue, it takes a little bit longer to escalate."
"When we started the new product and we introduced it, we started getting some new alarm types and the agent went offline."
"The initial setup, what we had, was called 35 then we went to a 45 version. Now we went from the 45 to what's called R11, that was a nightmare."
"We had a few issues, however, the issues were more on the infrastructure rather than with the application itself."
"CA Workload Automation is not part of CA's strategic vision going forward."
"We need the ability to be able to have Windows user passwords changed periodically and automatically."
"There should be easier migrations from a different bus scheduler."
"Performance improvements in the UI would be appreciated."
"It lacks support and integration with cloud computing platforms."
 

Pricing and Cost Advice

"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."
"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 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."
"There are no additional costs other than the license for Fortra's JAMS which is affordable."
"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 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's expensive, to be honest, but it does the job."
"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 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."
"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."
"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."
"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."
"There is an annual license to use AutoSys Workload Automation."
"CA pricing has been a problem, and not looked upon favorably here at all."
"I certainly think the pricing is worth the value."
"It is overpriced."
"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 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.
913,806 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Construction Company
11%
Comms Service Provider
10%
Manufacturing Company
9%
Outsourcing Company
11%
Financial Services Firm
11%
Construction Company
10%
Manufacturing Company
7%
Financial Services Firm
33%
Outsourcing Company
9%
Manufacturing Company
7%
Insurance Company
4%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business15
Midsize Enterprise16
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?
In terms of improvements, I believe JAMS can enhance its user interface for better user experiences. I would like to ...
What is your primary use case for JAMS?
My primary use case for JAMS is enterprise workload automation and batch job orchestration. I use it to schedule and ...
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: September 2026.
913,806 professionals have used our research since 2012.