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

Control-M vs Temporal comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 9, 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

Control-M
Ranking in Process Automation
3rd
Average Rating
8.8
Reviews Sentiment
7.0
Number of Reviews
120
Ranking in other categories
Managed File Transfer (MFT) (4th), Workload Automation (1st)
Temporal
Ranking in Process Automation
7th
Average Rating
8.6
Reviews Sentiment
7.2
Number of Reviews
17
Ranking in other categories
No ranking in other categories
 

Featured Reviews

Pedro Fuentes - PeerSpot reviewer
Cost-effective, excellent support, and centralized access and control
They have a department that handles requests for enhancements. I talked to Control-M guys back in October or November when they had a gathering here in Atlanta. We talked about not being able to go back in history in Helix Control-M for more than two weeks. We submitted a request for enhancement. They told us that they are working on it, and they are thinking of expanding that to 30 days. We would like to see it expand to 90 days, but they are working on it. In Control-M, we were able to go back 180 days, but that was on-prem. The storage of that data was on our own servers. We know that storage is money, and we do not expect them to store that much of the data, but at least 30 to 60 days seem proper.
AbhishekDash - PeerSpot reviewer
Orchestrates infrastructure tasks like deployment, deletion, and management
Temporal focus on developers rather than business users. In contrast to older workflow orchestration engines like Camunda, which are more business-oriented and strongly emphasize UI and workflow authoring, Temporal is geared toward developers. It provides extensive capabilities for building complex workflows. A standout feature of Temporal is its handling of long-running workflows, a significant advantage over many other solutions. Temporal excels in managing distributed transactions and application state durability, especially in microservice environments where transactions might fail due to network issues. Temporal simplifies these challenges by managing retries, fail-safes, and circuit breakers. As a result, developers don't need to implement these features manually; Temporal handles them implicitly, though it also allows for tuning based on specific needs.

Quotes from Members

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

Pros

"Its compatibility with the new technologies and platforms, like the Google Cloud or Amazon, is the most valuable. Its console allows us to view the duration and execution of a process. It is also very easy to use and easy to implement."
"It helps us meet our service-level agreements. It is integrated into our CI/CD pipeline. It enhances our operational productivity."
"Workload Archiving is a very good feature for us. It helps with our customer requirements in terms of reporting and auditing... Previously, when we didn't have any archive server, we managed the data in Control-M with man-made scripts, and we would pull the data for the last 365 days, or three or four months back. Since we installed the archiving, we have been able to pull the data, anytime and anywhere, with just one click."
"The initial setup is largely straightforward."
"As soon as you have an issue, a ticket is created and the tech support is quite responsive."
"We can tie together all the workloads across the estate and make the whole process reactive to events."
"If a job fails, that development team is notified right away, which improves reliability. Previously, it was on the operators to notify the developers that their job failed, erred, or aborted. Now, it's all automated."
"Control-M can cross all platforms and offers integration for container and cloud solutions."
"The solution's most valuable feature is its ability to fix things quickly."
"What I like best about Temporal is its durable execution, which means you don't need to write many boilerplate code for critical pieces, especially for retries. It also has great observability and a nice dashboard to see issues without digging into logs. The interface for viewing activities is excellent, with good tracing that shows how long activities took and what ran, making it almost perfect for debugging."
"We like the fact that the whole process is durable, which is very useful to us."
"It is very useful for long-running workflows."
"The solution's most valuable feature is its ability to retry from an interrupted state."
"Temporal provides visibility into workflow progress and analytics and supports scheduled tasks with customizable settings, making it very convenient."
"The initial setup is easy."
"The solution's most valuable features include its ability to simplify the management of complex workflows, improve system resilience and fault tolerance, and reduce the need for extensive boilerplate code."
 

Cons

