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

Control-M vs Temporal comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 17, 2024

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

"It has multiple features. You can plan your execution in Control-M. It provides one single window where you can define workflows regardless of geographic boundaries and platforms. A batch process can be executed from this single window. It provides insights into your processes. Your business people will know what process they are running and what is the state of the process. Instead of knowing that they're not going to meet the SLA the next morning, the business people immediately know the changes in their process. Control-M is very easy. I can tell a non-technical person that this is how it works, and he would be able to easily understand it. Business people can understand the methodology of Control-M and the intuitive features that it has. It has a fantastic graphical user interface and is easy to understand. You just have to drag and drop but in a very intuitive way. Monitoring features are also good. It has different color coding schemes, which can help you to understand the status of your workflow. An operator who is not that technical and is just monitoring the status of the application can see by color-coding the status of a process. If anything goes wrong or a process is stuck, it gives you a hint. You can just right-click and see the logs and the output. Even if the system is not right there in the data center and is located somewhere else, you can monitor it right from there and see the workflows."
"We are using Control-M for day-to-day operations only. It is helpful for us in our day-to-day operations. It is a key in our financial sector. We are automating via Control-M in our treasury operations, including any evening updates. Control-M makes things easier and faster by helping our treasury operations go without any interruptions."
"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 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."
"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."
"In the client, it provides a unified view for me. I can alter the view that I want to see jobs and conditions. This is nice to have. The fact that you can see everything in one space is very important, especially these days where everything is about data and monitoring as well as because we are working from home on a global basis. So, I can monitor jobs in real-time, along with any failures or anything that might be stuck. The real-time monitoring and the ability to see everything in one place is important for us because we operate 24/7."
"The workflow is much easier compared to the ACS services we were using."
"Before Control-M, we didn't have a centralized view and could not view what happened in the past to determine what will happen in the future. The Gantt view that we have in Control-M is like a project view. It is nice because we sometimes have some application maintenance that we need to do. So, in a single console, we can hold the jobs for the next hour or two. We can release that job when it is finished. This is a really nice feature that we didn't have before. It is something really simple, but we didn't previously have a console where we could say, "For the next two hours, what are the jobs that we will run? And, hold these jobs not to run." This is really important."
"It is very useful for long-running workflows."
"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."
"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."
"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 focus on developers rather than business users."
"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."
 

Cons

"Right now, Control-M is the leader in EMA analysis, which is similar to Gartner. However, clients want to invest in a strong technology, and therefore this product needs to keep up with the high expectations set for it."
"They can give more predefined plug-ins so that we don't have to create them."
"The documentation could be improved, and I'd also like to see automatic upgrades."
"I would like to see them adopt more cloud. Most companies don't have a single cloud, meaning we have data sources that come from different cloud providers. That may have been solved already, but supporting Azure would be an improvement because companies tend not to have only AWS and GCP."
"The infrastructure could be improved."
"The report form and display function are weak; they are not very powerful."
"We have some plug-ins like BOBJ, and we need a little improvement there. Other than that, it has been pretty good. I haven't seen any issues."
"But for some issues, BMC will suggest to upgrade to new version which will not be feasible to standards of the organisation. Hence some work around should be shown to run the business until new version was upgraded."
"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."
"One area for the product improvement is the learning curve."
"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."
"Temporal doesn't have built-in data storage to store the state of the ongoing execution."
"Temporal images aren’t FIPS compliant, and we have to be FIPS compliant."
"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."
"Developers often mention the desire for a more intuitive visualization of workflow states."
 

Pricing and Cost Advice

"Cost-wise, it is good."
"The cost is basically $100 a job, give or take."
"The price is right because of the licensing schema, which is based on nodes and processes. You purchase what you use, no more and no less, and you can grow with time."
"We have a five-year contract with task-based licensing."
"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."
"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."
"Pricing varies depending on which components and modules you are using."
"It is not bad. The company can afford it, and it pays for itself. We have those jobs running automatically."
"Temporal is a free, open-source tool."
"It is worth the price."
"Temporal is open-source and free to use, which is great. We didn't have to pay for any premium features."
"The savings weren't as big as we initially expected, but they were pretty great from a developer's perspective."
"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."
report
Use our free recommendation engine to learn which Process Automation solutions are best for your needs.
831,881 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
30%
Computer Software Company
16%
Retailer
13%
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 Control-M?
Pricing is generally affordable, though some features cost a bit more.
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: January 2025.
831,881 professionals have used our research since 2012.