AWS Step Functions vs Tidal by Redwood comparison

Amazon Web Services (AWS) and Tidal Software by Redwood are both solutions in the Workload Automation category. Amazon Web Services (AWS) is ranked #9 with an average rating of 9.0, while Tidal Software by Redwood is ranked #20. Amazon Web Services (AWS) holds a 2.0% mindshare in WA, compared to Tidal Software by Redwood’s 3.5% mindshare. Additionally, 85% of Amazon Web Services (AWS) users are willing to recommend the solution, compared to 97% of Tidal Software by Redwood users who would recommend it.

Comparison Buyer's Guide

Download the report

Executive SummaryUpdated on Mar 29, 2026

Tidal by Redwood and AWS Step Functions compete in the task automation and workflow orchestration category. Tidal by Redwood stands out for its flexibility and broad integration capabilities, whereas AWS Step Functions excels in seamless AWS service integration and workflow orchestration.

Features: Tidal by Redwood is known for its flexibility and extensive automation capabilities, allowing integration with numerous platforms and providing strong support for event-driven tasks. It excels in complex scheduling with dependencies, supporting diverse scripts across different servers. AWS Step Functions is integrated seamlessly with AWS services, featuring advanced workflow orchestration and a user-friendly graphical design interface, simplifying application development through JSON formatting for error management.

Room for Improvement: Tidal by Redwood could improve its job migration tools, reporting capabilities, and user interface. Cloud integration is challenging for some users. AWS Step Functions would benefit from enhanced third-party integration, increased payload capacity, and clearer pricing models. Both products require improvements in cloud integration methodologies and performance optimization.

Ease of Deployment and Customer Service: Tidal by Redwood operates primarily in on-premises and hybrid cloud environments, praised for its dedicated customer service post-Cisco acquisition by STA Group. AWS Step Functions, notably cloud-based, ensures efficient deployment within AWS, though its support could enhance responsiveness and technical insights.

Pricing and ROI: Tidal by Redwood offers flexible on-premises licensing without hidden costs, considered cost-effective with its extensive features, despite slight price increases. AWS Step Functions receives mixed feedback on cost-effectiveness due to complex pricing variables but is seen as affordable within the AWS ecosystem. Both demonstrate a positive ROI, increasing productivity and efficiency, with Tidal favoring budget management and integration with business processes, while AWS Step Functions caters to AWS-integrated businesses.

To learn more, read our detailed AWS Step Functions vs. Tidal by Redwood Report (Updated: August 2026).

Buyer's Guide

AWS Step Functions vs. Tidal by Redwood

August 2026

Download the complete report

Helped 908,858 peers since 2012

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

Mindshare comparison

As of August 2026, in the Workload Automation category, the mindshare of JAMS is 3.1%, up from 1.9% compared to the previous year. The mindshare of AWS Step Functions is 2.0%, up from 1.6% compared to the previous year. The mindshare of Tidal by Redwood is 3.5%, down from 4.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.

Workload Automation Mindshare Distribution
Product	Mindshare (%)
JAMS	3.1%
AWS Step Functions	2.0%
Tidal by Redwood	3.5%
Other	91.4%

Workload Automation

Featured Reviews

Latha Viswanathan

Principal Data Base And Infrastructure Engineer at a outsourcing company with 501-1,000 employees

Automation has replaced nightly monitoring and delivers reliable, unified job scheduling

We have really enjoyed working with JAMS in terms of notifications, alerts, and streamlining. There used to be a process with Automate, which is another product from Fortra, but even before that, the other division of the company that we were merging with had a tool that was built in-house called a file handler or file distributor. It was an in-house developed tool, but it was not as streamlined or as efficient as JAMS is. We literally had to have a dedicated nighttime person monitoring. Although we are 24/7, the divisions of the company that we were using JAMS for have been small scale. While we have automated it, we have streamlined it in such a way that notifications go out and alerts go out, but if there is anything, then we get paged and alerted, and if anything needs to happen at midnight, we can wake up. On the other hand, with the tool I mentioned, the file handler and distributor, we used to have a dedicated nighttime person that had to be sitting and monitoring it to see when a file arrived, whether it met the conditions, and then execute the next particular job. By using JAMS, we have gained a lot more efficiencies in terms of all of those to streamline it, and there is no necessary need for having an overnight engineer just keeping an eye on all of this.

