Try our new research platform with insights from 80,000+ expert users

AutoSys Workload Automation vs Tidal by Redwood 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.7
Number of Reviews
37
Ranking in other categories
No ranking in other categories
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
Tidal by Redwood
Ranking in Workload Automation
19th
Average Rating
9.0
Reviews Sentiment
7.2
Number of Reviews
37
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of February 2026, in the Workload Automation category, the mindshare of JAMS is 2.8%, up from 1.7% compared to the previous year. The mindshare of AutoSys Workload Automation is 8.0%, down from 14.9% compared to the previous year. The mindshare of Tidal by Redwood is 4.5%, up from 2.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation Market Share Distribution
ProductMarket Share (%)
JAMS2.8%
AutoSys Workload Automation8.0%
Tidal by Redwood4.5%
Other84.7%
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.
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.
JG
Batch Production Manager at a consultancy with 201-500 employees
Its versatility, ease of use, scalability, and cost-effectiveness make it a 10/10 and the best of the breed
The company is not really big. One of the areas that they are working on is improving the process of migrating jobs from the lower environment to the upper environment. They had used a tool called Transporter, which was a little difficult to use, but they've now released a new tool in August, which I've not yet used, to do that. It's probably called Repository or something like that, but it's a tool for migrating jobs from the lower environment to the upper environment. That's where they needed to improve, and it looks like they may have, but I haven't tried the tool yet. They can do better reporting in terms of production statistics reporting.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The alerting in it is really targeted... you can set specific alerting so that if jobs in a given folder fail, certain people are alerted. You can also set security at the folder level, so that only people in those areas can go set them. That means that the alerting and security can be set at a very granular level."
"The overall product is fantastic. I love it. It has been a fantastic, solid product. If I have one tiny bit of a problem with it, the support team gets in touch with me right away. I don't know if I've had another service that has been as fantastic as the JAMS support team."
"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."
"The product is easy to use."
"I appreciate JAMS for its readily available templates that allow me to create and deliver stand-up presentations within minutes quickly."
"The dashboard is intuitive."
"While I appreciate the other features, the agent stands out for its ease of installation and configuration for JAMS monitoring."
"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."
"The initial setup is easy."
"From an orchestrator perspective, it simplifies your workflow and job flow."
"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."
"AutoSys significantly reduces manual effort."
"It streamlines processing really well, so we're able to cut down on our processing times."
"​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.​"
"It has helped to simplify cross-dependency between MVS and Open systems jobs."
"AutoSys Workload Automation is scalable."
"The most valuable feature is the job scheduler, where you can schedule thousands of jobs to execute at specific times."
"Especially in the newer versions of Tidal, the segmentation of user permissions enables us to give people operator permissions for their jobs, to rerun jobs, but view-only for other groups' jobs. We're able to keep people from hurting themselves or other groups accidentally. The permissioning is really good."
"Tidal Automation offers extensive monitoring and reporting features that let users keep track of the status of their workflows and quickly spot any problems."
"The first, big thing that we got out of using Tidal Workload Automation was having a centralized view of the status of all of our batch processes across all these systems... We can look into the schedule at any given time and see if things are running on track or if they are falling behind. We can also see if something failed."
"We have to run about 12,000 jobs every day and the majority of them need to be launched from our ERP, JD Edwards. The native compatibility of the Tidal platform with JD Edwards dovetails with our greatest need. It's directly connected to the heart of our IT system. We couldn't work without it."
"We use the solution for cross-platform and cross-application workloads. That's one of the core reasons we chose it. It's one of a few things in the industry that can be used for cross-platform integration."
"Tidal Automation software provides real-time monitoring and alerts, allowing users to track job progress and identify potential issues before they cause delays or errors."
"The best feature is that it allows task scheduling based on particular occurrences, like the receipt of files, database updates, or system notifications."
 

Cons

"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."
"The search capability needs to be improved because when we try to search for a job, it's hard to do."
"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 error messages from JAMS often need clarification, hindering our ability to resolve issues swiftly."
"It is important to receive notifications if a charged job fails and SQL is halted. JAMS does not provide halted notifications by default, which is a critical feature that needs to be added."
"The JAMS automation code isn't so clean."
"I want JAMS to implement a global search function."
"When looking at a folder in JAMS with many jobs, it would be good to have better information in the list display of what's inside those jobs. We get some information, but other important details are missing."
"The reporting system, currently, could be better."
"AutoSys Workload Automation could improve the integration."
"Pricing model for distributed should have an Enterprise option."
"I would like to see two-factor authentication, since you see a lot of companies in the news for security breaches. That is a really big thing for us."
"Autosys is still lagging behind some competitive products from a functionality perspective."
"We had a few issues, however, the issues were more on the infrastructure rather than with the application itself."
"Some support issues need to be addressed, but not through email, through personal contact via phone or WebEx."
"There is a difference between a web interface and the thick client interface. We particularly like a thick client interface, and it has gone away."
"I know they are working on it, but there needs to be better reporting. Currently, there are only three or four reports that we can get off of the system. That needs to be improved. They already have a solution to this in the new version. I.e., a schedule of all the jobs running for one day, specifically calling out what dependencies that job relies on. It would be like a flow chart of how the day's jobs would run."
"One area for improvement is the command-line interface and the API to bulk-load jobs. It's a little bit kludgy, but we still manage without it. They're working on it and it's getting better all the time. In addition, the documentation for their API for creating jobs needs to be updated. It's a bit of a learning curve."
"Understanding and using Tidal Automation could be overwhelming for someone with minimal programming language."
"Initially, it is complicated to understand the functionalities as there is limited product documentation."
"One of the weaknesses of the product is, when something happens, it's difficult to find out the root cause. There are a lot of logs you can take a look at in Tidal. Sometimes, they are useful, but other times, they're not. That is mostly relegated to the administrative team. Users for the most part don't see that and don't know anything about that. They just know they have a problem, then it's up to the administrative team to see what happened and figure out the problem."
"One thing I would like to see improved is that, currently, when an action is executed and finishes in Tidal, it's marked as either "success" or "failure." I would like more options that would flag a job according to multiple options, rather than just "good" or bad"... Tidal has told us that it's possible to do so through the product or with a workaround."
"The GUI, the graphical user interface, gets a little bit busy."
"From an administrative point of view, I wouldn't give really high marks to the solution. I actually entertained getting the JAWS application at one point. One of the shortcomings with the scheduler is the reporting capabilities. At least at the time, JAWS was the best that they had for a third-party integration. I think they've got things in the pipeline to help alleviate that gap."
 

Pricing and Cost Advice

"The pricing is reasonable."
"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."
"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."
"It's expensive, to be honest, but it does the job."
"The product is reasonably priced, and we don't have any add-ons."
"Fortra's JAMS pricing structure has deteriorated significantly since its acquisition by Fortra."
"For what it does, the product is priced very well."
"The pricing needs to be improved. Some of my client's complained that it was too expensive."
"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."
"Validate how many agents you need beforehand."
"CA pricing has been a problem, and not looked upon favorably here at all."
"The return on investment would be very high because doing things manually without this product would be extremely expensive."
"We paid to use the solution monthly."
"I certainly think the pricing is worth the value."
"There are project, system, and server costs. Some of the things that they are doing is introducing new products. They are introducing what they call their Repository, which is a way for you to move a job. That doesn't cost anything to us, because it is reusing a tool called Transporter. The repository is the successor to Transporter, so we already own it and are sort of grandfathered in. But that new product requires a server and database, so now we have to go out and get a server and database. So, there is a cost there."
"BMC is really expensive. The other solutions are about the same price. I think Tidal is even cheaper than the others, such as CA, Stonebranch, and JAMS."
"The licensing model's flexibility is awesome. The way it's licensed for us is that it's licensed per master and then per agent. We have an enterprise agreement, so we have unlimited agents, and we have it on 500 devices."
"The solution’s licensing model in terms of its flexibility and transparency regarding costs is pretty good. A person can buy the license, and if you decide to stop support, you can do that but still have the product. So, it's not like you're paying constantly to keep that license alive. Certainly, you want to keep support going too. Once you buy it, you own it. It's not like I have to keep paying somebody to keep using it."
"The solution has no hidden costs. It helps me to plan forward into the future. I know that I can add another 100 or a thousand jobs, and that's how much it will cost me today."
"We pay maintenance annually through Blue House of about $9,000. That's for our two environments: production and test."
"Our annual maintenance cost is competitive for what we have and what they do."
"Their pricing seems very fair. It is more than the other solutions, but the functionality and the support are very much there. You pay for the job scheduler, and then they have certain things that are built into it, such as the FTP processes. If you then want to do JD Edwards jobs, you need an adapter. If you want to do SQL jobs, there is another adapter. Similarly, if you want to do Oracle jobs, there is an adapter. It is like there is the base and then there are the adapters for the jobs that you want to do, but it seems that's also how they pay for each of those adapters and keep them up to date."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
881,757 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Computer Software Company
11%
Manufacturing Company
10%
Healthcare Company
5%
Financial Services Firm
42%
Manufacturing Company
9%
Retailer
5%
Insurance Company
5%
Financial Services Firm
15%
Manufacturing Company
9%
Computer Software Company
9%
Performing Arts
8%
 

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 Business13
Midsize Enterprise5
Large Enterprise77
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise6
Large Enterprise38
 

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?
They recently switched to subscription-based pricing, which increased. The price is fair considering the functionalit...
What needs improvement with JAMS?
As far as we are using JAMS version 6, it looks good and there is nothing major to add about it. Everything is functi...
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...
Ask a question
Earn 20 points
 

Also Known As

No data available
CA Workload Automation, CA Workload Automation AE
Tidal Workload Automation, Cisco Workload Automation, Tidal Enterprise Scheduler
 

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
Gaumont, Mercantil do Brasil, CCEE, Hanwha Life
Information Not Available
Find out what your peers are saying about AutoSys Workload Automation vs. Tidal by Redwood and other solutions. Updated: January 2026.
881,757 professionals have used our research since 2012.