PagerDuty
by PagerDuty · Incident management with on-call scheduling and 750+ tool integrations
BenchRank score
Screenshots of PagerDuty
Homepage
Overview
PagerDuty is an incident management platform covering detection, on-call routing, response and post-incident review. Alerts from integrated monitoring tools are routed to responders through on-call schedules and escalation policies, with response handled in Slack, Microsoft Teams, web or mobile. Paid add-ons layer on AI agents and ML-based alert noise reduction.
- Best for
- Engineering and ops teams needing on-call scheduling and incident response across many tools.
- Pricing
- Free for up to 5 users, then $25/user/month (Professional) or $49/user/month (Business) billed monthly, with custom-priced Enterprise and separately priced add-ons.
- Runs on
- WebiOSAndroidSelf-hosted
Strengths and trade-offs
Strengths
- 750+ out-of-the-box integrations, including on the free plan
- Runs incident response inside Slack or Microsoft Teams
- Free plan for up to 5 users; 14-day trial needs no credit card
- Open APIs and MCP with bi-directional sync to other systems
Trade-offs
- AI agents require the Advance add-on, from $415/month
- AIOps noise reduction costs extra, starting at $699/month
- Free plan allows only 1 schedule and 1 escalation policy
- Conditional workflows and full chat actions are Enterprise-only
How PagerDuty markets itself
A structured read of the promise, proof and page design on PagerDuty’s captured homepage.
Homepage capture
“Move fast and MAKE SURE it works.”
- Angle: Outcome / benefit-led
- Hero: Product screenshot
Pricing
Published plans and prices from PagerDuty’s own pricing page.
How this score is made up
Each dimension is scored out of 100 and combined into the headline score using fixed weights.
MCP support
Whether an agent can drive the product through the Model Context Protocol, and how much setup that takes.
API quality
Public API surface: machine-readable spec, official SDKs, documented auth, errors, rate limits and versioning.
Documentation
Publicly reachable docs — coverage, freshness, code samples and machine readability.
Agent friendliness
How readable the site is to an automated client: llms.txt, structured data, server-rendered content, crawler access.
Pricing transparency
Whether real prices are published, self-serve signup exists, and usage costs are knowable without a sales call.
Changelog
A public, dated record of what shipped and when — the clearest signal that a product is still alive.
Marketing site structure
Whether the site answers a buyer's questions: clear positioning, the pages that matter, and accessibility.
Page speed
How fast the site loads for real visitors: Chrome UX Report 75th-percentile LCP, INP and CLS, with a Lighthouse mobile run standing in where a site has too little traffic for field data.
Operational trust
Status page and incident history, security disclosure, compliance and data-processing documentation.
Measured, but not part of the score
Useful to know, but not a mark for or against the product — so these do not affect the ranking.
Openness
Source availability, self-hosting, data export and open standards. Scored and shown, but not part of the composite — paid SaaS is not worse for being paid SaaS.
Maintenance
Release cadence and repository activity. Scored and shown, but not part of the composite — it is only measurable for open repositories.
This doesn’t look right — report a problem with PagerDuty’s score
Where this comes from
The PagerDuty pages BenchRank reads when it scores the product — its documentation, release notes, status and security pages, and its repository where there is one.
Alternatives in Monitoring & Observability
Ranked 1
87.4 — BenchRank score out of 100openstatus
OpenStatus · Open source status pages with uptime monitoring from 28 regions
Best for: Teams that need a public status page and uptime checks while working towards SOC 2.
Ranked 2
86.7 — BenchRank score out of 100OneUptime
OneUptime · Open-source observability and incident management on one platform
Best for: Teams wanting monitoring, on-call, status pages and observability on one open-source platform
Ranked 3
83.1 — BenchRank score out of 100Sentry
Sentry · Error tracking and application performance monitoring for developers
Best for: Development teams wanting error monitoring, tracing and session replay tied to one trace
Is this your product?
Claim PagerDuty to manage its profile. Claiming lets you suggest edits to the descriptive fields — it never changes scores or rankings.