Read full review

Yush Mittal

Senior Software Engineer at a tech services company with 10,001+ employees

Central orchestration has streamlined complex data workflows and now drives timely aviation alerts

The best features AWS Step Functions offers include the ability to deploy it via code. It helps us orchestrate anything that we want. Even if we have Glue jobs for another use case or Lambda that we are currently looking forward to, we are using Lambda to take DynamoDB data for real-time sales monitoring, then it goes to our S3 bucket. We have multiple workflows that are orchestrated by AWS Step Functions, and at the core, the main functionality is based on different frameworks. We have an Athena complete workflow, Glue job-based workflow, and a separate Lambda-based workflow. All of these are separately handled in AWS Step Functions. This is a good point and again with the inbuilt facilities of it, including how we can construct those workflows and add up a catch state or roll back or do multiple iterations using the Map state, that is very helpful for us.The Map state feature has specifically helped my team create a rollback state of the data since we were dropping some of our data assets. In case we want them back, we just wanted to do this. We took a particular layer and provided the data list, including the tables list, and using the Map state, we iterated over this list and one by one we did the backups of this data at the concurrency of five tables in a single execution. The Catch state, on the other hand, allows us to identify any error immediately. If we encounter an error, the Catch state immediately picks it up and we integrated webhooks or email notifications. That is how we are able to identify immediately if we face any error. At the core of our data engineering platform, AWS Step Functions sit at the topmost core of whatever pipelines we have. It is a main orchestration tool for us and helps us save costs. It is a key component of our engineering platform.

Read full review

Jim Gillingham

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.

Read full review

Quotes from Members

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

Pros

"Getting JAMS in place was a game changer for us back then."

"The feature or capability to import a job is most valuable. We can import an existing job from different platforms, and all the configurations get migrated as well without modifying the code, job schedule, etc."

"The most valuable feature for us is that it's DR-ready. With respect to disaster recovery, it has the built-in capability for failover to our DR site. If all of the required ports are open, it can be done seamlessly."

"It has definitely drastically improved our capabilities to scale our automation. Before JAMS, there were a lot of manual processes. We had a couple of operators who spent all day doing that. A lot of the time with human intervention and human processes, it is as good as the person who may be following a procedure and human error is a big problem."

"By using JAMS, we have gained a lot more efficiencies in terms of all of those to streamline it, and there is no necessary need for having an overnight engineer just keeping an eye on all of this."

"The alerting in it is really targeted... you can set specific alerting so that if jobs in a given folder fail, certain people are alerted. You can also set security at the folder level, so that only people in those areas can go set them. That means that the alerting and security can be set at a very granular level."

"JAMS offers diverse scheduling capabilities for any kind of job, including Linux, PowerShell scripts, and SQL, enabling automation of jobs, which has proven beautiful after three years of usage."

"JAMS positively impacts my organization because it helps make it easier to manage JD Edwards scheduled jobs and fills the gap that the JD Edwards application has with scheduling, resolving a lot of those issues."

More JAMS pros

"It's a general solution that you can adapt to your own needs and is simple to use. We like that it can be integrated with everything in the AWS suite, and that the creation of the pipeline can be done using the graphical user interface."

"The solution is stable...The solution is easy to scale."

"Overall, I would rate AWS Step Functions at least nine out of ten."

"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."

"It has enabled my organization to create workflows with a lot of different AWS services; it's a general solution that you can adapt to your own needs and is simple to use."

"The integration capability is easy, whereas building state machines is tricky."

"At the core of our data engineering platform, AWS Step Functions sit at the topmost core of whatever pipelines we have, is a main orchestration tool for us, helps us save costs, and is a key component of our engineering platform."

More AWS Step Functions pros

"It does a very good job of managing cross-platform, cross-application workloads."

"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."

"We wouldn't be able to do many of the complex scheduling that we do today without it. For us, it is a mission-critical app. Because if it doesn't work or has a problem, then SAP doesn't function. It is that critical. So, it's an essential tool for us to manage and run SAP jobs."

"It's easy to use and easy to administer, and it's very flexible."

