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

"We value Control-M mainly for the ability to control multiple nodes in a coordinated manner. Control-M has the ability to really coordinate across a lot of nodes."
"In our bank, all new applications need to be implemented with Control-M. We try to look for the best way to establish communication between both products. One of the new features for us is Application Integrator. It is a very interesting feature because it lets us integrate with those applications that are not included in Control-M. By using Application Integrator, we can easily integrate new technologies. With the help of Application Integrator, we recently integrated with Blue Prism, which is a robotic product. We could integrate such processes into Control-M. Now, we are working with Ansible, and we are putting Ansible automated processes into Control-M."
"The product has enhanced the interface with a clear visual display of data and process batches, showing the completion status of workflows."
"Speeds up processes and automated tasks."
"Control-M is useful to automate all critical and non-critical processes. Using Control-M, we can automate application workflows as well as file transfers involved in application workflows. We can also use it to run batches related to applications. Automating these processes reduces the RTO and RPO, which helps in the case of failures. It also helps us to identify bottlenecks and take corrective measures."
"The flexibility of Helix Control-M allows us to manage tasks efficiently. The user interface is comprehensive and lets me view all my jobs on one page, monitor everything, and access the job history."
"The integration with ServiceNow is good. When a job ends and there are problems with it, we automatically open an incident in this platform, and the number of the incident is forwarded to Control-M. This means that we have a record of it with the log of the job."
"Automation of the batch jobs is the most valuable feature."
"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."
"What I like best about the tool is that it's easy to install, especially since it uses JavaScript. It's also easy to set up with Docker, and the documentation is easy to understand."
"The solution's most valuable feature is its ability to retry from an interrupted state."
"We like the fact that the whole process is durable, which is very useful to us."
"When some jobs take a lot of time and fail midway, the solution’s retry feature automatically causes them to retry."
"The most valuable thing about Temporal is that we can create multiple and child workflows. We can segregate work as we want, which is good for work organization. It's also easy to maintain. We're trying to generate and fill PDF forms with custom data, including digital signatures. We call AWS and do all activities through Temporal, like calling and saving data in buckets. We do this because we have a lot of load, with multiple users requesting data. We have two types of users: admin and customer. The admin creates forms, and employees or customers fill them out. When admin gets a form, it's stored in Temporal."
"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."
"Temporal allows retryability for different workflows whenever they fail. It helps ensure idempotence and that things get done."
 

Cons

"One feature I would like to include is in the middle of the monitoring domain. In the monitoring domain, if I have to update a number of jobs, the only way to do it is by manually clicking on each job. I would like a feature that allows me to do a mass update in the jobs, which I feel is still lacking."
"Advanced File Transfer (AFT) has limitations that cause us to use a bit more licensing than we feel is appropriate."
"There can be some complexities with the UI part, especially with the advanced features."
"Some of the features are not available. We were about to deploy the REST API, but we had some challenges. We had to use a third-party application. So, it should be improved in terms of integrating REST API jobs. That was something that was lacking. The customer was not that happy in terms of getting the desired output. So, we had to use a third-party application called Hangfire. We would like to have more videos on REST API integration, and we would like to have easy integration with the Control-M application through the REST API."
"The report form and display function are weak; they are not very powerful."
"Finding documentation on the website can be a bit confusing."
"A lot of the areas of improvement revolve around Automation API because that area is constantly evolving. It is constantly changing, and it is constantly being updated. There are some bugs that are introduced from one version to the next. So, the regression testing doesn't seem to capture some of the bugs that have been fixed in prior versions, and those bugs are then reintroduced in later versions."
"They can give more predefined plug-ins so that we don't have to create them."
"There are areas where Temporal could improve. For instance, calling multiple microservices with Temporal introduces latency due to workflow registration and analytics overhead."
"Retro compatibility needs improvement. Sometimes, when we make new changes to a workflow, it fails if it is not configured properly due to compatibility issues."
"Temporal doesn't have built-in data storage to store the state of the ongoing execution."
"We previously faced issues with the solution's patch system."
"Temporal could be improved by making it more user-friendly for beginners and non-technical staff, ensuring easier integration and usability across different use cases."
"Temporal's debugging is a bit complex."
"One area where I think Temporal could improve is its dashboard, particularly in event tracking. Currently, the dashboard doesn't show a time-based view of events, meaning it doesn't display when an event started or went through the retry process. If this feature could be added in a future release, it would significantly enhance monitoring capabilities. Other than that, Temporal's overall performance is quite impressive, and we're confident we can migrate to the Temporal workflow."
"One area for the product improvement is the learning curve."
 

Pricing and Cost Advice

"Compare to other tools Pricing and licensing was more. It should be decrease."
"The pricing is moderate, not too low or too high compared to other solutions."
"BMC does NOT have a great licensing model from my perspective."
"We have account based licensing. There are two or three types of licensing. One of them is based on the number of jobs, so we a license close to 4,000 jobs per day. The cost is based on the different modules, which we buy from them. If we a buy a hardware module, which we are presently using and integrating, that is an additional cost, but I'm not sure of the amount. Each module comes with a different cost."
"We have a license till 2024. We are good and satisfied with it."
"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."
"we are more looking for a better cost/license/performance model because BMC, while we could say it's the best, is also the most expensive. That is what we are probably most annoyed with. We are paying something like €1,000,000 over three years for having 4,000 jobs running. That's expensive."
"The pricing is reasonable. It's not an exorbitant amount. The licensing is pretty reasonable for the number of jobs that we run."
"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."
"It is worth the price."
"Temporal is a free, open-source tool."
"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.