"The biggest improvement they could have is better QA testing before releases come out the door."
"The downtime is higher compared to AWS."
"We did encounter a few scalability issues. Sometimes, there are too many jobs in our environment on different servers, but that’s not the tool issue, we can simply increase the FS size. However, that requires bank cost; hence the scalability issue."
"The high availability that comes from BMC with its supplied Postgres database is very limited. Even using your customer-supplied Postgres database is problematic. We have engaged with them regarding this, but it is difficult. My company doesn't want to do this and BMC doesn't want to do that. We just need to find some middle ground to get the proper high availability. We're also moving away, like the rest of the world, from the more expensive offerings, like Oracle. We are trying to use Postgres, which is free. The stability is good. It is just that the high availability configuration is not ideal. It could be better."
"I would like to see more audit report templates added, and perhaps more customizability in terms of reporting."
"It has a slight issue with daylight savings time while advancing the clock in the Spring."
"They can improve their interface."
"With the current version update, I'm not sure why we needed a separate database upgrade. Why not put it all in one package? Previously, you could do it either via a manual upgrade or an in-place upgrade but it wasn't separate."
"One issue is that we don't have enough resources in the community to get answers when we face problems. We once had a cross-cluster persistence issue, which we solved using different keys. I think Temporal is good right now, but I'm part of the community and will let you know if I think of any improvements."
"I don't like the limitations on data flow, particularly the difficulty of passing large amounts of data between different activities."
"Sometimes it scales kind of badly, but it depends on the process of our products."
"Developers often mention the desire for a more intuitive visualization of workflow states."
"Configuring workflows can be improved —the solution could offer more options, but it's not a must-have."
"We previously faced issues with the solution's patch system."
"Temporal lacks many resources, like YouTube videos, which users can use to learn or refer to if they get stuck with the solution."
"Temporal doesn't have built-in data storage to store the state of the ongoing execution."
 

Pricing and Cost Advice

"Control-M isn't cheap, but this is an enterprise model."
"Pricing is generally affordable, though some features cost a bit more."
"We are paying way more for Control-M than we've paid for any of our other scheduling tools."
"This is now from my previous years as support for banks and big companies. If it's not enterprise scale, I find that it's too expensive for smaller companies. You really have to be quite big and need to have a dedicated support staff to run it, then you'll be fine. What we've seen at smaller companies, it's too expensive because they want to automate everything. Now, stuff that can literally run once a day for the rest of their lives is costing them $3 a job a day. It becomes too expensive, eventually. They are not seeing the return on investment because it's not business critical. Nobody is going to die or they're going to lose money if that job didn't run exactly at 11 minutes past 4:00. It's definitely for bigger enterprise companies, especially banks or healthcare providers. We have had an instance where Control-M was unavailable due to external factors for 20 minutes and there was a loss of almost a million euros because the solution involved logistics."
"The solution is not cheap, it comes with quite a hefty price tag. Control-M is the market leader, but we still want the price to be as friendly as possible."
"Its pricing is a little bit high. They could provide an enterprise-level license for an unlimited number of jobs. Currently, it is based on the number of jobs, and if you exceed the number of jobs, there are charges. For example, if your license is for 3,000 jobs per day, but you run 3,050 jobs, you will have to pay for the extra 50 jobs. They charge $120 per job. So, it is too costly."
"One of the restrictions that we had was with some of the licensing, and not having any insight on the financials part of the product. I don't know what the licensing on the product is, but we don't have an unlimited enterprise license. So, there might be a limitation on either the cost of the licensing or the number of seats."
"It works on task-based licensing."
"It is worth the price."
"Temporal is a free, open-source tool."
"Temporal is open-source and free to use, which is great. We didn't have to pay for any premium features."
"The tool is open source under the MIT license, so there are no hidden fees. You can freely use everything on their GitHub and Docker images."
"The savings weren't as big as we initially expected, but they were pretty great from a developer's perspective."
report
Use our free recommendation engine to learn which Process Automation solutions are best for your needs.
845,040 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
28%
Computer Software Company
13%
Manufacturing Company
8%
Insurance Company
6%
Financial Services Firm
28%
Computer Software Company
19%
Retailer
9%
Manufacturing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

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 because nothing gets left unattended since it is all visible in one place, and th...
What do you like most about Control-M?
First of all, the shift from manual to automation has been valuable. We have a tool that can automate.
What is your experience regarding pricing and costs for Temporal?
Temporal OSS is expensive in infrastructure, but it brings back the reliability that companies need.
What needs improvement with Temporal?
The actual user interface is still in its early stages. It’s very basic. Users don’t really have a complex permission model yet. Users don’t really have ways to automate things like, for example, p...
What is your primary use case for Temporal?
We [my company] use it to run a large workload. We have a set of security scans we want to perform, and we distribute them over a full day, that’s over 24 hours. We use it to orchestrate all the st...
 

Comparisons

 

Also Known As

Control M
No data available
 

Overview

 

Sample Customers

CARFAX, Tampa General Hospital, Navistar, Amadeus, Raymond James, Railinc
Information Not Available
Find out what your peers are saying about Control-M vs. Temporal and other solutions. Updated: March 2025.
845,040 professionals have used our research since 2012.