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
121
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

"You can let users access the system and manage jobs: self-service."
"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."
"I find Control-M for SAP and Control-M for Informatica good. You can connect to the Linux or Windows servers, and you can run multiple jobs."
"As soon as you have an issue, a ticket is created and the tech support is quite responsive."
"The feature we use most in Control-M is related to the file transfer module. It is quite advanced compared to the other tools like Automate, etc. The new version which has come of same MFT has a lot of advanced features which makes it very easy to work with. There is less need for written programs and more GUI-based stuff."
"It has certainly helped speed things up."
"In Helix Control-M, we have the automation API that allows us to customize and do integrations easily in any script, such as Java or Python. It is all integrated within the integration API."
"Control-M has helped to improve our data transfers because it allows us to monitor the execution of the process. With other technologies, we cannot do that."
"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."
"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."
"Temporal allows retryability for different workflows whenever they fail. It helps ensure idempotence and that things get done."
"The solution's most valuable feature is its ability to retry from an interrupted state."
"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."
"The solution's most valuable feature is its ability to fix things quickly."
"The tool is easy for a beginner to learn. The documentation covers activities, workflows, workers, servers, and more. While more examples could be beneficial, the existing resources are good enough to help you get started. There are also YouTube videos available that can provide additional context. The Slack community for Temporal is very active and helpful, similar to Stack Overflow, where you can find answers to a wide range of questions from basic to advanced levels. If you have a unique question, the community is responsive and provides knowledgeable support."
"Temporal focus on developers rather than business users."
 

Cons

"They can give more predefined plug-ins so that we don't have to create them."
"They could enhance the product's data flow, job processing speed, and efficiency."
"We've also had a few database bugs within our organization. I think we are migrating to OpenJDK rather than just regular Java and that has since shown some issues with our Control-M instance, timing out and causing our jobs to stop running. We are still working with BMC to fine-tune that and get that resolved."
"When it comes to supporting cloud services, Control-M is a bit slow. We are not advancing with the technology because we don't have the modules that can interact or use the new application services provided by the cloud technologies."
"A lot of businesses are using ServiceNow, which is another tool. I would like there to be some integration with ServiceNow or other third-party tools as well as have easily available integrations. Right now, we need to write scripts. Apart from that, if there were some integrations with an ITSM tool, then that would be good. Because at the end of the day, most of our clients are using different ITSM tools. I know that BMC Remedy is easy to integrate with Control-M. However, if there was availability for Jira as well as other ITSM and DevOps tools, that would be a good improvement."
"The company has been working with BMC on the MFT. There are still some things about MFT which don't work the way that we want with our needs. So, we would like to see that improved."
"Finding documentation on the website can be a bit confusing."
"It can definitely expand promotions, so that a single job can be moved. Currently you can only promote a job by promoting the entire table."
"Temporal doesn't have built-in data storage to store the state of the ongoing execution."
"Temporal lacks many resources, like YouTube videos, which users can use to learn or refer to if they get stuck with the solution."
"We previously faced issues with the solution's patch system."
"Configuring workflows can be improved —the solution could offer more options, but it's not a must-have."
"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."
"While the tool can be a bit daunting initially, especially if you're not used to async programming models, it's generally a pleasure. There's always room for improvement, though. I've noticed some limitations with the .NET SDK regarding dynamic workflows, but this might have been improved in recent versions. Overall, I think Temporal could be more open about implementing features in a more—.NET-friendly way, especially in how you add workers and clients."
"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."
"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."
 

Pricing and Cost Advice

"Pricing is generally affordable, though some features cost a bit more."
"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."
"We have a five-year contract with task-based licensing."
"The pricing is moderate, not too low or too high compared to other solutions."
"Pricing varies depending on which components and modules you are using."
"Its cost is a little bit higher than other solutions such as AutoSys or DAC. For the demo, there were some plans, such as start plan, scale plan, etc. Pricing was based on the plan."
"For the tooling that you get, the licensing is acceptable. It has competitive pricing, especially with all the value that you get out of it. There are additional costs with some of the additional modules, but they are all electives. Out of the box, you get the standard Control-M experience and the standard license. They're not forcing some of the modules on you. If you decide that you do need them, you can always purchase those separately."
"This is an area where it is a little difficult to work with BMC. They want to do licenses by job, which is what we have. For example, the simplest is to license by job, but they can also license by nodes. While the licensing is simple to use, it might not be the correct licensing model for the customer. It is okay because we want to license by job, which is something measurable. At the end of the day, licensing by job is the most important."
"It is worth the price."
"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."
"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."
report
Use our free recommendation engine to learn which Process Automation solutions are best for your needs.
849,190 professionals have used our research since 2012.
 

Top Industries

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

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: April 2025.
849,190 professionals have used our research since 2012.