PagerDuty

What PagerDuty actually is

PagerDuty is the incumbent of incident management: an on-call scheduling, alert routing, and incident response platform that turns monitoring alerts into phone calls, pushes, and SMS messages that wake the right human. It started in February 2009 as a side project of three ex-Amazon engineers in Toronto (first commit on the 18th, beta on Hacker News that August), was incorporated in Delaware in May 2010, and is now a New York Stock Exchange-listed company headquartered in San Francisco with roughly $494 million in annual recurring revenue as of fiscal year-end January 2025. That history matters for this category, because the value of a pager is mostly the reliability of the pipe: PagerDuty has spent more than a decade making sure the message arrives.

The product surface is broad but centers on four things: alert aggregation from monitoring and ticketing tools, on-call schedules with escalation policies, incident coordination (roles, status updates, stakeholder communication), and automation — runbook automation, event intelligence, and an AI layer sold as PagerDuty Advance. There are also adjacent products: Jeli for post-incident analysis, and workflow automation tooling. On ServerSpotter it lives in /category/monitoring-hosting because it is the tool that sits beside the infrastructure we compare — not the infrastructure itself.

Two published numbers define the customer base: 849 customers paying over $100,000 in ARR as of January 2025, and total paid customers of roughly 15,000. Our database claimed "25,000+ organizations"; we could not verify that figure against company reporting and have corrected it.

Pricing: what you really pay

PagerDuty sells per-user subscriptions in four tiers, with published list prices:

• Free: $0, up to 5 users, unlimited email and push notifications, plus 100 international phone/SMS notifications a month for the whole account.
• Professional: $21 per user per month billed annually, $25 billed monthly.
• Business: $41 annually, $49 monthly.
• Enterprise: custom pricing via sales.

