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

AutoSys Workload Automation vs Stonebranch vs Tidal by Redwood comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

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

Mindshare comparison

As of September 2025, in the Workload Automation category, the mindshare of AutoSys Workload Automation is 10.2%, down from 16.6% compared to the previous year. The mindshare of Stonebranch is 4.7%, up from 4.7% compared to the previous year. The mindshare of Tidal by Redwood is 4.7%, up from 3.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation Market Share Distribution
ProductMarket Share (%)
AutoSys Workload Automation10.2%
Stonebranch4.7%
Tidal by Redwood4.7%
Other80.4%
Workload Automation
 

Featured Reviews

Antony Askew - PeerSpot reviewer
Helps us manage complex workloads, reduce our workload failure rates, and save us time
The visibility and control features are somewhat limited. This is a recognized weakness, but thee vendor is currently revamping the user interface to address it. While the current UI is a bit outdated, it's undergoing improvement. AutoSys Workload Automation has some areas for improvement, particularly in housekeeping and product maintenance. These tasks are currently quite manual and labor-intensive for our team. Additionally, the reporting and forecasting functionalities could be more robust. One area for improvement with AutoSys Workload Automation is that it comprises several distinct tools configured to work together. This necessitates familiarity with multiple tools for effective solution management. Consequently, it can sometimes lack a sense of cohesiveness as a unified solution.
Siddharth Matalia - PeerSpot reviewer
Good GUI and has helpful support but needs a mobile app
This was a migration project where we provided our database, the previous one, and there was a tool that automatically converted the awarded job into Stonebranch. All the conversion was done from the Stonebranch side, and we got a person as well from Stonebranch during migration. There was a person who worked with us a decade back for the AutoSys install as well. He was well aware of our environment, so he helped us a lot. It was easy. It was not that complex. It is much more GUI. That said, we are looking for how the various automation can be done since, through command lines, you can create a number of jobs. While you are creating a single job, it takes 15 minutes with the GUI, however, if you go for the command line, within two or three minutes, your job gets completed. We have built our own solution for automation using some REST API and all those various integrations. It is working for our organization right now. However, we are requesting some kind of solution from Stonebranch. They should have been providing that to us already. For deployment, three or four people were engaged with the setup on their side. To manage everything, they provided us with a person who required help to manage it. Eventually, since it was a cloud platform on their side, if there is some configuration necessary, which they do it. They get a notification, and they fix it very immediately if there is an issue. The response time is very good from their side, and we don't have to worry about maintenance.
Steve Mikula - PeerSpot reviewer
Very reliable processing engine, and scheduling is flawless—crucial elements in our financial transaction processing
Because we've been on it for 20 years, it's pretty easy for us to automate jobs with Tidal at this point. It has become second nature. It's pretty simplistic to set up and get going, although there are different levels of complexity you can have within the product. It depends on how simple you want to keep it. If you just keep it: Job A, Job B, Job C, Job D, that becomes pretty simple. But when you start integrating some complex calendars that use sub-calendars—and you can go three, four, or five deep to set up schedules—it becomes more complicated. The beauty of it is you can go as deep as you need to. We can get really complex or we can keep it simple. We have some use cases for both scenarios. The thing that I like the most is the reliability of the engine. The actual scheduling part of the product is pretty much flawless, but the stability of the product is what I find to be reassuring. We are a financial company, we move billions of dollars a day, and if we don't have our transactions processed in a timely manner we can be penalized and our clients can be penalized. It can have a serious financial impact.

Quotes from Members

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

Pros

