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 ability to sequence jobs is excellent; it means we don't have to schedule them individually, and if one fails, it doesn't unwind the entire workflow."
"Being able to create a series of chained jobs, which are basically linked jobs is valuable."
"JAMS has improved our productivity immensely because everything flows. I don't think we could operate at our current staffing levels without it."
"It makes everything that we want to do so much easier. We have had a number of instances in the past where we have had developers who have been working on a project, and even though we have had JAMS for all these years, they will create some SQL Server Agent job, or something like that, to run a task. When it is in code review and development is complete, the question always comes around, "Can JAMS do this?" The answer has always been, "Yes." Pretty much anything we have ever developed could be run by JAMS."
"The most valuable aspect of JAMS is its robustness."
"The most valuable feature is the easily accessible data in the database because we run a lot of SQL scripting against the database."
"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."
"By implementing a sophisticated scheduling mechanism, the system allows for the precise triggering of jobs at user-selected frequencies, enabling a seamless and automated execution of tasks according to specified time intervals."
"I found ActiveBatch Workload Automation to be a very good scheduling tool. 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."
"We leverage the solution's native integrations regularly. We have to get files from a remote server outside the organization, and even send things outside the organization. We use a lot of its file manipulation and SFTP functionality for contacting remote servers."
"We use the main job-scheduling feature. It's the only thing we use in the tool. That's the reason we are using the tool: to reduce costs by replacing manual tasks with automated tasks and to perform regular, repetitive tasks in a more reliable way."
"It is very useful in sending confidential files through FPP servers."
"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."
"Easy to configure and simple to develop new features."
"One of the valuable features is the ability to trigger workflows, one after another, based on success, without having to worry about overlapping workflows. The ability to integrate our BI, analytics, and our data quality jobs is also valuable"
"The web UI is beneficial and the granular security policies allow us to cover all of our audit requirements."
"​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.​"
"The aggregator reporting utility which tells us our throughput in lag and latency."
"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"
"The most valuable feature of AutoSys Workload Automation is batch processing."
"​It allows you to automate tasks, and reduce headcount, prevent errors, self-heal."
"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."
"It works constantly and is pretty seamless. You do not have to open up many support tickets."
 

Cons

"JAMS notifications for hung jobs could be improved."
"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."
"The monitoring of the JAMS product and its performance is an area of concern for me."
"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."
"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."
"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."
"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."
"There are very few documents that provide us with detailed information on the troubleshooting of errors that occur during integration with the existing environment."
"Setting up the software was hard."
"ActiveBatch UI could use a little more help, and video tutorials would be greatly appreciated for user guides."
"As more organizations are moving towards a cloud-based infrastructure, ActiveBatch could incorporate more capabilities that support popular cloud platforms, such as AWS, Azure, and Google Cloud."
"It could be easier to provide dashboards on how many jobs are running at the same time; more monitoring."
"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."
"I believe ActiveBatch by Redwood could be improved because the UI could be modernized."
"Except for the GUI, everything looks good."
"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."
"​A better graphical user interface, because we have a lot of people using the client utility, and we want to get them away from that.​"
"We had a few issues, however, the issues were more on the infrastructure rather than with the application itself."
"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.​"
"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."
"Some support issues need to be addressed, but not through email, through personal contact via phone or WebEx."
"Pricing model for distributed should have an Enterprise option."
 

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."
"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."
"The pricing is reasonable."
"There are no additional costs other than the license for Fortra's JAMS which is affordable."
"The pricing of JAMS has not been an issue for us, as it has allowed us to save time."
"Our licensing is pretty cheap because we have a state solution. So, we pay only $1,000 a year."
"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."
"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 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."
"It allows for lower operational overhead."
"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."
"Currently, we are paying approximately $7,000 yearly, which includes support."
"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."
"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."
"It is overpriced."
"Validate how many agents you need beforehand."
"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."
"We paid to use the solution monthly."
"There is an annual license to use AutoSys Workload Automation."
"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."
"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."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
883,896 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Manufacturing Company
10%
Computer Software Company
10%
Healthcare Company
6%
Financial Services Firm
14%
Insurance Company
7%
Manufacturing Company
7%
Performing Arts
7%
Financial Services Firm
41%
Manufacturing Company
9%
Insurance Company
5%
Retailer
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?
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.
883,896 professionals have used our research since 2012.