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

IBM Workload Automation vs Tidal by Redwood comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Sep 21, 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

IBM Workload Automation
Ranking in Workload Automation
8th
Average Rating
8.0
Reviews Sentiment
7.0
Number of Reviews
33
Ranking in other categories
No ranking in other categories
Tidal by Redwood
Ranking in Workload Automation
13th
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 October 2025, in the Workload Automation category, the mindshare of IBM Workload Automation is 6.0%, down from 8.3% 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 (%)
IBM Workload Automation6.0%
Tidal by Redwood4.7%
Other89.3%
Workload Automation
 

Featured Reviews

Ilhami Arikan - PeerSpot reviewer
With an easy setup phase in place, agent-based installation can be done in minutes
Sometimes we have issues with the solution's stability. So, stability can be improved. Reporting and visibility of the solution need improvement. These days, we need more visibility. We need to access the logs and databases easily. You need to keep track of the running number of logs, like which ones are executed, completed, etc. So if there would be a good reporting dashboard, then it would be good. There's room for improvement in the solution since it is a challenging thing when we want to use the solution's technology with our new technologies. For example, if we need to use TWS on our OpenShift platform, the solution's API is not capable enough. So the product itself needs to be aligned with new technologies.
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

"Technical support from IBM is very good."
"I recommend IBM Workload Automation as it's a well-established and stable product."
"IBM Workload Automation provides good performance and monitoring."
"The project we worked on involved the running of nearly 24,000 job instances in a single day, so I would say that the solution is stable."
"The most valuable feature of IBM Workload Automation is its holistic view, which helps me find technical solutions quickly. For instance, if a customer has an issue completing their workload within a specific time frame, the tool provides enough information to identify and resolve the issue. One of the main challenges is dealing with data infrastructure problems and pending updates. Workload Automation helps me leverage current AI capabilities to recommend architectural updates to avoid these issues. It also allows me to balance CPU usage effectively, ensuring service level agreements are met. The interface is user-friendly and facilitates this process smoothly."
"The whole product is valuable because it is a tool for batch automation."
"The DWC, when configured correctly, is a great GUI tool to provide Self-Service Scheduling capabilities to the user community."
"This solution has a request feature where users can request the added features they need to have developed. Based on client voting for those features, these are developed and released."
"It has been super stable. There are no complaints on stability. We would not be using it if Tidal wasn't stable."
"The Graphical Views feature is also very good for helping us to understand a job stream. It's great for providing a visual overview of the status of a workflow, especially the Critical Path view. That is one of our favorites."
"Tidal integrates with other third-party systems, which makes it easy to connect and exchange data."
"We use the solution for cross-platform, cross-application workloads. The solution’s ability to manage and monitor these workloads is very easy and accurate. We have file dependencies for running jobs. The job does not start until a file exists on a completely different server, then where the job will run. So, it is cross systems."
"The feature that I find to be valuable, as I'm working with other folks, is the ability to cross-schedule across platforms, and the flexibility that comes with that."
"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."
"We use the solution for cross-platform, cross-application workloads. That's the biggest use for us and that's the biggest advantage."
"The most valuable feature is the job scheduler, where you can schedule thousands of jobs to execute at specific times."
 

Cons

"Slow down on the releases a bit. I fully understand that IWA functionality is increasing at an amazing rate, but trying to keep up with the upgrades is rough."
"IBM Workload Automation could be improved by reducing its cost. The maintenance charges have increased significantly, and a lower cost would be beneficial."
"To improve IBM Workload Automation, I suggest enhancing automation features further, as more automation would be beneficial. The product is good enough for my current customers, but improving technical support and pricing would be welcome. We often need quicker responses and better solutions than we can manage manually. These improvements would make the product even better."
"The solution should offer more free technical sessions to customers so that they can gain more experience or learn more about how to use it."
"There should be more custom documentation, specifically around Java APIs. There should also be more training. In terms of features, we are currently using only 50% of its features. We don't use all features that are available, but there is always room for improvement in all of the tools."
"The performance of the previous versions could be better."
"It would be helpful to have a mobile app that could be used to follow the job schedule."
"It should support other schedulers that aren't IBM products."
"When we patch to the next version, there is often a little thing that breaks. It has rarely been a big deal, but I always seem to have to follow up on one tiny issue. It would help if they had some better QA testing of their patches."
"The user interface is the place that needs the most work. If and when we find issues with the product, they are usually in that area. If I had to choose, that's where I'd want issues, as opposed to in the engine. But the UI is average. It's a little sluggish at times and there are some bugs in it."
"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 drill-down into details using the Graphical Views feature is a bit difficult and not that helpful. If you want to go into the details, you have to go to the Job Activity. Graphical Views is not that easy for getting that kind of information."
"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."
"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."
"Initially, it is complicated to understand the functionalities as there is limited product documentation."
"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."
 

Pricing and Cost Advice

"To my knowledge, IWA is the only WLA product that will provide "parallel tracking" capability to assist in upgrading from one platform to IWA."
"The solution is a little bit expensive."
"We transitioned from a server license to per job license, and that saved us a lot money."
"The solution's pricing is affordable."
"The contract is with the customer with whom we are working, so IBM is not directly involved in this."
"Pricing depends on the number of agents that you install."
"It is about one-third of the cost of a controller."
"The new prices that we've received seem reasonable and comparable to the marketplace."
"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."
"Tidal is a low-cost tool and not expensive in comparison to other tools."
"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 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."
"We pay maintenance annually through Blue House of about $9,000. That's for our two environments: production and test."
"This solution is a bit expensive in the current world where everybody is trying to cut down on certain things."
"There have been pricing increases, but with the reduction that our company obtained from Tidal this year, the pricing has become very acceptable for this type of product."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
869,832 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
29%
Manufacturing Company
8%
Computer Software Company
8%
Retailer
8%
Financial Services Firm
16%
Computer Software Company
11%
Manufacturing Company
9%
Insurance Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise1
Large Enterprise29
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise6
Large Enterprise38
 

Questions from the Community

What needs improvement with IBM Workload Automation?
IBM Workload Automation could be improved by reducing its cost. The maintenance charges have increased significantly, and a lower cost would be beneficial.
What is your primary use case for IBM Workload Automation?
We use IBM Workload Automation ( /products/ibm-workload-automation-reviews ) as a scheduler. We install agents on the application servers and use scheduling to trigger jobs on other servers. Our us...
What advice do you have for others considering IBM Workload Automation?
I recommend IBM Workload Automation as it's a well-established and stable product. However, the cost is a concern. The product features a master-slave setup that ensures continuity during failures....
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 and configuration of the software is a bit complicated. Providing the training vi...
 

Also Known As

IBM Tivoli Workload Scheduler, IBM TWS
Tidal Workload Automation, Cisco Workload Automation, Tidal Enterprise Scheduler
 

Overview

 

Sample Customers

Standard Life Group, Banca Popolare di Milano, A*STAR, ArcelorMittal Gent
Information Not Available
Find out what your peers are saying about IBM Workload Automation vs. Tidal by Redwood and other solutions. Updated: September 2025.
869,832 professionals have used our research since 2012.