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

PagerDuty Operations Cloud 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

PagerDuty Operations Cloud
Ranking in Process Automation
13th
Average Rating
8.8
Reviews Sentiment
7.3
Number of Reviews
37
Ranking in other categories
IT Alerting and Incident Management (1st), AIOps (9th), Critical Event Management (CEM) (1st)
Temporal
Ranking in Process Automation
7th
Average Rating
8.6
Reviews Sentiment
7.2
Number of Reviews
17
Ranking in other categories
No ranking in other categories
 

Featured Reviews

JeremyEmmett - PeerSpot reviewer
Centralized alert management with customizable routing and superior scheduling
Everything can always be better. Operations are somewhat limited by their integration package. For example, integrating with Jira was problematic until they updated to a better plug-in. The ability to build customized modules would be advantageous, allowing organizations to define their own integration modules. It would be useful to have a way to define all configurations in code that is similar to how Terraform operates.
AbhishekDash - PeerSpot reviewer
Orchestrates infrastructure tasks like deployment, deletion, and management
Temporal focus on developers rather than business users. In contrast to older workflow orchestration engines like Camunda, which are more business-oriented and strongly emphasize UI and workflow authoring, Temporal is geared toward developers. It provides extensive capabilities for building complex workflows. A standout feature of Temporal is its handling of long-running workflows, a significant advantage over many other solutions. Temporal excels in managing distributed transactions and application state durability, especially in microservice environments where transactions might fail due to network issues. Temporal simplifies these challenges by managing retries, fail-safes, and circuit breakers. As a result, developers don't need to implement these features manually; Temporal handles them implicitly, though it also allows for tuning based on specific needs.

Quotes from Members

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

Pros

"It reduces the amount of white noise. If something comes through, then it will alert somebody. However, if it's a bit of white noise that comes through at night, then it gets dealt with the next day. Everything is visible to everybody. It's not just a single person getting an SMS, then going, "Oh, I'm not going to worry about that." The visibility to everybody on the team is one of the great things about it because it reduces the white noise."
"PagerDuty helps you bifurcate teams and redirect alerts to specific teams"
"The initial setup is straightforward."
"It integrates with multiple applications and is highly customizable, with policies, escalation procedures, and an event routing tool that ensures contacting the right person."
"PagerDuty let us set up rosters based on our shifts. We could assign a hierarchy for how the calls should be escalated and the number of times the call will be transferred between people before it is answered. It makes it easy to access an agent via mobile phone."
"I'd rate the solution ten out of ten."
"The most valuable features of PagerDuty are customization, access, policies, and different rules regarding the path of escalation. Additionally, it's easy to use and create overrides. For example, if you all are on a call for one week each, but somebody wants to go on PTO, the team needs to swap shifts in PagerDuty. This is easy to do by creating overrides to switch up the set schedules. It's very user-friendly in that aspect. It works well for monitoring and alerting."
"The most valuable feature is the phone app that allows us to send notifications without the additional fees when sending by SMS or phone calls."
"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 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."
"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 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 solution's most valuable feature is its ability to fix things quickly."
"Temporal allows retryability for different workflows whenever they fail. It helps ensure idempotence and that things get done."
"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."
 

Cons

"The On-Call Teams feature could be better in terms of levels of conditions related to which team or member should get the responsibility of handling a matter or incident."
"Because of the way you have to structure the rosters, if an engineer has to go on leave (or something), you can't just go in and reassign/take this person out of all of the different rosters that they're in. You have to go into each of the rosters and take them out. There might be a roster for business hours, after hours rotation, and monitoring deployments. Each time we need to take an engineer out of the pool, e.g., if they're sick or on leave, then we have to go and touch all of those rosters, updating and replacing them. Whereas, if we could just take the person out and have it automatically fill in the rostering, then that would make life a lot easier for managing it."
"The biggest area for improvement with PagerDuty is noise suppression. There have been a handful of incidents through our use of PagerDuty over the years where one incident may lead to 30 to 50 pages because you're monitoring all these different things, and each thing is an individual page. There should be the ability to set up paging tiers and group correlations between some of the different pages. That is something that would be really valuable. We should be able to say this one page may have a group or a tree of effective other pages that may tier off of it. So, if you see those pages independently, go ahead and alarm, but if you see this plus that, don't do that."
"PagerDuty can improve the integration with Terraform."
"PagerDuty's webhooks need some improvement."
"I am not a direct end user of PagerDuty. It's hard to consider its shortcomings in that sense."
"Operations are somewhat limited by their integration package. For example, integrating with Jira was problematic until they updated to a better plug-in."
"It is a very non-customizable product, so you cannot add things like root cause analysis or the classification of incidents based on the area where you are getting more incidents. For example, if you're getting a lot of database issues, that may be an are you want to probe."
"Temporal images aren’t FIPS compliant, and we have to be FIPS compliant."
"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."
"Sometimes it scales kind of badly, but it depends on the process of our products."
"I don't like the limitations on data flow, particularly the difficulty of passing large amounts of data between different activities."
"Developers often mention the desire for a more intuitive visualization of workflow states."
"We previously faced issues with the solution's patch system."
"Temporal doesn't have built-in data storage to store the state of the ongoing execution."
 

Pricing and Cost Advice

"The cost is quite high. But if you want to get a full-featured application and you have a big team..."
"If we wanted phone calls or additional SMSs, we would have to pitch up for those. They give us so many per month per user, then we have to pay extra if it goes over that."
"There is a license needed to use PagerDuty."
"The price is very high."
"The solution is paid on a monthly basis and represents about 1% of the platform's budget."
"Licensing costs are around $700 a month, and the only additional costs, are phone costs in some instances."
"The cost is based on the package you select."
"PagerDuty has monthly and yearly licenses available, the costs of which can get quite high if you have a large number of users."
"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."
"The savings weren't as big as we initially expected, but they were pretty great from a developer's perspective."
report
Use our free recommendation engine to learn which Process Automation solutions are best for your needs.
846,617 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
21%
Financial Services Firm
13%
Manufacturing Company
7%
Healthcare Company
6%
Financial Services Firm
27%
Computer Software Company
18%
Retailer
9%
Manufacturing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about PagerDuty?
The product easily integrates with other solutions.
What is your experience regarding pricing and costs for PagerDuty?
The solution was expensive, but if all its features were utilized, it was considered worth the cost. The tier-based pricing model was cumbersome, and there was a desire for a service-based catalog ...
What needs improvement with PagerDuty?
Everything can always be better. Operations are somewhat limited by their integration package. For example, integrating with Jira was problematic until they updated to a better plug-in. The ability...
What is your experience regarding pricing and costs for Temporal?
Temporal OSS is expensive in infrastructure, but it brings back the reliability that companies need.
What needs improvement with Temporal?
The actual user interface is still in its early stages. It’s very basic. Users don’t really have a complex permission model yet. Users don’t really have ways to automate things like, for example, p...
What is your primary use case for Temporal?
We [my company] use it to run a large workload. We have a set of security scans we want to perform, and we distribute them over a full day, that’s over 24 hours. We use it to orchestrate all the st...
 

Overview

 

Sample Customers

40% of the Fortune 100 TrustPagerDuty. Customers include: Slack, Intuit, Zendesk, Panasonic, Pinterest, Airbnb, eHarmony, McKesson, Comcast
Information Not Available
Find out what your peers are saying about PagerDuty Operations Cloud vs. Temporal and other solutions. Updated: April 2025.
846,617 professionals have used our research since 2012.