"The initial setup is easy."
"The benefits I have seen from AutoSys Workload Automation are significant; I would say it is about ease of administration."
"​We run millions of jobs through it every day using it for financial transactions, banking, credit cards, PeopleSoft, payroll, etc."
"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"
"It streamlines processing really well, so we're able to cut down on our processing times."
"I prefer AutoSys over the other ones out there for ease of use, ease of understanding, and getting people to understand how the tool works."
"CA Workload Automation AutoSys Edition is one of the most powerful schedulers that you have on the open systems, or going between Window servers; to be able to schedule and take advantage of the different powers that the automation has with it."
"We automate recurring processes, keeping track of IT processes controlled worldwide."
"Stonebranch performs well, and the graphical representation is excellent. Overall, it requires more technical effort from our teams, but the solution is intuitive, so anybody can use it."
"I love the Universal Controller. It's been great for us. We host it on-premise... It's High Availability, meaning there's failover from one server to the other if one goes down."
"The tasks are incredibly capable, and as long as you name them with a nice, uniform naming convention, they are very useful. You can create some interesting workflows through various machines, or you can just have it kick off single tasks. All in all, I really like the Universal Task. You can do some mutually exclusive stuff, such as an "A not B" kind of thing. It has a lot of capabilities behind the scenes."
"I can name the aliases on the agent, so if we need a passive environment for an agent, that's one of the nice features. If our primary goes down, I can bring up the passive one and I don't have to change anything in the scheduling world. It will start running from that new server."
"I like the dashboard and the various workflows."
"I have found the agents to be so much simpler, when compared to ESP."
"The support is good from Stonebranch Universal Automation Center."
"The features are upgraded, and every six months they're releasing patches."
"Tidal helps administrators and users to see the information that is relevant to them in that single pane of glass. They can see jobs running, they can see job history, and they can see job progression. If you look at alternatives like Airflow and clouds, you'd have to design your own UI to monitor the progress of the different jobs that you've created in Airflow. So Tidal is huge for us."
"The best feature of Tidal Workload Automation Software is its ease of integration with other systems, including ERP, CRM, and BI tools."
"For us, the calendaring system is very robust. Some of the teams have very specific requests for when they need jobs to run. That's been really valuable, because a lot of times, when people run scripts, if they run on a holiday, they're going to fail... A couple of times a month it probably saves us work and the necessity of logging in from home and checking to make sure everything's okay."
"The job dependency is something that you cannot have in a regular, simple cron job or simple scheduler dependency. The event-driven jobs are core for us, as we really need that. Therefore, we really need Tidal with its ability to run thousands of jobs per day."
"It is intended to enable large-scale automation environments, making it appropriate for companies with complicated processes and big data volumes."
"We had a number of different schedulers in this organization and we've been porting everything that was running out of these other, unrelated schedulers into this scheduler. That has afforded us the ability to set up direct dependencies between processes that couldn't talk to one another before. Over the 15 years, we've definitely gained a lot from that. What had been manual controls have become automated controls..."
"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 best feature is that it allows task scheduling based on particular occurrences, like the receipt of files, database updates, or system notifications."
 

Cons

"Ease of implementation for upgrades."
"I would like to see the Service Orchestrator, a B2B product, and maybe a process audit."
"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."
"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."
"Since Broadcom acquired it, the prices have increased. Many companies feel the same way and are looking for alternate solutions to replace AutoSys Workload Automation."
"We see improvement possibilities in the processing provision of predefined evaluations or individual objects, or in the Self Service portal, which can be used by any user to monitor objects or start objects."
"Documentation and cross-application externals could be improved."
"Quick search feature and job analysis could be improved."
"Stonebranch Universal Automation Center could improve the analytics."
"I would rate Stonebranch somewhere in the middle for ease of setup. It wasn't too straightforward for us because our infrastructure is complex."
"Occasionally, we have an agent that doesn't come back up after patching. That doesn't happen very often... It's really just a restart of the agent and it comes back up. But that might be one thing that could be improved."
"There is a component called the OMS, which is the message broker. We rely on infrastructure, resiliency, and availability for that piece. If that could change to be highly available just as a software component, so that we don't have to provide the high-available storage, etc. for it, that would be a plus. It would just be cheaper to run."
"There is room for improvement with its connectivity with the Microsoft SRS system. It is very weak. They keep telling us it works with it, and technically it does, but it does not provide a lot of visibility. We have lost a lot of visibility migrating to Stonebranch, compared with just running tasks on the SRS server. That's really about the only thing that is a sore point for us."
"I have a request regarding our agent on the mainframe. It may time out when communicating to the Universal Controller, when the mainframe is extremely busy. That can cause a task which is running at that time to not see the results of the job that ran on the mainframe. It happens sporadically during times of really busy CPU usage. We're expecting that enhancement from them in the fourth quarter."
"One hiccup we've had is due to the fact that we have other internal scheduling tools. We're able to talk to them, but we have trouble with some of the networking between them, so we're still trying to work out the kinks there."
"It can be hard to manage the task monitor."
"I don't know if Tidal wants to get into the business of monitoring long-running jobs, but that could be a feature for the future: a job launching and monitoring tool. Using Tidal for monitoring doesn't seem like a good fit, but if they could offer something that did that as an add-on or include it, it might be helpful."
"It takes a lot of time to learn the product. I have admins and developers who are working on the products for the last three to four years and still don't know all the functionalities. Tidal has really great things about it, but people are focused on their day-to-day job and the solution is not intuitive."
"They can do better reporting in terms of production statistics reporting."
"I would like more involvement with the cloud."
"I'm still hoping with Explorer to be able to see end-to-end job streams. That's not really something that's easy to see today in the web client. However, I haven't worked with Explorer yet. One of the things that we have found frustrating is not being able to see an end-to-end job stream across multiple applications within Tidal. We use jobs for that right now, but I have high hopes that we'll be able to see that in Explorer."
"The biggest improvement they need to work on is doing better QA checks before they release new patches and service packs. We do find that you can't trust getting the new product right away, as they have to get some bug fixes out. They do tend to have some bugs in the first iteration."
"My complaint about their pricing model is that every year or every time technology changes or somebody has a new requirement, it usually means that I can schedule that with Tidal, but I would need another adapter. So, every time there is a change, I need a different adapter that I don't have. That's why it is harder to plan for Tidal growth because you have to buy a new adapter every time."
"Tidal Software interface could be more intuitive and user-friendly."
 

