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

ActiveBatch by Redwood vs AutoSys Workload Automation 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 October 2025, in the Workload Automation category, the mindshare of ActiveBatch by Redwood is 2.8%, up from 2.1% compared to the previous year. The mindshare of AutoSys Workload Automation is 9.9%, down from 16.1% compared to the previous year. The mindshare of Tidal by Redwood is 4.7%, up from 3.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation Market Share Distribution
ProductMarket Share (%)
AutoSys Workload Automation9.9%
Tidal by Redwood4.7%
ActiveBatch by Redwood2.8%
Other82.6%
Workload Automation
 

Featured Reviews

Shubham Bharti - PeerSpot reviewer
Flexible, easy to use, and offers good automation
Occasionally, I find myself contemplating if there is room for improvement in the user interface (UI), and envisioning that with certain enhancements. The UI could potentially offer a more refined and user-friendly experience, fostering smoother interactions and facilitating easier navigation for users engaging with the application. New users might encounter a minor setback due to the absence of readily accessible training videos, which could have otherwise proven to be an invaluable resource in aiding their initial familiarization with the platform, potentially hindering their seamless onboarding process and delaying their ability to harness the software's full range of capabilities to its utmost potential.
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.
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

"Since we are no longer waiting for an operator to see that a job is finished, we have changed our daily cycle from running in eight hours down to about five. We had a third shift-operator retire and that position was never refilled."
"The REST API adapters and native integrations for integrating and orchestrating the software stack are very flexible."
"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."
"ActiveBatch has reduced work by providing automated workflows across several different applications."
"Since I started using this product, I have been able to easily track everything as it mainly monitors, alerts, and looks after all the services - even across platform scheduling - which has helped me immensely."
"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."
"Error Handling is one of the best standout features of ActiveBatch."
"The nice thing about ActiveBatch is once we have created a specific job that can be easily be replicated to another job, then minimal changes will have to be made. This makes things nice. Reduction of coding is substantial in a lot of cases. The replication of one job to another is just doing a few minor tweaks and rolling it into production. This decreases our development costs substantially."
"The flexibility in solving job scheduling challenges allows us to successfully integrate an acquired business’ fiscal close with our own, even though there is a lot of variance as to when they run in the calendar month."
"This solution has made my clients' workplaces a lot less labor-intensive."
"The initial setup is easy."
"It is stable, it works, and it does what it is supposed to."
"The most valuable feature of AutoSys Workload Automation is batch processing."
"We automate recurring processes, keeping track of IT processes controlled worldwide."
"This solution enables us to improve our daily processing times. We can do everything faster than before we used this solution."
"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."
"By leveraging machine learning algorithms, Tidal Automation can use this data to optimize turbine settings and improve overall efficiency and performance."
"The most valuable feature is the job scheduler, where you can schedule thousands of jobs to execute at specific times."
"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."
"The best feature of Tidal Workload Automation Software is its ease of integration with other systems, including ERP, CRM, and BI tools."
"Tidal Automation is very efficient and can quickly automate most manual and repetitive tasks."
"It has been super stable. There are no complaints on stability. We would not be using it if Tidal wasn't stable."
"Tidal Workload Automation Software provides the ability to quickly adapt to changing business requirements."
"We use the solution for cross-platform, cross-application workloads. That's the biggest use for us and that's the biggest advantage."
 

Cons

"ActiveBatch UI could use a little more help, and video tutorials would be greatly appreciated for user guides."
"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."
"A nice thing to have would be the ability to comfortably pass variables from one job to another. That was one of the things that I found difficult."
"The help center and documentation are not that helpful."
"Providing some detailed training materials could be very helpful for new users who have very limited technical information about the tool."
"Some of the advanced features in the user interface are a bit confusing even after referring to the documents."
"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. Then, in order to continue on with your testing, you have to open those back up. I have taken that to them, and they are like, "Yep. We know about it. We know we have some enhancements that need to be taken care of. We have more developers now." They are working towards taking the minor things that annoy us, resolving them, and getting them fixed."
"Except for the GUI, everything looks good."
"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."
"Autosys is still lagging behind some competitive products from a functionality perspective."
"It would be helpful to be able to monitor and manage workload windows so we could minimize downstream applications. This would allow us easier access to the applications."
"Most AutoSys Workload Automation customers are moving because of cost; it is more cost intrusive."
"The WCC could be improved."
"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."
"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."
"AutoSys Workload Automation could improve the integration."
"For the most part, the drill-down and the logging are really good. But if we take an Informatica job, for example: We have the ability, and the operators have the ability, to actually drill down and see, at a session level, where the failure is. There is, unfortunately, no way to extract that into an actual output email or failure email. It's not that that information is not available, but extracting it into an email would be a nice-to-have."
"They can do better reporting in terms of production statistics reporting."
"Tidal's adaptability and user-friendliness could be increased by integrating it with additional programmes and platforms."
"I would like more involvement with the cloud."
"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."
"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. We have to go all the way back to the dependencies and then we can see that one of the dependencies has become unscheduled, for some reason. No changes were made to the schedule but this prerequisite job has, all of a sudden, become unscheduled. I have brought this up with Tidal's support but they have never had an answer for it."
"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."
 

Pricing and Cost Advice

"Currently, we are paying approximately $7,000 yearly, which includes support."
"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."
"If you compare ActiveBatch licensing to Control-M, you're looking at $50,000 as opposed to millions."
"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."
"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."
"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."
"There is an annual license to use AutoSys Workload Automation."
"The return on investment would be very high because doing things manually without this product would be extremely 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 pricing needs to be improved. Some of my client's complained that it was too expensive."
"CA pricing has been a problem, and not looked upon favorably here at all."
"The price of this solution is reasonable and there is an annual license required."
"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."
"I certainly think the pricing is worth the value."
"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."
"The pricing is pretty reasonable. That seems to help a lot versus other companies. There are no other fees aside from the standard licensing fees. There are other products out there where you pay based on how many jobs you run and so on, and I know that's very frustrating for users."
"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."
"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."
"The price is reasonable in terms of the product’s functionality."
"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."
"Our annual maintenance cost is competitive for what we have and what they do."
"Tidal is a low-cost tool and not expensive in comparison to other tools."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
869,089 professionals have used our research since 2012.
 

Top Industries

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

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business10
Midsize Enterprise13
Large Enterprise46
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 ActiveBatch Workload Automation?
Managing the workload and monitoring the tasks were very difficult with manual interventions. Now, by using ActiveBat...
What needs improvement with ActiveBatch Workload Automation?
After upgrades we are facing a few issues and errors triggered, so focusing on this would be appreciated. Some of the...
What is your primary use case for ActiveBatch Workload Automation?
ActiveBatch helped us to streamline our IT workflows and improve overall efficiency. It is the most essential tool in...
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 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

ActiveBatch
CA Workload Automation, CA Workload Automation AE
Tidal Workload Automation, Cisco Workload Automation, Tidal Enterprise Scheduler
 

Overview

 

Sample Customers

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
Information Not Available
Find out what your peers are saying about BMC, Broadcom, JAMS Software and others in Workload Automation. Updated: September 2025.
869,089 professionals have used our research since 2012.