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

Make 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

Make
Ranking in Process Automation
30th
Average Rating
7.0
Reviews Sentiment
6.6
Number of Reviews
2
Ranking in other categories
No ranking in other categories
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

Yaniv Ivgi - PeerSpot reviewer
An affordable cloud solution for automation and data manipulation
Make has a single IP. We cannot use a single IP because of the security. There are a lot of crashes when you work manually. Also, they need to provide more models. When you have an error, Make should inform them with guidance before you make the mistake. There is a lot of data you can confuse.
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

"The most valuable features of Make are the additional options when compared to other similar solutions. For example, with Google my business, you can only do certain things with Zapier, whereas with Make, you can do a little bit more."
"The solution's most valuable feature is its ability to fix things quickly."
"It is very useful for long-running workflows."
"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 provides visibility into workflow progress and analytics and supports scheduled tasks with customizable settings, making it very convenient."
"It's easy to get started and user-friendly."
"The solution's most valuable feature is its ability to retry from an interrupted state."
"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."
 

Cons

"Make could improve the ease of use, it can be more complicated than other solutions. There are a lot of elements that are more technical than in other solutions."
"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."
"Temporal images aren’t FIPS compliant, and we have to be FIPS compliant."
"We previously faced issues with the solution's patch system."
"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."
"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

"The price of Make is approximately $20 per month for the platform."
"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."
"It is worth the price."
"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.
846,617 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Financial Services Firm
27%
Computer Software Company
18%
Retailer
9%
Manufacturing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What needs improvement with Make?
Make has a single IP. We cannot use a single IP because of the security. There are a lot of crashes when you work manually. Also, they need to provide more models. When you have an error, Make shou...
What is your primary use case for Make?
We use Make to manipulate data, cut the numbers, take this line of code, and translate it to another line of code. SaaS products use XML, and other products use JSON. You need to translate to commu...
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

Integromat
No data available
 

Overview

 

Sample Customers

Buan Consulting, Armadia
Information Not Available
Find out what your peers are saying about Make vs. Temporal and other solutions. Updated: April 2025.
846,617 professionals have used our research since 2012.