"The versatility of being able to run on many different types of servers is valuable. There is also a versatility of different services that you could run jobs on. It's highly versatile. You can run a lot of different types of scripts on a lot of different types of servers. It interfaces with all of them."

"With the varied features in the varied adapters provided, we use Tidal Enterprise Scheduler because we want everything to be scheduled in one place. Tidal provides that for us with its tools and varying platforms in our organization. Tidal provides all the connectors to the platforms. This is very useful because we don't want to look for another scheduler for scheduling certain jobs. We don't want to look at those schedules manually between platforms."

"Tidal Automation’s most valuable feature is customization. It can work and connect with any app."

"Having a single pane of glass, regardless of which technology we're talking about has been great."

More Tidal by Redwood pros

Cons

"I would enhance the compatibility feature of JAMS because sometimes when the server is under high load, it does not inform us and we cannot get answers."

"All my machines at work are Macs. JAMS client is a Windows-based thing. It is all built on .NET, which makes perfect sense. However, that means in order for me to access it, I need to connect to a VPN, then log onto one of our Azure VMs in order to access the JAMS client. This is fine, but if for some reason I am unable to do so, it would be nice to be able to have a web-based JAMS client that has all the exact same functionality in it. There are probably a whole bunch of disadvantages that you would get with that as well, but that is definitely something that would make life easier in a few cases."

"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 client is horrible. Every time JAMS puts out a survey on what they can improve, I always say, "The client: When you are setting up jobs, it is quite horrible." The response has been, "Well, we are just using the Windows foundation," and I am like, "Why isn't it only your product?" We can get around it now that we know its quirks, but it is not the most user-friendly of tools out there. The UI is completely unintuitive. We had to go and open up a support ticket with JAMS just to get something back. It is not user-friendly at all."

"Fortra is getting much better with documentation and examples, but there is still room for improvement."

"Sometimes the UI is not the most responsive I've ever used. But because it does its job, I don't complain."

"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 UI is completely unintuitive. We had to go and open up a support ticket with JAMS just to get something back."

More JAMS cons

"The pricing of the solution can be improved."

"It is hard to coordinate the declaratory language."

"I would like to see more data transformation features in Amazon Step Functions like additional operators and logic."

"The solution's pricing could be cheaper. It is cheaper than Airflow."

"The interface can sometimes feel limited, as we're unable to see what AWS is running behind the scenes."

"It wasn't easy to understand the licensing model. It's like if you use just a little, it's cheap, but it becomes more expensive as you use more. It's like a hook that ties you inside the Amazon ecosystem. So, it creates a dependency."

"One area for improvement is the payload size. Currently, I sometimes have to save data as a file since I cannot pass it within Step Functions, necessitating caching in processes."

"The price and support are areas with shortcomings where the solution needs to improve."

More AWS Step Functions cons

"The solution needs more advanced reporting and data visualization capabilities to enable deeper analysis of job performance and trends."

"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."

"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."

"The software's performance and scalability could be improved, particularly when dealing with large-scale workloads or complex business processes."

"To better fit their unique needs, the solution should give more customization options."

"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."

"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."

"Initially, it is complicated to understand the functionalities as there is limited product documentation."

More Tidal by Redwood cons

Pricing and Cost Advice

"The pricing of JAMS has not been an issue for us, as it has allowed us to save time."

"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."

"The licensing model for JAMS is straightforward and based on the number of agents, not the number of jobs you run. It's cheap and fairly simple."

"The product is reasonably priced, and we don't have any add-ons."

"JAMS is relatively inexpensive, with additional costs only incurred for tags, other services, and optional support renewals."

"I haven't been involved in the financial side for several years, but we buy one host and unlimited agents, and we get a reasonable price for that. We're happy with the amount we pay and the scalability it provides."

"Our licensing is pretty cheap because we have a state solution. So, we pay only $1,000 a year."

"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."

More JAMS pricing and cost advice

"The solution is expensive."

"The solution's price is reasonable."

"We are satisfied with the pricing of Tidal. It's in the moderate range and it feels very achievable for us."

"...it is a pretty affordable scheduler tool that lets us do a lot. You get a lot of bang for the buck... The licensing model is hugely flexible."

"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 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."

"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."

