No more typing reviews! Try our Samantha, our new voice AI agent.

AWS Step Functions vs OpCon comparison

Sponsored
 

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:
 

Categories and Ranking

JAMS
Sponsored
Ranking in Workload Automation
3rd
Average Rating
8.8
Reviews Sentiment
6.4
Number of Reviews
45
Ranking in other categories
No ranking in other categories
AWS Step Functions
Ranking in Workload Automation
9th
Average Rating
8.4
Reviews Sentiment
6.8
Number of Reviews
15
Ranking in other categories
Business Process Management (BPM) (11th)
OpCon
Ranking in Workload Automation
13th
Average Rating
9.2
Reviews Sentiment
7.3
Number of Reviews
59
Ranking in other categories
No ranking in other categories
 

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 OpCon is 2.4%, up from 1.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation Mindshare Distribution
ProductMindshare (%)
JAMS3.1%
AWS Step Functions2.0%
OpCon2.4%
Other92.5%
Workload Automation
 

Featured Reviews

LV
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.
YM
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.
Jose Rivera Hernandez - PeerSpot reviewer
Senior VP of Technology at Triangle Credit Union
Helps automate all kinds of jobs and it's worth the price because it saves a lot of time and money
One problem that I had with them when we got SMA Technologies is that sometimes the jobs fail, but they automatically restart. SMA Technologies automatically gets a notification that the job has failed, and they restart it on their end, so now, we have the job restarting twice. There were times when we came into the office in the morning, and we had two files because the job ran twice. I do not know if the system can prevent a job from running the second time. If a job has run successfully, or it is running, it should not run again.

Quotes from Members

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

Pros

"We have over 50 jobs running daily to manage all the integration of our systems and we don’t have to monitor these jobs; they just run, JAMS centralizes the management of jobs in our environment, has streamlined our monitoring, saves us about four hours a week in troubleshooting time, and has helped free up about eight hours a week of IT staff time."
"Fortra's JAMS helped us centralize job management across our platforms and applications. This is critical because we schedule tasks across multiple applications and operating systems, using triggers and start dates to coordinate their execution."
"The code-driven automation for more complex scheduling requirements frees up time because it's really easy to use... It's almost like a stand-alone software that we can't live without."
"One of the things I like the most, as a SQL DBA, is the fact that we can manipulate tables in the background. Also, the fact that you can have your own views and work with the product the way it fits best is a very helpful feature."
"JAMS has improved my organization by taking a myriad of manual processes and allowing us to automate them. It enables our folks to focus more on tasks that require their human intelligence and their creativity and less on just mundane tasks. It increases efficiency, accuracy, and consistency."
"JAMS has been a beneficial monitoring tool for our project in terms of being able to deliver data that is essential for users."
"JAMS has helped save IT staff time by automating tasks previously performed with scripts, and its scheduling feature has been particularly useful."
"The user-friendly and adaptable scheduler allows us to manage various scheduling scenarios."
"It is a scalable solution."
"The solution is stable...The solution is easy to scale."
"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 JSON app launched recently allows us to define data execution more easily."
"The integration capability is easy, whereas building state machines is tricky."
"What I like the most about Amazon Step Functions is how easy it is to use."
"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."
"It's Amazon, it's scalable."
"The fact that I can do five minutes to three hours of work in 30 seconds is a significant improvement."
"For us, the most valuable feature of the solution is the file transfer piece and being able to automate the moving of files around between our various vendors. It reduces the time involved versus somebody having to individually move the files around."
"The most valuable feature is being able to schedule tasks so that they reliably occur each day, each week, each month, or sometimes several times a day... The scheduler works as it should."
"We have definitely seen a return on our investment with OpCon, as we have doubled our client base without needing to increase our workforce and are able to take on additional projects while our operators focus on monitoring and other valuable work."
"File Watcher can run jobs when files are made available in a folder."
"Last year, we added a second environment and the OpCon Deploy product. This has allowed us to build a testing environment. This has been a great addition for us as we can work through our workflows without disrupting our production environment."
"My favorite feature is the dashboard feature, which shows jobs that are running, and completed, any failures, and provides dashboard reporting."
"We consider OpCon to be one of our tier-one applications, meaning it's almost as critical and important as our core host system."
 

Cons

