No more typing reviews! Try our Samantha, our new voice AI agent.

ServiceNow Orchestration vs Temporal comparison

Why PeerSpot?
 

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

ServiceNow Orchestration
Ranking in Process Automation
14th
Average Rating
8.2
Reviews Sentiment
6.6
Number of Reviews
16
Ranking in other categories
No ranking in other categories
Temporal
Ranking in Process Automation
10th
Average Rating
8.6
Reviews Sentiment
6.8
Number of Reviews
18
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of November 2026, in the Process Automation category, the mindshare of ServiceNow Orchestration is 2.6%, down from 3.5% compared to the previous year. The mindshare of Temporal is 3.3%, down from 7.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Process Automation Mindshare Distribution
ProductMindshare (%)
Temporal3.3%
ServiceNow Orchestration2.6%
Other94.1%
Process Automation
 

Featured Reviews

Claude-Yameogo - PeerSpot reviewer
Consultant at a comms service provider with 1,001-5,000 employees
Has helped orchestrate processes and integrate workflows across cloud environments
I recommend ServiceNow Orchestration for larger companies because they have the capability to manage complex environments where it performs better. I promote low-code solutions for these implementations. I don't currently have an idea regarding the pre-built integrations of ServiceNow Orchestration, but I plan to check my area to determine what added value it can bring. I would rate this solution a nine overall.
MP
Founder & CEO at Lanzar
Automation streamlines operations and improves time and cost efficiency
My overall experience with Temporal is rated between 8 to 9, mainly due to a learning curve that only senior developers can navigate effectively, which makes it a bit challenging for junior developers. We don't have any instances of on-premise, so I cannot comment on that because we are a first company, with all services deployed on cloud infrastructure. Most of the integration is through RPC or APIs, ensuring all our systems are in cohesion. We do state persistence to a Postgres instance, and we have modified it to our use case with better indexing. And for fault tolerance, we built a queue and an alerting mechanism that notifies us if any workflows fail after specific failure points so we can act upon it. On a scale of 1-10, I rate Temporal an 8.

Quotes from Members

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

Pros

"The product has a flexible interface for development."
"The solution effectively automates business processes."
"It's scalable."
"It's probably the best product out there."
"It is a very stable product, highly affordable."
"Orchestration is commonly utilized by major corporations. The process of linking methods in ServiceNow, known as the RTS chain to parent methods, is executed seamlessly and efficiently. It's quite impressive and significant in its impact."
"I use it to orchestrate processes and integration features to gather and update data during specified timeframes or exchange data in real-time when changes occur based on certain criteria."
"The automation ServiceNow has provided saves us a lot of time and resources."
"Temporal provides visibility into workflow progress and analytics and supports scheduled tasks with customizable settings, making it very convenient."
"Temporal focus on developers rather than business users."
"The solution's most valuable feature is its ability to retry from an interrupted state."
"The most valuable feature is its ability to manage and automate workflows without manual intervention efficiently."
"We like the fact that the whole process is durable, which is very useful to us."
"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."
"It's easy to get started and user-friendly."
"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

"The flow rate for releases and updates is very, very slow and does not meet customers' objectives for scalability."
"ServiceNow Orchestration needs to improve multiple aspects in which their event monitoring system is one. The solution lacks event monitoring systems which makes them non-competitive. They need to include improvements in a similar manner that they did in Sweden."
"There can be gaps in integration."
"There is still room for more integrations. Or, it would be nice to bundle multiple products together rather than selling everything as a model as that turns out to be a bit costly."
"The connectors need to be updated because certain connectors for third-party tools are not up to date, and our customers are having problems synchronizing data with some of these tools."
"If I compare the interface of ServiceNow Orchestration with Boomi, it is easier to use Boomi than ServiceNow Orchestration."
"Efficiency of some features could be improved."
"The automatic remediation needs enhancement, particularly integrating ServiceNow with tools like SolarWinds and Logic Monitor. It is functional, but it needs improvement."
"Temporal doesn't have built-in data storage to store the state of the ongoing execution."
"Temporal's debugging is a bit complex."
"Not all necessary information is available online, and community support is limited."
"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."
"There are areas where Temporal could improve. For instance, calling multiple microservices with Temporal introduces latency due to workflow registration and analytics overhead."
"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."
"Developers often mention the desire for a more intuitive visualization of workflow states."
 

Pricing and Cost Advice

"This is an expensive product, but it is the best in the market considering the features and lack of competitors."
"The solution is costly and orchestrations are very expensive."
"The cost of the solution is based on the number of plugins, conductors and integrations used and is charged annually. The licensing cause has been increasing gradually which makes it difficult to access. Initially offer free features but over the time the charges rise which make it an expensive solution with limited features. Along with that, the integration issues persist and require additional middle where and internet connectivity for effective usage."
"It is not very expensive."
"It is quite expensive because we've had some customers come back and say it's quite pricey because in order for them to go ahead with Orchestration, they must have already been paying for Discovery, service mapping, and a few other things."
"Pricing is custom to every customer."
"ServiceNow doesn't give a clear cost indication. They have different contracts with different organizations and it's all about negotiation, so you don't know how they are doing at the cost level."
"In terms of price, this solution is at the higher end of what you'll find."
"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."
"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."
"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."
report
Use our free recommendation engine to learn which Process Automation solutions are best for your needs.
921,840 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Manufacturing Company
11%
Outsourcing Company
10%
Comms Service Provider
9%
Financial Services Firm
27%
Computer Software Company
7%
Manufacturing Company
7%
Comms Service Provider
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise4
Large Enterprise9
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise4
Large Enterprise6
 

Questions from the Community

What is your experience regarding pricing and costs for ServiceNow Orchestration?
The cost of ServiceNow Orchestration is considered medium; it is expensive but powerful. I would rate the pricing experience as a six out of ten.
What needs improvement with ServiceNow Orchestration?
If I compare the interface of ServiceNow Orchestration with Boomi, it is easier to use Boomi than ServiceNow Orchestration. Boomi is an ESB with orchestration features to integrate and exchange dat...
What is your primary use case for ServiceNow Orchestration?
I use ServiceNow Orchestration's third-party integrations, and when I benchmarked ServiceNow Orchestration, I ensured that there are connectors and API capabilities available to integrate it wi...
What is your experience regarding pricing and costs for Temporal?
In terms of pricing, Camunda is indeed costlier than Temporal. The cloud deployment costs differ, and while Camunda 7 can be cheaper due to its integrated setup, comparing latest versions between T...
What needs improvement with Temporal?
The only area for improvement in Temporal is the UI. I know it is a non-UI first product, but comparing Camunda versus Temporal UI, there is a difference. Moreover, n8n, being a no-code platform, i...
What is your primary use case for Temporal?
The main purposes for using Temporal are automation flows, especially financial automations and supply chain automations. Our company name is SR, we are a digital-first CPG brand making company, ma...
 

Overview

 

Sample Customers

experian, BEACHBODY, HealthPartners, Banosoft
Information Not Available
Find out what your peers are saying about ServiceNow Orchestration vs. Temporal and other solutions. Updated: November 2026.
921,840 professionals have used our research since 2012.