Pricing and Cost Advice

"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 price of this solution is reasonable and there is an annual license required."
"There is an annual license to use AutoSys Workload Automation."
"Validate how many agents you need beforehand."
"It is overpriced."
"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."
"We paid to use the solution monthly."
"Stonebranch is cheaper than Control-M, so many companies are using Stonebranch."
"I don't have pricing information, but I do know it's cheaper than our old legacy system. Other than the standard licensing fees there are no additional costs."
"The price of the solution is at a medium level compared to the competition."
"Outside of licensing fees, there aren't any other costs."
"When we reviewed this solution against other vendors, Stonebranch blew everybody out of the water in terms of cost."
"I have had no issues with the licensing."
"We've been able to purchase more adapters because the cost of the product has been very reasonable."
"We think the pricing is very fair. We have been happy with the pricing compared to some of the other solutions in the space."
"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."
"If you are willing to shop around to other vendors, you can possibly get a good price on your support license."
"Our licensing model for Tidal is on an annual basis. It is very good and works well for us. Tidal's licensing is very transparent and simple. It lets you know, for the amount you use, that's the price that you pay. So, we buy X number of licenses, and we know that this is where we are. I'm very happy with that. I saw the licensing modules on other platforms, and I didn't like them. Other companies and solutions would calculate the connections, adapters, and instances. I think that's the reason that BMC was pretty expensive: They just didn't understand what our needs are."
"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."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
867,349 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
46%
Manufacturing Company
9%
Computer Software Company
6%
Insurance Company
5%
Financial Services Firm
25%
Manufacturing Company
10%
Computer Software Company
9%
Insurance Company
8%
Financial Services Firm
17%
Computer Software Company
10%
Manufacturing Company
9%
Insurance Company
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise5
Large Enterprise77
By reviewers
Company SizeCount
Small Business1
Midsize Enterprise5
Large Enterprise22
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise6
Large Enterprise38
 

Questions from the Community

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...
What is your experience regarding pricing and costs for AutoSys Workload Automation?
The solution is costly. The pricing is based on the number of users, which for me, translates to approximately $120,0...
Ask a question
Earn 20 points
What do you like most about Tidal Automation?
Tidal Automation by Redwood is a user-friendly solution.
What is your experience regarding pricing and costs for Tidal Automation?
The price is reasonable in terms of the product’s functionality.
What needs improvement with Tidal Automation?
Initially, it is complicated to understand the functionalities as there is limited product documentation. The setup a...
 

Also Known As

CA Workload Automation, CA Workload Automation AE
Stonebranch Universal Automation Center
Tidal Workload Automation, Cisco Workload Automation, Tidal Enterprise Scheduler
 

Overview

 

Sample Customers

Gaumont, Mercantil do Brasil, CCEE, Hanwha Life
Nissan, Coop, United Supermarkets, Groupon, CSC, Orbitz, Johnson & Johnson, BMW, Qantas.
Information Not Available
Find out what your peers are saying about BMC, Broadcom, JAMS Software and others in Workload Automation. Updated: September 2025.
867,349 professionals have used our research since 2012.