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 (24th), Managed File Transfer (MFT) (15th)
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 April 2026, in the Workload Automation category, the mindshare of JAMS is 2.7%, up from 1.7% compared to the previous year. The mindshare of ActiveBatch by Redwood is 3.0%, up from 2.4% compared to the previous year. The mindshare of AutoSys Workload Automation is 7.1%, down from 12.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation Mindshare Distribution
ProductMindshare (%)
JAMS2.7%
AutoSys Workload Automation7.1%
ActiveBatch by Redwood3.0%
Other87.2%
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

"We also use the solution’s Interactive Agents. If we need to push something to our dealer portal, we can just drop a file in a folder and it goes. Running interactive tasks helps me users focus on business processes since I don’t have to take care of running the jobs manually."
"The most valuable aspect of JAMS is its robustness."
"JAMS has improved our productivity immensely because everything flows. I don't think we could operate at our current staffing levels without it."
"The scheduling and execution of jobs are the most valuable features. The scheduling is important because if there is a task we want to execute at 4:00 AM, there's no way we will have someone who can manually run the job. In addition, we execute 100 to 200 jobs per day, and manual intervention is not an option."
"The planning capabilities are most valuable."
"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 dashboard is intuitive."
"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."
"The breakthrough for us was when we were able to take completely different software tools and integrate them into one long flow of data."
"The REST API adapters and native integrations for integrating and orchestrating the software stack are very flexible."
"It has helped with scheduling complex jobs with simple scripts."
"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."
"We see ActiveBatch as the Center of Excellence for all things related to automation for our business."
"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."
"Managing the workload and monitoring the tasks were very difficult with manual interventions. Now, by using ActiveBatch, the process is automated and it runs tasks on a scheduled basis."
"We look at different products and this is definitely a very good one."
"The actual scheduling of our jobs has helped us tremendously. Before it was all done manually, and we've totally automated the whole functionality, so there's no longer a case where somebody didn't run something."
"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."
"One of the biggest strengths is the stability of the product."
"It has streamlined our scheduling and cut down our overall run time; not in half, but significantly."
"Without this product we would have to manually submit jobs and it would take longer."
"CA 7 Edition just performs its job day in, day out, with very little need to remediate any issues and has performed well for decades."
"Top-notch scheduling features and functionality Reliability, performance and stability Advanced GUI to manage the batch, flexibility to schedule jobs on various business needs"
"The flexibility of being able to schedule the timing and frequency of different automation scripts makes it easier for us to meet our customers’ business requirements."
 

Cons

"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."
"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."
"All my machines at work are Macs. JAMS client is a Windows-based thing."
"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 monitoring of the JAMS product and its performance is an area of concern for me."
"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."
"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."
"I believe ActiveBatch by Redwood could be improved because the UI could be modernized."
"They could provide an easier installation guide or technical support to the organizations during the installation process."
"The user interface can be improved so that it is more appealing and accessible to new users."
"The technical support was difficult if you wanted to escalate the issue, it takes a little bit longer to escalate."
"I have faced struggles to understand, set up the tool, and implement it in my early days as a new user."
"The help center and documentation are not that helpful."
"Between version 10 and version 12 there was a change. In version 10, they had each object in its own folder, but when we moved over to version 12, everything was in the same area mixed together and 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."
"While the console app works well, they have some crucial design flaws within the console that still need to be worked out because it is not working exactly how we hoped to see it, e.g., just some minor things where when you hit the save button, then all of a sudden all your job's library items collapse."
"A better graphical user interface. We have a lot of people using the client utility, and we want to get them away from that."
"The main push is the web UI, to be able to give it to our business users."
"The GUI/Workstation is weak and needs to be improved. CA is working on this right now."
"In terms of what should be in the next release, I want integration and AI and so on. I'd like easy reporting where you can compare information, for example, "that job normally takes three minutes and last time it took six minutes or 10 minutes." Then you can get the information to the engineer of which job is taking more time than normal - understanding strange behavior compared to the baseline."
"Because this product only computes processing days, it is hard when things need to be scheduled according to non-processing days."
"Pricing model for distributed should have an Enterprise option."
"Some support issues need to be addressed, but not through email, through personal contact via phone or WebEx."
"The most important thing is that duration is not displayed in the actual WCC GUI."
 

Pricing and Cost Advice

"This is a good product at a fair price."
"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."
"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."
"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 product is reasonably priced, and we don't have any add-ons."
"The product is reasonably priced, and we don't have any add-ons."
"It's expensive, to be honest, but it does the job."
"JAMS is priced competitively compared to similar solutions and offers flexible licensing options to cater to user needs."
"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."
"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."
"Currently, we are paying approximately $7,000 yearly, which includes support."
"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."
"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."
"There is an annual license to use AutoSys Workload Automation."
"CA pricing has been a problem, and not looked upon favorably here at all."
"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."
"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 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.
890,071 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Construction Company
13%
Manufacturing Company
8%
Computer Software Company
6%
Financial Services Firm
12%
Construction Company
7%
Manufacturing Company
7%
Performing Arts
7%
Financial Services Firm
39%
Manufacturing Company
9%
Insurance Company
5%
Retailer
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise10
Large Enterprise20
By reviewers
Company SizeCount
Small Business12
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?
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 primary use case for JAMS?
My use case is in batch scheduling and managing the batch jobs.
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.
890,071 professionals have used our research since 2012.