The annual discount is exactly 16% on both paid tiers — $48 per user per year saved on Professional, $96 on Business. Those check out against the monthly rates. Business costs almost exactly double Professional at any headcount, and what the extra money buys is service dependency mapping, richer analytics, unlimited API access, single sign-on (per one source's tier table; another lists SSO as a Professional feature — worth confirming in your quote), and a larger PagerDuty Advance allowance. Professional already includes unlimited schedules, escalation policies, and global SMS/voice.

The structural detail that matters: the free tier ends at five users, and when you add a sixth, the entire account converts to paid. Six engineers on Professional annual is $126 a month, $1,512 a year. Ten is $2,520 a year; fifty is $12,600 on Professional and $24,600 on Business. This is where the "expensive at scale" reputation comes from — not the unit price in isolation, but the fact that every person who can be paged consumes a full license. The main lever for controlling the bill is stakeholder licensing (reported at roughly $150 per 50 stakeholders a month) so that read-only stakeholders do not carry responder seats.

Two fine-print items. PagerDuty Advance AI actions are allocated as one-time bundles (1,000 on Professional, 5,000 on Business, 20,000 on Enterprise) rather than monthly allowances, so they behave like a trial. And the SLA explicitly does not cover the Free plan or trials.

Performance & infrastructure

This is a SaaS product, so "performance" means delivery reliability and hosting footprint. PagerDuty publishes a Standard Service Level Agreement with concrete commitments: once an incident triggers, the first responder notification is delivered within a five-minute notification delivery period for 99.9% of notifications in a calendar month; the web application's acknowledgement and resolution functionality is available 99.9% of the month; Runbook Automation commits 99.5% and Jeli 99.9%. Misses earn service credits under the agreement. For context, competitors market 99.99% notification commitments — that gap permits roughly 43 minutes of degraded delivery a month versus about 4, and it is the sharpest honest criticism of the platform's paperwork, whatever its real-world record.

Hosting is region-selectable at account creation. The US service region runs across AWS US West (Northern California), AWS West (Oregon), and US East (Ohio); the EU service region runs across AWS EU Central (Frankfurt) and AWS EU West (Ireland), with Frankfurt as the primary facility since the EU region reached general availability. EU region selection is permanent for an account, and integrations that do not target EU endpoints can route API traffic through US infrastructure — a detail compliance teams should audit before signing. There is no Asia-Pacific service region.

Operational transparency is good: a public status page runs 24/7, and the platform's reliability record over the past decade is the quiet argument in its favor. We have not tested PagerDuty's delivery times ourselves; we would not claim to. What we can say is that its market position was built on notification reliability, and that incumbent status shows in the integration catalog and the maturity of the mobile apps.

One caveat on how to read the competitive claims around this product: rival vendors quote PagerDuty's SLA number rather than its track record, and PagerDuty's marketing quotes customer logos rather than its per-seat bill. Both framings are marketing. Our approach is to compare the contract text (what is promised and what credits you get), the published list price at your headcount, and whether the tool's incident history has been public and boring — boring is the compliment here.

Where it falls short

Price is the first and loudest complaint, and it is structural. Per-seat billing punishes teams where everyone rotates on call, and the cliff at user six turns a free habit into a four-figure annual line item overnight. For a five-person startup, the free plan is genuinely one of the best deals in the category; for a fifty-person engineering org, the annual bill can exceed what some companies pay for their entire monitoring stack.

Second, the SLA is thin for a pager. 99.9% notification delivery inside a five-minute window is a modest contractual promise for a product whose entire job is waking people up, and the SLA's exclusion of the free plan means the smallest teams have no contractual recourse at all. We do not think PagerDuty is unreliable — but we think the paperwork prices in more slack than a modern competitor's.

Third, the platform has grown by acquisition and addition, and it shows: Jeli, Runbook Automation, and the AI features are separate surfaces with separate limits and separate SLAs, and the pricing page has enough fine print that quotes need reading line by line. Teams that want a single, simple, Slack-native incident tool increasingly find the product heavy, and smaller competitors differentiate on exactly that.

The migration math is worth spelling out, because on-call tools are sticky. Once schedules, escalation policies, and a few hundred integration hooks live in PagerDuty, moving means re-creating rotations and re-pointing alert sources, and doing it without dropping a page. Vendors know this, which is why list prices rarely move and why we advise teams to trial two tools with real rotations before committing — the switching cost starts on day two, not year two.

Who should pick this

We pick PagerDuty when on-call reliability is the business's most critical automation and the budget exists: organizations with follow-the-sun rotations, compliance requirements around incident records, and 849-class spend tolerance not required but common in its customer base. The integration catalog is deep, the escalation machinery is the most battle-tested available, and the free plan is our pick for a small team's first pager — five users, real escalation, no credit card.

We would not pick it for a large rotation where every responder needs a paid seat and the budget is tight; incident.io, Opsgenie, or open-source Alertmanager-plus-Grafana stacks deserve a look first. And EU organizations with strict data-flow requirements should provision the EU region deliberately and audit their integrations' endpoints on day one.

Key takeaways

• The on-call incumbent since 2009: alert routing, escalation policies, incident coordination, and automation in one platform.
• Free plan covers 5 users with 100 phone/SMS notifications a month; adding a sixth user converts the whole account to paid.
• Paid tiers: Professional $21/user/month and Business $41 billed annually (16% discount vs monthly), Enterprise quoted.
• Published SLA: 99.9% notification delivery within 5 minutes, 99.9% web app availability; free plans excluded.
• US and EU service regions on AWS (Frankfurt/Ireland for EU); no APAC region; region fixed at signup.
• Our pick for reliability-critical on-call with budget; the free plan is our pick for teams under five people.

Sources

• https://alertping.com/blog/how-much-does-pagerduty-cost
• https://woopy.dev/blog/pagerduty-pricing
• https://www.pagerduty.com/standard-service-level-agreement/
• https://support.pagerduty.com/docs/service-regions
• http://pagerduty.com/blog/company/decade-of-duty
• https://www.sec.gov/Archives/edgar/data/1568100/000162828019003003/pagerdutys-1.htm
• https://businesswire.com/news/home/20250313210792/en/PagerDuty-Announces-Fourth-Quarter-and-Full-Year-Fiscal-2025-Financial-Results
• https://incident.io/blog/pagerduty-gdpr-compliance-data-residency