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

ServiceNow Orchestration 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

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
3rd
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 April 2026, in the Process Automation category, the mindshare of ServiceNow Orchestration is 2.7%, down from 4.1% compared to the previous year. The mindshare of Temporal is 4.9%, down from 5.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Process Automation Mindshare Distribution
ProductMindshare (%)
Temporal4.9%
ServiceNow Orchestration2.7%
Other92.4%
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

"I would recommend ServiceNow Orchestration, and I consider it the best product in its domain in the market now."
"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."
"Great with IT processes and business processes."
"The solution effectively automates business processes."
"The iTerm suite is also crucial for visibility and optimization."
"The product has a flexible interface for development."
"The automation ServiceNow has provided saves us a lot of time and resources."
"It's probably the best product out there."
"The ROI is apparent in terms of business case automation; previously, a bunch of people filled in data in NetSuite or managed stocks between warehouses and Amazon, but now everything is automated, saving time."
"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."
"The solution's most valuable feature is its ability to retry from an interrupted state."
"When some jobs take a lot of time and fail midway, the solution’s retry feature automatically causes them to retry."
"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."
"We like the fact that the whole process is durable, which is very useful to us."
"It's easy to get started and user-friendly."
"The solution's most valuable feature is its ability to fix things quickly."
 

Cons

"There can be gaps in integration."
"Frequent upgrades may negatively impact the performance of instances. Therefore, for now, I don't recommend any additional upgrades."
"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."
"We cannot perform GUI automation using the tool."
"I would like a user experience module to be added."
"The automatic remediation needs enhancement, particularly integrating ServiceNow with tools like SolarWinds and Logic Monitor. It is functional, but it needs improvement."
"From my space, the only thing that I can say is the spinning up with Google Cloud Services."
"Sometimes it scales kind of badly, but it depends on the process of our products."
"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's debugging is a bit complex."
"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."
"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."
"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

"In terms of price, this solution is at the higher end of what you'll find."
"It is not very expensive."
"This is an expensive product, but it is the best in the market considering the features and lack of competitors."
"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."
"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."
"The solution is costly and orchestrations are 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."
"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 open-source and free to use, which is great. We didn't have to pay for any premium features."
"It is worth the price."
"Temporal is a free, open-source tool."
report
Use our free recommendation engine to learn which Process Automation solutions are best for your needs.
886,011 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
22%
Manufacturing Company
8%
Computer Software Company
6%
Insurance Company
6%
Financial Services Firm
29%
Computer Software Company
11%
Manufacturing Company
7%
Retailer
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 with o...
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: April 2026.
886,011 professionals have used our research since 2012.