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.9
Number of Reviews
38
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 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 AutoSys Workload Automation is 7.7%, down from 14.2% compared to the previous year. The mindshare of Tidal by Redwood is 4.6%, up from 3.0% 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%
Tidal by Redwood4.6%
Other84.9%
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 interface is good, and it's very easy to define and create jobs. If a job is not running or there is an error, the solution will send an email. That's all very good and very useful."
"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 feature of JAMS is its user-friendly interface, especially after upgrading from version six to seven."
"JAMS has helped save IT staff time by automating tasks previously performed with scripts, and its scheduling feature has been particularly useful."
"The most valuable feature is the easily accessible data in the database because we run a lot of SQL scripting against the database."
"Fortra's JAMS helped us centralize job management across our platforms and applications. This is critical because we schedule tasks across multiple applications and operating systems, using triggers and start dates to coordinate their execution."
"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."
"The product is easy to use."
"The most valuable feature of this solution is the functions are easy to use."
"This solution enables us to improve our daily processing times; we can do everything faster than before we used this solution."
"Visibility into the workflow and ease of use to be able to schedule have improved our organization."
"After we started using CA Workload Automation, everything became one integrated system and it makes the troubleshooting and monitoring much easier."
"AutoSys significantly reduces manual effort."
"It is a fairly stable solution."
"We definitely can count on it being up all the time."
"Automic Automation Engine provides us the ability to map logic using a scripting language, giving us an advantage where practically all automation problems can easily be implemented within the Automation Engine."
"It's very user-friendly, intuitive, and robust, and most people, once you give them a quick tutorial on it, can figure out how to use Tidal."
"The best feature of Tidal Workload Automation Software is its ease of integration with other systems, including ERP, CRM, and BI tools."
"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."
"It has been super stable. There are no complaints on stability. We would not be using it if Tidal wasn't stable."
"It saves times due to automation. With some files, we do hundreds a day for a particular vendor. This would be hard to do manually. Also, the speed at which we can do this is excellent."
"Tidal Automation’s most valuable feature is customization. It can work and connect with any app."
"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 by Redwood is a user-friendly solution."
 

Cons

"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."
"The product does not allow the users to cut and paste the job names from the screen."
"The documentation is not super... It's not as quick and slick as I'd like it to be."
"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."
"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."
"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."
"This is probably something you don't want to hear, but support seems to be getting worse over the years."
"Documentation and cross-application externals could be improved."
"Needs better documentation with fully explained examples for some of the job types."
"Autosys is still lagging behind some competitive products from a functionality perspective."
"Pricing model for distributed should have an Enterprise option."
"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."
"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."
"Performance improvements in the UI would be appreciated."
"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."
"The biggest improvement they need to work on is doing better QA checks before they release new patches and service packs."
"The reporting is kind of lacking and not super awesome."
"Understanding and using Tidal Automation could be overwhelming for someone with minimal programming language."
"With the client, we have had certain issues. The user interface for Tidal is a little slow. A lot of people would love this tool if they had a faster user interface. The drill-down functionality should be much quicker than what it is pulling out now. If I fill out some data, then it takes awhile to get that data back onto the screen. It's not as fast as we were expecting."
"Setting up the initial product was a little hard."
"The software's performance and scalability could be improved, particularly when dealing with large-scale workloads or complex business processes."
"We've had some quirky stuff happen on an occasional basis where a job does not take off; for example, a job we expected to be finished by 3:00 a.m. is sitting there and not executing when we come in in the morning, and I have brought this up with Tidal's support but they have never had an answer for it."
 

Pricing and Cost Advice

"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 expensive, to be honest, but it does the job."
"Fortra's JAMS pricing structure has deteriorated significantly since its acquisition by Fortra."
"This is a good product at a fair price."
"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."
"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."
"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."
"JAMS is relatively inexpensive, with additional costs only incurred for tags, other services, and optional support renewals."
"The pricing needs to be improved. Some of my client's complained that it was too expensive."
"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."
"CA pricing has been a problem, and not looked upon favorably here at all."
"There is an annual license to use AutoSys Workload Automation."
"Validate how many agents you need beforehand."
"It is overpriced."
"We paid to use the solution monthly."
"Right now, we are in a good position with the licensing model that we have with the Tidal vendor. So, we won't have any issues. even if we double in our current production. Initially, Tidal provided us some specs where if you have these number of jobs, then you come under this category. They usually provide a range of jobs from 2,000 to 10,000. You can use these specs for your infrastructure. Whether you have 2,000 or 8,000 jobs, Tidal should support it."
"They work with you on licensing. So, it has been great. Everybody has different licensing, but I've had good luck with the licensing. They've been very accommodating. You basically need to buy a license for each physical server, but then you're allowed an unlimited number of virtual servers."
"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."
"Our yearly licensing costs are between $10,000 to $20,000. They have always been reasonable with us. I like that non-production licensing is about half the cost of production licensing. Licensing is by adapter typically. We have had scenarios where we have had to take an adapter from one environment to another, and they've allowed us to do that. They have made it a very reasonable process. There's definitely a feeling that they will work with you."
"I have had no issues with the licensing."
"The new prices that we've received seem reasonable and comparable to the marketplace."
"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."
"This solution is a bit expensive in the current world where everybody is trying to cut down on certain things."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
884,933 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Manufacturing Company
10%
Computer Software Company
9%
Healthcare Company
5%
Financial Services Firm
40%
Manufacturing Company
9%
Insurance Company
5%
Retailer
5%
Financial Services Firm
14%
Computer Software Company
9%
Manufacturing Company
9%
Performing Arts
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business12
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?
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...
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: March 2026.
884,933 professionals have used our research since 2012.