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

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
12th
Average Rating
8.0
Reviews Sentiment
6.9
Number of Reviews
15
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 October 2025, in the Process Automation category, the mindshare of ServiceNow Orchestration is 3.7%, down from 4.5% compared to the previous year. The mindshare of Temporal is 7.6%, up from 1.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Process Automation Market Share Distribution
ProductMarket Share (%)
Temporal7.6%
ServiceNow Orchestration3.7%
Other88.7%
Process Automation
 

Featured Reviews

Dinesh Kumar Raghu - PeerSpot reviewer
Fastest upgrading technology in the market currently
In each upgrade, ServiceNow is enhancing its product across various areas. They continuously improve different aspects one by one, ensuring that their service evolves with the changing needs. However, frequent upgrades may negatively impact the performance of instances. Therefore, for now, I don't recommend any additional upgrades. The current version fulfills everyone's requirements, and ServiceNow automatically updates annually, keeping pace with industry standards. They've been performing well, so I see no need for further upgrades, especially considering their consistent updates.
Gustavo Carneiro - PeerSpot reviewer
Availability it provides to our products is great and stable product
Sometimes it scales kind of badly, but it depends on the process of our products. If we have too many signals in a workflow, we might need 50 or 60 pods of the same worker. But this doesn’t happen with every worker; it just happens in some special use cases. The scalability is great, but could be better. We needed to change Temporal's database from Postgres to Cassandra to handle it more cheaply for our infrastructure. We do not use Temporal Cloud; we use Temporal Open Source. Cassandra DB was the best choice because it was cheaper. The problem with Postgres was the only problem we faced. But besides that, it has been great since the start.

Quotes from Members

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

Pros

"Employee onboarding, de-boarding, and other service-provision features make the process easier and it saves us a lot of time."
"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."
"It's scalable."
"The solution effectively automates business processes."
"The interface of the solution is very user friendly and it is easily accessible via a simple URL. This makes it easier to complete the UI based tasks but using other features require expertise in languages like Java. But along with that, there are limitation in terms of network connectivity testing and administrator faces regular challenges in conducting connectivity tests due to these limitations."
"There are a lot of ready to use orchestration custom packs."
"The data visualization is good."
"This is a user-friendly solution where scripts can be made with ease. There are also many integration options, including Microsoft products, which gives the product a competitive edge."
"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."
"Temporal focus on developers rather than business users."
"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."
"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."
"The initial setup is easy."
"Temporal provides visibility into workflow progress and analytics and supports scheduled tasks with customizable settings, making it very convenient."
"It is very useful for long-running workflows."
 

Cons

"There should be connectors to cover at least the top industry applications, and they should be easier to configure in a plug-and-play fashion."
"The automatic remediation needs enhancement, particularly integrating ServiceNow with tools like SolarWinds and Logic Monitor. It is functional, but it needs improvement."
"The third-party integrations are challenging when the tools are not from ServiceNow partners. This presents issues when integrating solutions from other vendors."
"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."
"We cannot perform GUI automation using the tool."
"From my space, the only thing that I can say is the spinning up with Google Cloud Services."
"Frequent upgrades may negatively impact the performance of instances. Therefore, for now, I don't recommend any additional upgrades."
"Temporal images aren’t FIPS compliant, and we have to be FIPS compliant."
"Sometimes it scales kind of badly, but it depends on the process of our products."
"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."
"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."
"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."
"I don't like the limitations on data flow, particularly the difficulty of passing large amounts of data between different activities."
"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 lacks many resources, like YouTube videos, which users can use to learn or refer to if they get stuck with the solution."
 

Pricing and Cost Advice

"In terms of price, this solution is at the higher end of what you'll find."
"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."
"The solution is costly and orchestrations are very expensive."
"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."
"This is an expensive product, but it is the best in the market considering the features and lack of competitors."
"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."
"It is not very expensive."
"Pricing is custom to every customer."
"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.
872,778 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
21%
Manufacturing Company
9%
Computer Software Company
9%
Insurance Company
7%
Financial Services Firm
29%
Computer Software Company
14%
Retailer
7%
Manufacturing Company
6%
 

Company Size

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

Questions from the Community

What do you like most about ServiceNow Orchestration?
The interface of the solution is very user friendly and it is easily accessible via a simple URL. This makes it easier to complete the UI based tasks but using other features require expertise in l...
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?
The third-party integrations are challenging when the tools are not from ServiceNow ( /products/servicenow-reviews ) partners. This presents issues when integrating solutions from other vendors.
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: September 2025.
872,778 professionals have used our research since 2012.