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

"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."
"Employee onboarding, de-boarding, and other service-provision features make the process easier and it saves us a lot of time."
"It's scalable."
"The data visualization is good."
"I would definitely recommend Orchestration if you're already on the ServiceNow platform."
"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 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."
"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."
"Temporal allows retryability for different workflows whenever they fail. It helps ensure idempotence and that things get done."
"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 most valuable feature is its ability to manage and automate workflows without manual intervention efficiently."
"It is very useful for long-running workflows."
"When some jobs take a lot of time and fail midway, the solution’s retry feature automatically causes them to retry."
"The solution's most valuable feature is its ability to fix things quickly."
"It's easy to get started and user-friendly."
"The initial setup is easy."
 

Cons

"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."
"We had a few use cases where we couldn't find solutions in Orchestration and had to go with the publishers to solve them."
"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."
"If I compare the interface of ServiceNow Orchestration with Boomi, it is easier to use Boomi than ServiceNow Orchestration."
"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 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."
"Configuring workflows can be improved —the solution could offer more options, but it's not a must-have."
"Temporal doesn't have built-in data storage to store the state of the ongoing execution."
"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."
"Temporal lacks many resources, like YouTube videos, which users can use to learn or refer to if they get stuck with the solution."
"Developers often mention the desire for a more intuitive visualization of workflow states."
"Sometimes it scales kind of badly, but it depends on the process of our products."
"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."
"There are areas where Temporal could improve. For instance, calling multiple microservices with Temporal introduces latency due to workflow registration and analytics overhead."
 

Pricing and Cost Advice

"It is not 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."
"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."
"This is an expensive product, but it is the best in the market considering the features and lack of competitors."
"Pricing is custom to every customer."
"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."
"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."
"Temporal is a free, open-source tool."
"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."
"It is worth the price."
report
Use our free recommendation engine to learn which Process Automation solutions are best for your needs.
886,426 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,426 professionals have used our research since 2012.