"We think the pricing is very fair. We have been happy with the pricing compared to some of the other solutions in the space."

More Tidal by Redwood pricing and cost advice

See which vendors are best for you

Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.

See recommendations

908,858 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Financial Services Firm

16%

Construction Company

12%

Manufacturing Company

Comms Service Provider

Financial Services Firm

22%

Manufacturing Company

Comms Service Provider

Insurance Company

Financial Services Firm

18%

Construction Company

11%

Manufacturing Company

Performing Arts

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

By reviewers
Company Size	Count
Small Business	15
Midsize Enterprise	14
Large Enterprise	23

By reviewers
Company Size	Count
Small Business	8
Midsize Enterprise	2
Large Enterprise	6

By reviewers
Company Size	Count
Small Business	3
Midsize Enterprise	6
Large Enterprise	38

Questions from the Community

What is your experience regarding pricing and costs for JAMS?

I was not really involved in the pricing, setup cost, and licensing at that level. I am more involved in the technica...

See all answers

What needs improvement with JAMS?

To improve JAMS, it should resolve the issues with the JD Edwards application and the need for the SSH client connect...

See all answers

What is your primary use case for JAMS?

My main use case for JAMS is to install, set up, and configure for customers working with JD Edwards application. A s...

See all answers

What is your primary use case for Amazon Step Functions?

My main use case for AWS Step Functions is in our data platform where we are trying to generate alerts. For generatin...

See all answers

What advice do you have for others considering Amazon Step Functions?

I rate AWS Step Functions a nine out of ten on a scale of one to ten. I chose a nine out of ten because it is basical...

See all answers

What is your experience regarding pricing and costs for Amazon Step Functions?

AWS Step Functions helps us save costs as it is a self-managed service and is serverless. We look out for the inbuilt...

See all answers

Ask a question

Earn 20 points

Comparisons

Control-M vs JAMS

Compared 12% of the time

AutoSys Workload Automation vs JAMS

Compared 9% of the time

Stonebranch vs JAMS

Compared 8% of the time

VisualCron vs JAMS

Compared 7% of the time

ActiveBatch by Redwood vs JAMS

Compared 4% of the time

More JAMS Competitors

Camunda vs AWS Step Functions

Compared 12% of the time

Apache Airflow vs AWS Step Functions

Compared 6% of the time

Control-M vs AWS Step Functions

Compared 6% of the time

Nintex Process Platform vs AWS Step Functions

Compared 6% of the time

Pega Platform vs AWS Step Functions

Compared 4% of the time

More AWS Step Functions Competitors

Control-M vs Tidal by Redwood

Compared 12% of the time

AutoSys Workload Automation vs Tidal by Redwood

Compared 7% of the time

ActiveBatch by Redwood vs Tidal by Redwood

Compared 5% of the time

Arvato streamworks vs Tidal by Redwood

Compared 5% of the time

Stonebranch vs Tidal by Redwood

Compared 4% of the time

More Tidal by Redwood Competitors

Product Reports

Buyer's Guide

JAMS

August 2026

Download JAMS product report

Buyer's Guide

AWS Step Functions

August 2026

Download AWS Step Functions product report

Buyer's Guide

Tidal by Redwood

July 2026

Download Tidal by Redwood product report

Also Known As

No data available

Amazon Step Functions, Step Functions

Tidal Workload Automation, Cisco Workload Automation, Tidal Enterprise Scheduler

Interactive Demo

JAMS Software

Demo not available

Amazon Web Services (AWS)

Demo not available

Tidal Software by Redwood

Overview

JAMS is an automation orchestration and job scheduling solution that runs, monitors, and manages critical IT processes from a single console, from simple batch jobs to complex, cross-platform workflows. JAMS automates jobs across Windows, Linux, UNIX, IBM i, z/OS, and OpenVMS, with native integrations for the databases, BI tools, and ERP systems already running your business, including SQL Server and SAP. Jobs run on any schedule or trigger off other events, and dependency management keeps multi-step workflows in the right order.

Every job is centrally monitored, with notifications on success or failure and an audit trail of every execution. Built-in conversion tools migrate existing jobs from Windows Task Scheduler, SQL Agent, or Cron without rebuilding them, and JAMS replaces homegrown, single-platform scripts with one centrally managed system.

