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 key benefits about JAMS is having the ability to run long running jobs on-premise as compared to products like Azure Data Factory."
"JAMS offers diverse scheduling capabilities for any kind of job, including Linux, PowerShell scripts, and SQL, enabling automation of jobs, which has proven beautiful after three years of usage."
"Previously, we manually managed file transfers by writing our scripts. The automated MFT feature is great for me and the company. It helps us know where the files are going and enables us to track errors if anything fails. It also makes the connection seamless for third-party vendors."
"Our company is based on data. Everything we do is data-driven, so it has been very valuable having one place where we can process all of the data and do batch schedules with chunks of data."
"The most valuable feature of JAMS is its user-friendly interface, especially after upgrading from version six to seven."
"The code-driven automation for more complex scheduling requirements frees up time because it's really easy to use... It's almost like a stand-alone software that we can't live without."
"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."
"We see ActiveBatch as the Center of Excellence for all things related to automation for our business."
"The nice thing about ActiveBatch is once we have created a specific job that can be easily be replicated to another job, then minimal changes will have to be made. This makes things nice. Reduction of coding is substantial in a lot of cases. The replication of one job to another is just doing a few minor tweaks and rolling it into production. This decreases our development costs substantially."
"I found ActiveBatch Workload Automation to be a very good scheduling tool, and what I like best about it is that it has very less downtime when managing many complex scheduling workflows, so I'm very impressed with ActiveBatch Workload Automation."
"This is a very good tool and I'm really missing it in my new company because I don't have a robust enterprise-wide scheduling tool and a really good tool for automating end-to-end."
"ActiveBatch provides summary reports and logs for further analysis and improvements in monitoring servers, which is very handy."
"The most valuable feature is its stability. We've only had very minor issues and generally they have happened because someone has applied a patch on a Windows operating system and it has caused some grief. We've actually been able to resolve those issues quite quickly with ActiveBatch. In all the time that I've had use of ActiveBatch, it hasn't failed completely once. Uptime is almost 100 percent."
"ActiveBatch by Redwood has many best features that allow me to define a process, a step of the process, and how to interconnect them, making automation easy and providing complete visibility on the entire process."
"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 features in AutoSys Workload Automation are its scalability and robustness; it can process a significant amount of jobs within a short period without delays when supported by powerful infrastructure and can communicate with endless agents and scan all 10,000 agent machines within minutes, updating agent statuses in the database quickly."
"We automate recurring processes, keeping track of IT processes controlled worldwide."
"It's very stable, it's highly redundant, it's very recoverable within the batch work, and it's easy to use."
"​It scales very well. We can add jobs and remove jobs. We do not have problems maintaining the product across multiple environments and multiple servers.​"
"We definitely can count on it being up all the time."
"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."
"We’ve never had any issues; we run over 300,000 jobs a day and we have thousands of end users, at least 10,000 who can evaluate their flows and manage schedules."
"Virtual machine usage: It helped us to schedule the job to run on multiple servers based on the workload."
 

Cons

"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."
"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."
"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."
"I would like to see the ability to interface with Microsoft group-managed service accounts, but they're still in the research phase. They need to ensure everything's legit and safe. The report designer and dashboards could also be improved. We're running 7.3, so I don't know if they have updated the reporting in 7.5, but I think the reports and dashboards could be better."
"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."
"We have had a lot of people working from home who can't always connect to the JAMS server. We use VPN, as most companies do, and we have it set up so that everybody can access the JAMS server. But many times, our people cannot access it... JAMS could do a better job of telling you what the problem is when you try to log in to the server."
"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 error messages from JAMS often need clarification, hindering our ability to resolve issues swiftly."
"One way ActiveBatch by Redwood can be improved is through a more intuitive user interface for new users."
"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."
"ActiveBatch is a little complex."
"We haven't explored the cloud aspect of the solution because it's very costly."
"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."
"ActiveBatch UI could use a little more help, and video tutorials would be greatly appreciated for user guides."
"There are very few documents that provide us with detailed information on the troubleshooting of errors that occur during integration with the existing environment."
"They could provide an easier installation guide or technical support to the organizations during the installation process."
"I am not sure whether it is our limitation or a tool limitation because we haven't yet explored it, but whenever we look for different types of reporting, we have some limitations in getting those. It could be because of the way we have set it up internally in our enterprise, but it would be helpful if we can customize the reporting features and some of the alerts that can go out. When we connect enterprise systems, each one looks for a different use case, and if we can get different types of reporting, it will be helpful."
"​The cross-platform arena, where you can run work on multiple platforms, needs improvement."
"Some of the reports are either a bit hard to understand or don’t give you what you might expect to see."
"This product needs to improve its graphical user interface."
"Some support issues need to be addressed, but not through email, through personal contact via phone or WebEx."
"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."
"They could do better supporting it. They have too many of the same type of products, so sometimes it doesn't get as much attention as it should."
"Reduce the number of operational files. This would make the job of a system programmer supporting ESP easier."
 

Pricing and Cost Advice

"Definitely check how many single processes you want to run and count them as jobs. That is how you would work out your pricing on JAMS. For example, if you're running a number of commands and you can put them all into one script and run that script, you can count that as one job."
"All licensing models are a little overpriced, but JAMS offers a good value, especially given their support response times and ability to handle unforeseen issues like the SFTP transfers. I hope to find more use cases to get a better bang for our buck."
"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."
"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 of JAMS has not been an issue for us, as it has allowed us to save time."
"JAMS is relatively inexpensive, with additional costs only incurred for tags, other services, and optional support renewals."
"JAMS is priced competitively compared to similar solutions and offers flexible licensing options to cater to user needs."
"The pricing is reasonable."
"It allows for lower operational overhead."
"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."
"Currently, we are paying approximately $7,000 yearly, which includes support."
"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."
"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."
"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 certainly think the pricing is worth the value."
"Validate how many agents you need beforehand."
"There is an annual license to use AutoSys Workload Automation."
"We paid to use the solution monthly."
"The return on investment would be very high because doing things manually without this product would be extremely expensive."
"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."
"It is overpriced."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
908,834 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%
Performing Arts
6%
Financial Services Firm
35%
Manufacturing Company
8%
Outsourcing Company
6%
Retailer
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,834 professionals have used our research since 2012.