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

"It's probably the best product out there."
"The iTerm suite is also crucial for visibility and optimization."
"It is a very stable product, highly affordable."
"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."
"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 would definitely recommend Orchestration if you're already on the ServiceNow platform."
"There are a lot of ready to use orchestration custom packs."
"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 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."
"The solution's most valuable feature is its ability to retry from an interrupted state."
"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."
"It is very useful for long-running workflows."
"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."
"We like the fact that the whole process is durable, which is very useful to us."
 

Cons

"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."
"Efficiency of some features could be improved."
"There can be gaps in integration."
"The deployment requires awareness among the project staff."
"I would like a user experience module to be added."
"The third-party integrations are challenging when the tools are not from ServiceNow partners. This presents issues when integrating solutions from other vendors."
"Frequent upgrades may negatively impact the performance of instances. Therefore, for now, I don't recommend any additional upgrades."
"It is a highly complex platform to work on."
"Temporal's debugging is a bit complex."
"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."
"Not all necessary information is available online, and community support is limited."
"Configuring workflows can be improved —the solution could offer more options, but it's not a must-have."
"Temporal lacks many resources, like YouTube videos, which users can use to learn or refer to if they get stuck with the solution."
"There are areas where Temporal could improve. For instance, calling multiple microservices with Temporal introduces latency due to workflow registration and analytics overhead."
"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."
"We previously faced issues with the solution's patch system."
 

Pricing and Cost Advice

"The solution is costly and orchestrations are very expensive."
"In terms of price, this solution is at the higher end of what you'll find."
"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."
"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."
"It is not very expensive."
"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."
"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."
report
Use our free recommendation engine to learn which Process Automation solutions are best for your needs.
920,769 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Outsourcing Company
10%
Manufacturing Company
10%
Comms Service Provider
8%
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 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...
 

Comparisons

 

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.
920,769 professionals have used our research since 2012.