JAMS includes two AI capabilities at no additional cost. JAX is an AI agent built into the JAMS Web Client. Ask it a question in plain language, and it finds a job, troubleshoots a failure, or looks up how to do something, grounded in JAMS documentation, not general AI guesswork. It acts only when asked, and every change waits for your approval. JAMS MCP brings JAMS into the AI coding tools teams already use, including Cursor, Claude Code, GitHub Copilot, and Claude Desktop.

Both run inside the customer's network with the signed-in user's permissions and no elevated AI account, and every action, AI-driven or not, lands in the same audit trail as everything else in JAMS.

For teams managing thousands of jobs across SQL Server, ADF, Airflow, SAP, JDE, and Banner, this cuts tribal knowledge and middle-of-the-night troubleshooting. Knowledge that once lived in one person's head becomes something any team member can ask about directly.

The AI lives in the product, not in the support queue. Support is staffed by humans JAMS will never outsource, based in the United States, the United Kingdom, and Australia. New tickets go to long-tenured engineers, and every JAMS customer has the CEO's cell phone number.

JAMS' mission is to reduce the operational burden of critical automation, so teams spend more time on the work automation was meant to free them for.

JAMS Software

AWS Step Functions integrate seamlessly with other AWS services to offer efficient pipeline and workflow management. Its intuitive design allows for streamlined orchestration, easily handling complex tasks.

AWS Step Functions provide robust orchestration and automation capabilities, simplifying the creation of workflows with graphical and JSON-based designs. It excels in managing tasks through advanced parallelization and error handling features. Automatic scaling further enhances performance, ensuring reliability in varied environments. However, improvements are needed in IDE integration, larger data handling, and fault tolerance. Users find value in its capacity for microservice orchestration and data integration, although dependency on the Amazon ecosystem and limited third-party integrations pose challenges.

What are the key features of AWS Step Functions?

Integration with AWS Services: Facilitates seamless coordination with AWS offerings like Lambda and Glue.
Graphical and JSON-Based Design: User-friendly interfaces simplify workflow design and management.
Advanced Orchestration: Efficiently manages task execution with parallelization and error handling.
Automatic Scaling: Ensures optimal performance by adjusting resources as needed.
Microservice Integration: Supports smooth microservice communication and operation.

What benefits should organizations assess when considering AWS Step Functions?

Enhanced Efficiency: Automates and streamlines task execution across platforms.
Scalability: Adapts to workloads, providing flexibility in resource management.
Improved Workflow Management: Facilitates reliable and error-free operations.
Visualization and Automation: Simplifies complex processes with visual tools.
Data Validation and Script Execution: Integrates data operations smoothly within data lakes.

In industries managing data pipelines, AWS Step Functions orchestrate workflows, execute parallel ETL jobs, and integrate various AWS services, enabling smoother operations and efficient data migration. Companies benefit from streamlined processes and robust handling of interdependent tasks.

Amazon Web Services (AWS)

Tidal Software is a leading provider of enterprise workload automation solutions that orchestrate the execution of complex workflows across systems, applications and IT environments. With a comprehensive portfolio of products and services, Tidal optimizes mission-critical business processes, increases IT cost efficiencies and satisfies legal and regulatory compliance requirements. Hundreds of customers around the world count on Tidal for modernizing their workload automation and driving their digital transformation. Tidal Software is headquartered in Chicago with offices in Houston, London, Minsk, Belarus and Chennai, India. For more information, visit tidalsoftware.com.

Tidal Software by Redwood

Sample Customers

Teradata, Arconic, General Dynamics, Yum!, CVS Health, Comcast, Ghiradelli, & Boston’s Children’s Hospital

Alpha Apps, The Guardian, SGK, Bigfinite

Information Not Available

Buyer's Guide

AWS Step Functions vs. Tidal by Redwood

August 2026

Free Report: AWS Step Functions vs. Tidal by Redwood

Find out what your peers are saying about AWS Step Functions vs. Tidal by Redwood and other solutions. Updated: August 2026.

DOWNLOAD NOW

908,858 professionals have used our research since 2012.

See our AWS Step Functions vs. Tidal by Redwood report.

See our list of best Workload Automation vendors.

We monitor all Workload Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.