"I would like a simple web interface that I could give to my team to go in and kill jobs or see why jobs died so that we don't have to drill down deeper into the application and know everything about it. It would be good to have a really clean web engine that would say here are the jobs running. We can then click to see the time running and whether any of them fails and other similar things. I know they have one, but it's not very simplistic."
"When looking at a folder in JAMS with many jobs, it would be good to have better information in the list display of what's inside those jobs. We get some information, but other important details are missing."
"I would like to see the ability to interface with Microsoft group-managed service accounts, but they're still in the research phase. They need to ensure everything's legit and safe. The report designer and dashboards could also be improved. We're running 7.3, so I don't know if they have updated the reporting in 7.5, but I think the reports and dashboards could be better."
"Fortra is getting much better with documentation and examples, but there is still room for improvement."
"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."
"It is important to receive notifications if a charged job fails and SQL is halted. JAMS does not provide halted notifications by default, which is a critical feature that needs to be added."
"Sometimes the UI is not the most responsive I've ever used. But because it does its job, I don't complain."
"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."
"Setup took about one day. We had some errors to understand in the beginning, but now everything is working good."
"The interface can sometimes feel limited, as we're unable to see what AWS is running behind the scenes."
"If AWS Step Functions keeps adding more integrations, it would be even better."
"It is hard to coordinate the declaratory language."
"AWS Step Functions' fault tolerance capabilities can be improved, but if managed well in orchestration, then the impact is minimal."
"The solution's data size limit can be improved."
"I think AWS Step Functions is good, but the UI in the console can be much more user-friendly."
"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."
"There are some limitations in the actual jobs that are created and how you're able to rename files. Suppose you're bringing in, say, 10, 15, or 20 reports from a core system, and you're using an "asterisk character" to identify files. For example, if you're grabbing files that start with this, end with this, but the characters in between could be different, it has to retain that same name in the destination. It won't allow you to rename them with a date stamp or the like."
"Stability is an area for improvement. There are FTP agents that run on the MCP and they are there so that we can transfer a file from the MCP to the Windows environment or vice versa. Sometimes, and nobody has been able to figure out why, it just goes down, and all of my jobs that need it are hanging or failing... It would be very helpful if they could figure out what in the world is happening with that FTP client that's on the MCP."
"The ability to retrieve information from logs in variables to display relevant information would be helpful."
"I have noticed lately that [tech support's] first answers tend to be, "Let's upgrade it to the latest and greatest first," without looking into anything. The last couple of times I've logged a ticket that's been the response, which is a little frustrating. We're not big on just upgrading on a whim. We do full testing."
"The only thing that we have been talking about with the vendor is the Solution Manager tool that we have. It is a great tool. It is getting replaced by another tool that is probably called Enterprise Manager. We just had a few complaints about it. The navigation of that new tool is a little bit more arbitrary than what we have been used to."
"The logs are a little daunting to look at the first few times, however, as you begin to understand what you're looking at, it becomes easier."
"There is some difficulty with the ease of use when I don't have some of the templates that were already created. More templates would be great. Non-core featured templates are my biggest struggle."
"Licensing would be the first part I would overhaul. Each time a new licensing paradigm comes out, more features are removed and costs are added. They "add" features that are rarely used and increase charges for the number of jobs run. I'm sure someone in finance got a raise for their brilliance but the end-users won't thank them one bit. Expect price hikes and threats when you hold them to account at every opportunity."
 

Pricing and Cost Advice

"Fortra's JAMS pricing structure has deteriorated significantly since its acquisition by Fortra."
"The pricing is reasonable."
"It was $10,000 for the first year. Then, there is a maintenance cost for licensing every year that we get billed $5,000 for every year."
"Take advantage of its scalability. You can start small. The initial cost is very reasonable. Once you have started picking up the tool and adopting it, then you can scale up from there and buy more agents."
"All licensing models are a little overpriced, but JAMS offers a good value, especially given their support response times and ability to handle unforeseen issues like the SFTP transfers. I hope to find more use cases to get a better bang for our buck."
"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."
"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 solution is expensive."
"The solution's price is reasonable."
"The pricing is very reasonable."
"Our license is for 1000 jobs. Including support, the license and upgrades are 2000 euros a month."
"Cost depends on your environment. We are doing stuff now with failover and recovery, so we have boosted our costs."
"It's definitely worth the cost."
"This solution is slightly more expensive than our previous solution. Right now, we are paying about $40,000 a year. However, we think it's well worth the cost to keep things automated, reducing our staff."
"I have seen some contracts, and it seems that Control-M is a lot more expensive than OpCon, but I do not know the pricing of OpCon. Control-M seems to be four or five times more expensive than OpCon."
"Our annual maintenance costs are $45,000. The initial cost is separate."
"Scaling is pricey."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
908,800 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Construction Company
12%
Manufacturing Company
8%
Comms Service Provider
7%
Financial Services Firm
22%
Manufacturing Company
9%
Comms Service Provider
6%
Insurance Company
6%
Financial Services Firm
17%
Computer Software Company
16%
Construction Company
8%
Outsourcing Company
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business15
Midsize Enterprise14
Large Enterprise23
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise2
Large Enterprise6
By reviewers
Company SizeCount
Small Business16
Midsize Enterprise29
Large Enterprise19
 

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...
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...
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...
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...
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...
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...
What is your experience regarding pricing and costs for OpCon?
I am the one who signs the contract. In the beginning, when I started working here, it seemed very expensive, but aft...
What needs improvement with OpCon?
One problem that I had with them when we got SMA Technologies is that sometimes the jobs fail, but they automatically...
What is your primary use case for OpCon?
In this credit union, we use OpCon for automation. That is the main use of it. We have over 3,000 jobs and schedules ...
 

Comparisons

 

Also Known As

No data available
Amazon Step Functions, Step Functions
No data available
 

Interactive Demo

Demo not available
Demo not available
 

Overview

 

Sample Customers

Teradata, Arconic, General Dynamics, Yum!, CVS Health, Comcast, Ghiradelli, & Boston’s Children’s Hospital
Alpha Apps, The Guardian, SGK, Bigfinite
LOHR, Carnival Cruise Lines, Herbalife, Digital Federal Credit Union, Synergent, Frandsen Bank & Trust
Find out what your peers are saying about AWS Step Functions vs. OpCon and other solutions. Updated: August 2026.
908,800 professionals have used our research since 2012.