PagerDuty

Name: PagerDuty
Brand: PagerDuty
Rating: 4.5 (1569 reviews)

Leader

The no-code, cloud workflow automation platform empowering people to digitize business operations.

Est 2009|Valuation $1.4B|Raised $410.5M|129 Ref Customers

LinkedIn 67K|Web traffic 1.6M|FTEs 1,155|HQ San Francisco, California, US

MarketsSecurity Information and Event Management (SIEM)IT Service Desk (ITSM)Incident Management & On-Call Observability Platform Incident Management & On-Call

Published Oct 24, 2026

01Common complaints

1. Small teams (e.g., 2–5 engineers) with low incident volume - Seat-based pricing and formal schedule design may be disproportionate to needs; built-in alerting from monitoring vendors or simpler tools may suffice. 2. Organizations primarily optimizing for cost-per-seat - Community feedback often highlights cost concerns when advanced features or broad access are required. 3. Teams that prioritize Slack-first incident coordination - Platforms designed primarily for Slack-centric workflows may provide a more integrated experience for those teams. 4. Environments that require guaranteed offline or redundant paging paths - If the notification pipeline cannot tolerate vendor downtime, organizations should consider redundant mechanisms in addition to any single vendor solution.

Deal disqualifiers (poor fit)

Organizations that are highly cost-sensitive and need only basic paging
Organizations seeking a primarily Slack-native experience with minimal context switching
Very small teams unable to sustain primary/secondary rotations or similar scheduling patterns

Known limitations (publicly observable)

Pricing and add-on creep can increase total cost beyond initial expectations.
Dependence on vendor uptime: outages in the vendor platform can affect incident creation and notification delivery.
Small-team rotation constraints: headcount expectations for scheduling can be difficult for very small teams.

Roadmap / "What’s new"

PagerDuty maintains a "What’s New" page. Procurement teams should confirm which features are generally available versus in beta and which tiers include specific capabilities.

Source: https://www.pagerduty.com/whats-new/

Security/compliance gaps

No specific compliance gaps were confirmed in publicly accessible sources. Organizations should validate HIPAA/BAA availability and data residency options for their required plans.

02Why they buy

Capabilities supported by market feedback

Configurable alerting and routing engine commonly used as a paging backbone in many organizations
Broad integration catalog according to vendor statements

Areas where competitors may have an advantage

Slack-native incident collaboration and in-chat workflow models offered by some newer vendors
Simpler packaging and more transparent pricing from vendors that emphasize bundled plans
Potentially lower cost for limited/basic paging needs, depending on organizational scale and required features

03Field reports

Review platform snapshot (what users tend to note)

Across major review sites, common positive themes include:

Reliable alerting and escalation for notifying designated responders
A broad catalog of monitoring and ITSM integrations
Scheduling and on-call workflows described by users as feature-rich and configurable

Review sources (accessed):

G2 product and seller pages
TrustRadius product reviews
Gartner Peer Insights listing

Common negative themes (what users criticize)

Recurring criticisms from community discussions and reviews include: - Cost concerns, particularly for smaller teams or when additional features are required - UI/UX complaints from some users who prefer newer interfaces - Alert fatigue and the need for careful event-rule and orchestration design - Mixed reports on support experience relative to price expectations - Sensitivity to vendor outages due to PagerDuty's role in the notification pipeline

Direct quotes (community) — positive & negative

Representative comments from public discussion forums (these are opinion-based and time-dependent): - "Biggest problem with pager duty is that it enables corporations to take advantage of employees by forcing them to work around the clock…" (community forum) - "PagerDuty and several other competitors seem insanely expensive for the value they actually provide." (community forum) - "pagerduty went down… no incident creation, half the notifications never showed up…" (community forum) Note: Public forums are not controlled review environments; comments can be subjective, context-poor, and time-dependent.

Why customers choose PagerDuty (inferred from review themes)

Requirement for configurable paging and escalation with broad integration coverage
Desire for a commonly used tool that aligns with enterprise procurement patterns
Consolidation of multiple teams onto a single incident/on-call system

Why some customers leave or evaluate alternatives

Budget considerations and published per-seat pricing at scale
Preference for Slack-native or integrated incident coordination platforms
Desire for a more modern UI or different workflow philosophies
Procurement or packaging issues around annual commitments and sales processes

Vendor-published outcomes (treat as vendor-reported until validated)

PagerDuty's website presents ROI and downtime reduction claims based on vendor-commissioned or vendor-curated studies. These materials can be useful but should be validated through independent references or direct customer interviews where possible.

Forrester TEI (vendor-commissioned) — evaluation guidance

A Total Economic Impact (TEI) report exists for the PagerDuty Operations Cloud. TEI and similar vendor-commissioned studies can be informative but are not independent audits. When assessing such reports, review sample size, assumptions about the composite organization, baseline comparisons, and cost items that may have been excluded.

Customer story example (vendor site)

PagerDuty hosts customer stories (for example, a nonprofit customer case). These narratives illustrate use cases but are curated and may not include counterfactual analysis.

Third-party case study where PagerDuty is the customer

Sumo Logic published a case study describing PagerDuty as a Sumo Logic customer; this type of material can provide insight into PagerDuty's operational scale and tooling choices but is not an independent validation of vendor claims about product impact.

04Best fit

Company size (practical ranges)

Typical fit: organizations with anywhere from a few hundred to many thousands of employees operating 24/7 systems and multiple engineering/service teams with recurring incident activity.
Potential fit for smaller teams: may be appropriate where uptime risk is high, but cost and rotation constraints can make the product challenging for very small teams.

Industries/verticals

Common verticals include:

SaaS and cloud services
E-commerce
Financial technology
Media and streaming
Other enterprise IT operations organizations with strict uptime objectives

Roles/personas

Decision makers: VP of Engineering, Head of SRE/Platform, CIO/IT Ops Director
Administrators: SRE leads, DevOps managers
End users: on-call engineers, incident commanders, NOC staff, support escalation managers

Qualification criteria (good fit)

Requirement for complex routing, escalation policies, and ownership mapping across many services
Established or planned incident response processes and a need for a durable system of record
A need for broad integration coverage and enterprise capabilities

05The pitch

What the product does (objective value proposition)

PagerDuty is a SaaS operations platform focused on incident management and on-call alerting. Core features include routing alerts from monitoring, security, and customer-support systems to designated responders, coordinating escalation policies and schedules, and supporting incident response workflows (acknowledgement, mobilization, communications, post-incident review). The company has expanded positioning to include additional capabilities described by the vendor under an "Operations Cloud" umbrella, including AIOps, automation, analytics, and generative AI assistance.

Target market and market positioning

- Primary buyers/users: SRE/DevOps/IT Ops leaders, NOC teams, incident commanders, platform engineering, and in some organizations, SecOps and customer support operations. - Typical organization profile: Mid-market to enterprise organizations with 24/7 services, multiple teams, and significant incident volume or complex routing requirements. - Positioning: PagerDuty is positioned for enterprise use and is commonly used as a de facto standard for paging and escalations in many organizations.

Get a comprehensive analysis of PagerDuty including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →