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

AWS Step Functions vs Tidal by Redwood comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jun 15, 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

AWS Step Functions
Ranking in Workload Automation
10th
Average Rating
8.2
Reviews Sentiment
7.3
Number of Reviews
13
Ranking in other categories
Business Process Management (BPM) (9th)
Tidal by Redwood
Ranking in Workload Automation
12th
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 August 2025, in the Workload Automation category, the mindshare of AWS Step Functions is 1.6%, up from 0.6% compared to the previous year. The mindshare of Tidal by Redwood is 4.6%, up from 3.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation
 

Featured Reviews

Carlos Alberto Marangon - PeerSpot reviewer
Automate complex workflows with seamless AWS integration
Step Functions provide seamless integration with AWS services, which enhances the speed of application development. The JSON app launched recently allows us to define data execution more easily. The Standard Workflows feature includes error replay capabilities, which are crucial for efficient error management. The Amazon State Language (ASL) in JSON format facilitates workflow automation and accelerates the deployment of Step Functions.
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

"It is a scalable solution."
"What I like the most about Amazon Step Functions is how easy it is to use."
"AWS Step Functions acts as a high-level layer, allowing us to seamlessly integrate with microservices."
"The JSON app launched recently allows us to define data execution more easily."
"The solution is stable...The solution is easy to scale."
"Overall, I would rate AWS Step Functions at least nine out of ten."
"One can rate all the calls and that is a good feature."
"If you want to create a workflow to call one Lambda function after another, and other serverless features, it could save you a ton of money. That's for sure."
"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 data management on offer was valuable."
"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."
"I like the fact that I have control, and I am able to monitor. If there is an issue, I would be able to respond to any jobs that may fail. With any other scheduler that I know of, a lot of times, when I have a very complex script, if there is an issue in the middle of it, I have to let the whole process fail and then figure out a way to recover from it, whereas Tidal will stop the process, and I can resolve that issue. Once I resolve the issue, I can continue the process. This is very important for invoicing, accounts payable, accounts receivable, or any kind of financial reporting. It allows you to recover from an issue much more effectively than anything else that I have seen."
"From a management standpoint, when using the solution for cross-platform, cross-application workloads, I've never had a problem with the application. It's very interactive, especially with the different security levels that they offer."
"Tidal Workload Automation Software provides the ability to quickly adapt to changing business requirements."
"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."
"Thinking of all the people involved in checking jobs on a daily basis, manually running jobs or auditing them through standalone tools, and trying to connect them. We have saved hundreds of hours weekly, which is substantial."
 

Cons

"It is difficult to suggest improvements at the moment."
"It is hard to coordinate the declaratory language."
"The interface can sometimes feel limited, as we're unable to see what AWS is running behind the scenes."
"The solution's pricing could be cheaper. It is cheaper than Airflow."
"The solution's data size limit can be improved."
"I would like to see more data transformation features in Amazon Step Functions like additional operators and logic."
"Setup took about one day. We had some errors to understand in the beginning, but now everything is working good."
"Increasing the payload size would be beneficial."
"To better fit their unique needs, the solution should give more customization options."
"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."
"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."
"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."
"There are several improvement points that our team has provided to the vendor."
"The GUI, the graphical user interface, gets a little bit busy."
"Their software installation and update process could use some improvements. I'm pretty sure they're working on that, but that's definitely an area where it could be streamlined a lot. There's still a lot of manual work that you have to do with the schedule when you deploy masters or do the agents."
"They can do better reporting in terms of production statistics reporting."
 

Pricing and Cost Advice

"The solution's price is reasonable."
"The solution is expensive."
"We pay maintenance annually through Blue House of about $9,000. That's for our two environments: production and test."
"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."
"We think the pricing is very fair. We have been happy with the pricing compared to some of the other solutions in the space."
"The new prices that we've received seem reasonable and comparable to the marketplace."
"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 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."
"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."
"We've been able to purchase more adapters because the cost of the product has been very reasonable."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
864,155 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
30%
Manufacturing Company
10%
Computer Software Company
7%
Insurance Company
7%
Financial Services Firm
19%
Manufacturing Company
11%
Computer Software Company
9%
Insurance Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Amazon Step Functions?
The integration capability is easy, whereas building state machines is tricky.
What is your primary use case for Amazon Step Functions?
The primary use case was the execution of scripts and data migration related to data lakes. We were using Python and other AWS Step Functions ( /products/aws-step-functions-reviews ).
What advice do you have for others considering Amazon Step Functions?
I would recommend AWS Step Functions to others. Overall, I rate AWS Step Functions an eight out of ten.
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

Amazon Step Functions, Step Functions
Tidal Workload Automation, Cisco Workload Automation, Tidal Enterprise Scheduler
 

Overview

 

Sample Customers

Alpha Apps, The Guardian, SGK, Bigfinite
Information Not Available
Find out what your peers are saying about AWS Step Functions vs. Tidal by Redwood and other solutions. Updated: July 2025.
864,155 professionals have used our research since 2012.