Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 3 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by PagerDuty, Inc. · www.pagerduty.com

Compare with ilert → Report an error on this page Is this your product? →

Link to this page

PagerDuty: AI-assisted analysis on whats-best.ai PagerDuty: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

PagerDuty at a glance

Vendor
PagerDuty, Inc.
Headquarters
Incorporated in the United States source, captured 6 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 6 Nov 2026
Free plan
Yes, per the vendor’s own page source, captured 6 Nov 2026
Panel verdict
The AI panel rates PagerDuty 3/5, the mean of 6 judges. PagerDuty, an on-call and incident management platform, scored strongest on incident response — the only category to reach 8 — and weakest on pricing transparency and sovereignty, each dipping to 5. how scores are made
As of
Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources

PagerDuty alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The panel's verdict

PagerDuty, an on-call and incident management platform, scored strongest on incident response — the only category to reach 8 — and weakest on pricing transparency and sovereignty, each dipping to 5. Incident response is documented end to end: incidents declared from Slack, the web and mobile apps, email or the API, a filterable timeline, Incident Commander and Customer Liaison roles, internal and external status pages. Scores for on-call scheduling and alerting and routing clustered at 6-7, on delivery over push, phone, SMS, email, Slack and WhatsApp, five documented grouping techniques and live call routing through the same schedules. Pricing is published in detail — Free at $0 per year, Professional at $25 per user per month or $21 annually, platform fees from $2,800 to $48,000 per year, Ultimate at Custom Pricing — yet we found no public information on prices for the separately purchased add-ons or included SMS and voice volumes. Sovereignty ranged 5-7 as judges weighed a US contracting entity and US-based AI providers against published Standard Contractual Clauses, transfer impact assessments and an EU service region. The disagreement check flagged nothing.

Report an error

Speaks for it

  • Incident declaration from Slack, the web and mobile apps, email or the API, with a filterable timeline and post-incident reviews through Jeli analysis.
  • Alert grouping documented across five named techniques, with auto-pause for transient alerts, suppression and live call routing that follows the same schedules.
  • Public pricing lists Free at $0 per year, Professional at $25 per user per month or $21 annually, and platform fees of $2,800, $12,000 and $48,000 per year with stated seats, Signal Intelligence Events, AI Actions and Live Call Routing lines.
  • Compliance artifacts include SOC 2 Type II, ISO 27001 and FedRAMP Low authorization, a public status page with history and an assurance portal for reports on request.
  • A published data processing addendum incorporates the EU Standard Contractual Clauses with transfer impact assessments, an EU representative is named, and customers choose a US or EU service region.

Report an error

Held against it

  • Ultimate carries Custom Pricing, and we found no public information on prices for the separately purchased add-ons or per-country SMS and voice rates.
  • The contracting party is PagerDuty, Inc. of San Francisco under California law, and the generative AI features run on AWS, Google, Microsoft and OpenAI in the United States.
  • Audits under the data processing addendum are limited to once annually, on site, with the customer reimbursing PagerDuty at then-current professional services rates.
  • We found no public information on SCIM provisioning, audit logs, a Terraform provider or documented migration from another tool.
  • We found no public information on exporting on-call hours per person for pay and working-time rules.

Report an error

Best for

  • You need incident response you can run from Slack, with declaration, roles like Incident Commander and Customer Liaison, status pages and post-incident reviews.
  • You must assemble an audit file from public artifacts: SOC 2 Type II, ISO 27001, FedRAMP Low authorization, a public status page and an assurance portal.
  • You can accept a US contracting entity provided the transfer chain is documented, with published SCCs, transfer impact assessments and a choosable EU service region.
  • You want published entry pricing, with a free tier at $0 per year and a 14-day trial with no credit card required.

Report an error

Avoid if

  • You must budget a complete annual cost from public pages alone: Ultimate is Custom Pricing and AIOps, PagerDuty Advance, Runbook Automation, Status Pages and Live Call Routing are purchased separately.
  • Your procurement requires a European contracting entity or European processing end to end: the agreement is with PagerDuty, Inc. of San Francisco under California law and the generative AI subprocessors are US-based.
  • You need audit rights on your own terms: audits are once annually, on site, and you reimburse PagerDuty at then-current professional services rates.
  • You plan to run a full rota on the Free plan: it allows five users, one schedule and one escalation policy.

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.

On-call schedules, rotations & escalation

Show reasoning
How this is scored

Who is on call and what happens when nobody answers: schedules with daily, weekly and custom rotations, layers and follow-the-sun hand-offs across time zones, overrides, swaps and holiday cover, escalation policies with timeouts, repeat and fallback levels, round-robin and team escalation, calendar export and sync, reminders before a shift, on-call reports and hours exported for on-call pay and working-time rules, and a mobile app that shows the shift and lets a responder hand it over.

0 — No schedules or escalation of any kind; alerts go to a fixed list of people.

3 — A simple weekly rotation and one escalation step; overrides, layers, time zones and on-call reports are basic or not described.

5 — Schedules with several rotation types and layers, overrides and swaps from the app, escalation policies with timeouts and several levels, time-zone handling, calendar export, shift reminders, and a report of who was on call when.

8 — Follow-the-sun and multi-team schedules, round-robin and conditional escalation, coverage gaps flagged before they happen, schedules and policies managed as code or by API, and on-call hours exported per person for pay and working-time rules, all documented.

10 — Scheduling a large organisation runs on: every feature above with fairness and fatigue reports, rest-period rules enforced or warned, schedules imported from HR or workforce tools, and every scheduling limit documented per plan.

Report an error

The SRE Lead

Escalation mechanics are documented in real depth: layered schedules with precedence, round-robin assignment, easy shift overrides, handoff notices up to 48 hours before a shift, reminders, and calendar export to Outlook, Google Calendar and iCal, plus hard limits like twenty rules and nine repeats per policy with timeout minimums. We found no public information on exporting on-call hours per person for pay and working-time rules, on coverage gaps flagged before they happen, or on schedules managed as code beyond a listed FAQ question. 2 3 6 17 18

Report an error

The IT Operations Manager

Custom schedules, rotations and layered schedules with the lowest layer taking precedence are documented, plus escalation timeouts I can set down to a one-minute minimum with a single target and three minutes with several, repeated up to nine times across up to twenty rules — enough to ring the deputy after ten minutes. Calendar export to Outlook, Google and iCal, handoff warnings up to 48 hours ahead, overrides, reminders and round-robin assignment are all written down; we found no public information on exporting on-call hours per person for pay and working-time records, and follow-the-sun patterns appear only as support questions. 2 3 6 17 18

Report an error

The MSP NOC Lead

Schedules with layers, unlimited schedules and escalation policies on paid plans, easy shift overrides, calendar export to Outlook and iCal, and handoff reminders up to 48 hours ahead cover how I would build a night rota per key account; escalation policies with adjustable timeouts, up to 20 rules, nine repeats and optional round-robin assignment are well documented. We found no public information on exporting on-call hours for pay or working-time rules, and coverage-gap handling is only described as skipping to the next rule with an on-call responder, so I stop short of the top bands. 2 6 17 18

Report an error

The ICT Risk Officer

Rotations, layer precedence, overrides, shift revert, reminders, handoff notices up to 48 hours ahead and calendar export to Outlook, Google Calendar and iCal are documented, alongside escalation policies with up to 20 rules, adjustable timeouts, up to nine repeats and round-robin assignment; the FAQ also covers multi-time-zone schedules, shift swaps, conflict detection and managing schedules through an API or infrastructure-as-code. We found no public information on on-call hours exported per person for pay and working-time rules, or on fairness and fatigue reporting, which a German works council would ask for. 17 6 18 2

Report an error

The Engineering Manager

Schedules with layers, rotation templates, easy shift overrides, revert, calendar export to Outlook, Google Calendar and iCal, on-call handoff reminders up to 48 hours ahead, and escalation policies with up to 20 rules, adjustable timeouts and up to nine repeats are all documented, and the on-call pages also cover multi-timezone schedules, shift swaps, conflict detection, schedule templates and managing schedules by API, with round-robin assignment behind a feature gate. We found no public information on exporting on-call hours per person for payroll and working-time rules, nor on fatigue or rest-period warnings — both essential under our works council agreement. 2 3 6 17 18

Report an error

The Skeptic

Schedules with layers and precedence rules, shift overrides, calendar export to Outlook, Google Calendar and iCal, hand-off reminders up to 48 hours ahead, round-robin assignment, and escalation policies with up to 20 rules, nine repeats and adjustable timeouts from one minute up are documented. Multi-time-zone schedules, shift swaps, templates and conflict resolution appear on the features page only as FAQ question titles rather than behaviour we could read, and we found no public information on exporting on-call hours per person for pay and working-time rules or on schedules managed as code. 2 3 6 17 18

Report an error

Alert delivery, routing & noise reduction

Show reasoning
How this is scored

Whether the alert reaches a human and only the right one: notification by push, SMS, voice call, email and chat, critical alerts that override do-not-disturb on iOS and Android, personal notification rules with retries and fallbacks, acknowledgement by app, SMS reply or keypad, delivery receipts, live call routing for a hotline, routing rules by service, severity, payload and time, deduplication, grouping and correlation of related alerts, suppression and maintenance windows, heartbeats for silent failures, and inbound email and webhook endpoints.

0 — Sends no alerts to people; a dashboard or log viewer only.

3 — Push and email notifications with acknowledgement; SMS, voice, routing rules and noise reduction are basic or not described.

5 — Push, SMS, voice and email with personal notification rules and retries, critical alerts on mobile, acknowledgement from the app or by phone, routing by service and severity, deduplication, and maintenance windows.

8 — Alert grouping or correlation with its logic documented, routing on payload fields and time conditions, delivery receipts and a notification log per alert, live call routing, heartbeat monitoring, suppression rules, and the countries and channels where SMS and voice are delivered stated.

10 — Delivery that is evidenced, not promised: redundant SMS and voice carriers named with automatic failover, delivery statistics published, AI or rule-based noise reduction with measurable results, and every notification limit per plan documented.

Report an error

The SRE Lead

Push, phone, SMS, email and WhatsApp all land, with acknowledge, resolve and escalate from the phone keypad or by SMS reply, bundling on every channel, live call routing into the same schedules, and alert grouping whose logic is documented across five named techniques plus auto-pause and suppression — the noise-reduction story is the strongest part. We found no public information on heartbeat monitoring, delivery receipts, or the countries and channels where SMS and voice are delivered. 2 4 6 19 20 21

Report an error

The IT Operations Manager

Push, phone, SMS, email and WhatsApp delivery with keypad control — acknowledge, resolve or escalate from the phone, or acknowledge by SMS reply — is exactly the plant-floor behaviour we need, and bundling, notification delays and test notifications are documented. Alert grouping is documented with five named techniques plus auto-pause, suppression and a maintenance-mode reference in the incident lifecycle, and live call routing brings inbound calls onto the same schedules; we found no public information on delivery receipts, heartbeat monitoring, or which countries SMS and voice reach. 2 4 19 20 21

Report an error

The MSP NOC Lead

Push, phone, SMS, email, WhatsApp and Slack delivery with acknowledgement by app, phone keypad or SMS reply, notification bundling and delays, suppression, maintenance mode, live call routing that follows the schedules, and alert grouping with five documented techniques gives me the routing-by-service behaviour I need for sixty customers. We found no public information on delivery receipts, heartbeat monitoring for silent failures, or the countries where SMS and voice are delivered, which is what separates a strong delivery story from a fully evidenced one. 2 19 20 21

Report an error

The ICT Risk Officer

Push, phone, SMS, email and WhatsApp delivery are documented channel by channel, with acknowledgement by app, by phone keypad (including bulk acknowledge and resolve) and by SMS reply, plus live call routing that sends inbound callers through the on-call schedules and turns voicemails into incidents. Alert grouping is documented in five techniques with its logic explained, auto-pause quiets transient alerts, and the incident timeline records every notification sent. We found no public information on delivery receipts, heartbeat monitoring, or the countries and channels where SMS and voice are delivered. 19 20 21 2

Report an error

The Engineering Manager

Push, phone, SMS, email and WhatsApp delivery with acknowledgement by phone keypad or SMS reply, bundling across all channels, delays in personal notification rules, suppression and maintenance mode, and live call routing that turns voicemails into incidents are documented, and alert grouping has five named techniques with auto-pause for transient alerts, while each incident's timeline logs the notifications sent. We found no public information on heartbeats for silent failures, delivery receipts, critical alerts overriding do-not-disturb on mobile, or the countries where SMS and voice are delivered. 2 19 20 21 4

Report an error

The Skeptic

Delivery runs over push, phone, SMS, email, Slack and WhatsApp with acknowledgement by SMS reply or phone keypad, notification delays and bundling, alert suppression, maintenance mode, auto-resolve, and five documented alert-grouping techniques; live call routing sends inbound callers through the same schedules and escalation policies, and the vendor claims alert noise cut by 91%. We found no public information on delivery receipts, heartbeats for silent failures, or the countries and channels where SMS and voice are delivered, and the telecom sub-processors — Twilio, Vonage, MessageBird — are named in a list with no failover commitment. 2 4 6 15 19 20 21

Report an error

Incident response, status pages & post-incident review

Show reasoning
How this is scored

What happens once the alert is a real incident: declaring an incident from Slack, Microsoft Teams or the app, a dedicated channel and video bridge, incident roles and commander, severities and incident types, runbooks, tasks and automated workflows, stakeholder updates, public and internal status pages with subscribers, a timeline, post-incident reviews and postmortem templates with follow-up actions, analytics such as MTTA and MTTR, and AI features that summarise, suggest causes or draft the review.

0 — No incident record of any kind beyond the alert itself.

3 — An incident list with status and notes; channels, roles, status pages and post-incident reviews are basic or not described.

5 — Incidents declared from chat or the app with severities, a Slack or Teams channel created, incident roles, a timeline, a public status page, stakeholder notifications, postmortem templates, and MTTA and MTTR reports.

8 — Workflows and runbooks that automate the response, incident types with their own process, internal and public status pages with components and subscribers, follow-up actions tracked into Jira or Linear, service catalogue and dependencies, and AI summaries with their data handling described.

10 — A response process a regulated enterprise runs on: every feature above with major-incident and regulatory reporting templates, cross-team analytics and learning reviews, AI features documented with model provider, data handling and an opt-out, and every limit per plan stated.

Report an error

The SRE Lead

This is close to what I run on: declare an incident from Slack, the web app, mobile or the API; a filterable timeline per incident; roles like Incident Commander and Customer Liaison assignable to one accountable responder in Slack and Teams; public and private status pages from the Starter tier upward; post-incident reviews plus the Jeli analysis service; and GenAI features whose data handling is disclosed, with a stated choice and no customer data used for training. We found no public information on status-page subscribers, follow-up actions tracked into Jira or Linear, or a service catalogue with dependencies. 2 3 8 9 21 22

Report an error

The IT Operations Manager

Incidents can be declared from the web app, mobile app, Slack, email or the API, with a filterable timeline, priorities, customizable roles such as Incident Commander and Customer Liaison usable in Slack, Teams and workflows, post-incident reviews, analytics, and internal and external status pages counted per plan. Incident workflows and runbook automation exist, and the AI features are backed by a disclosure on request and a statement that no customer data is used for training; we found no public information on follow-up actions tracked into Jira or Linear. 3 4 8 9 21 22

Report an error

The MSP NOC Lead

Incidents declared from Slack, the app or by API with custom incident types, predefined Incident Commander and Customer Liaison roles plus custom roles, a filterable timeline, internal and public status pages with subscribers, post-incident reviews via Jeli, runbook automation and stakeholder communications are all documented, and the AI data handling states no customer data is used for training with customer choice offered. We found no public information on follow-up actions tracked into Jira or on MTTA and MTTR as reportable metrics, though analytics and a 70 percent MTTR reduction claim are published. 3 8 9 21 22

Report an error

The ICT Risk Officer

Declaration from Slack, the web and mobile apps, API and email, a filterable timeline recording statuses, actions and every notification sent, incident roles from Incident Commander to custom roles across web, Slack, Teams and workflows, post-incident reviews, Jeli analysis, internal and external status pages, stakeholder communications and incident workflows are documented, with custom incident types and tasks on the upper tiers. The vendor commits to customer choice on generative AI and states no customer data is used for training, with a fuller AI disclosure available on request. We found no public information on follow-up actions tracked into Jira or Linear, or on major-incident and regulatory reporting templates. 21 22 8 3 4

Report an error

The Engineering Manager

Incidents can be declared from Slack, the web and mobile apps, email or the API, with Incident Commander and Customer Liaison roles plus custom roles usable in Slack, Teams and workflows, severities, a filterable timeline, post-incident reviews and Jeli incident analysis, internal and external status pages, stakeholder communications, and incident workflows and runbook automation; the captured pages also state that no customer data is used for AI training, with a detailed AI disclosure available on request. We found no public information on follow-up actions tracked into Jira or Linear, subscribers and components on customer status pages, or MTTA and MTTR reporting. 3 8 9 21 22

Report an error

The Skeptic

Incidents can be declared from the web app, mobile app, API, email integration or Slack, with severities, a filterable timeline, custom roles such as Incident Commander and Customer Liaison usable across Slack, Teams and workflows, incident workflows with Runbook Automation, internal and external status pages, stakeholder communications and post-incident reviews. The AI agents carry a stated commitment that no customer data is used for training, with an AI disclosure available on request. We found no public information on follow-up actions tracked into Jira or Linear, on subscribers for customer status pages, or on MTTA and MTTR reporting beyond a marketing claim of 70% MTTR reduction. 3 4 8 9 21 22

Report an error

Integrations, API & administration

Show reasoning
How this is scored

How the tool fits the stack and the organisation: inbound integrations with monitoring and observability tools (Prometheus, Grafana, Datadog, Zabbix, Checkmk, PRTG, Azure Monitor, CloudWatch, Sentry), outbound integrations with chat, ticketing and ITSM tools (Slack, Microsoft Teams, Jira, ServiceNow, ConnectWise, Autotask), bidirectional sync, a documented REST API, webhooks and a Terraform provider, teams and services, roles and permissions, single sign-on (SAML or OIDC) and SCIM, audit logs, multi-tenant or customer separation for service providers, and migration help from other tools.

0 — No integrations and no administration beyond a single shared account.

3 — Email and webhook intake and a few named integrations; the API, roles and single sign-on are basic or not described.

5 — Dozens of named inbound and outbound integrations including Slack or Teams and Jira, a documented REST API and webhooks, teams with roles, two-factor authentication, single sign-on, and an import path from at least one other tool.

8 — Bidirectional ITSM and ticketing sync, a Terraform provider or configuration as code, SCIM provisioning, granular roles per team, audit logs, service-provider or multi-tenant set-ups, and API coverage of schedules, escalations and incidents documented.

10 — Administration that scales across many teams and customers: every setting reachable by API with parity stated, audit logs exportable to a SIEM, SSO enforced with SCIM, white-label or sub-account management for service providers, and documented migration from the major competitors.

Report an error

The SRE Lead

750+ native integrations, a documented REST API with versioning and scoped OAuth, bi-directional ServiceNow sync with CMDB table endpoints, and a free self-service developer programme mean the fit into a Prometheus-to-Slack stack is not in doubt. But we found no public information on a Terraform provider, SCIM provisioning, audit logs, multi-tenant setups for service providers, or migration help from other tools, and single sign-on appears on the captured pages only as a component name on the status page. 3 7 8 10 11 21 23 24

Report an error

The IT Operations Manager

A claim of 750-plus native integrations and open APIs sits beside a documented REST API with versioning and full ServiceNow enrichment endpoints, bi-directional ServiceNow field sync on the top plan, teams with roles and permissions for multi-team coordination, and single sign-on appearing on the vendor's own service list. For our estate we found no public information naming Checkmk or PRTG among the integrations, and none on SCIM provisioning, audit logs, a Terraform provider or migration help. 3 8 10 11 23 24

Report an error

The MSP NOC Lead

750-plus native integrations, a documented REST API with ServiceNow endpoints including bi-directional CMDB sync on the top tier, Slack and Microsoft Teams ChatOps, teams tied to escalation policies and a sign-in with SSO service give me most of the plumbing, though the captured pages never name Autotask or ConnectWise specifically. We found no public information on audit logs, SCIM provisioning, a Terraform provider, multi-tenant separation for service providers, or migration help from other tools — the last matters most to me as an MSP. 3 6 8 10 23

Report an error

The ICT Risk Officer

750+ native integrations are claimed with Slack and Microsoft Teams named, a REST API is documented with OAuth scopes, versioning and rate limits, ServiceNow CMDB enrichment endpoints exist, and bi-directional ServiceNow custom-field sync arrives on the top tier; teams, plan-based team fields and role administration are described. Single sign-on appears only as a line on the vendor's own status page, and we found no public information on audit logs, SCIM provisioning, a Terraform provider or documented migration from other tools. Before entering this tool in our ICT third-party register, the missing public information on audit logging is the part I would chase hardest. 3 6 8 10 23 24

Report an error

The Engineering Manager

750+ integrations including Slack and Microsoft Teams, a documented REST API with versioning, rate limits and scoped OAuth, teams with roles and permissions, and ServiceNow bi-directional custom field sync on the top platform tier are evidenced, and single sign-on appears as a live service on the vendor's status page. We found no public information on SCIM provisioning, audit logs, a Terraform provider, two-factor authentication details, or migration help from other tools. 3 8 10 11 23

Report an error

The Skeptic

"750+ native integrations" are claimed with Slack and Microsoft Teams named, the REST API is documented with versioning headers, scoped OAuth and rate limits, ServiceNow bi-directional sync with CMDB table endpoints is documented for the top tier, teams with roles and permissions are described, and single sign-on appears as a named service on the vendor's own status page. We found no public information on SCIM provisioning, a Terraform provider, audit logs, two-factor authentication or a documented migration path from another tool. 3 6 8 10 11 23 24

Report an error

Platform reliability, security & compliance

Show reasoning
How this is scored

Whether the pager works on the day everything else is down and holds up in an audit: an architecture independent of the customer's own cloud, multi-region or multi-zone hosting with failover, a stated availability or SLA with credits, the vendor's own public status page and incident history, delivery via redundant carriers, encryption in transit and at rest, security certifications (ISO 27001, SOC 2, BSI C5), penetration tests, data retention and deletion, audit trails, and what the vendor documents for DORA, NIS2, HIPAA or other regulated customers.

0 — Nothing on availability, security or how the service is operated.

3 — A claim of high availability or "enterprise security"; the SLA, status page, certifications and architecture are basic or not described.

5 — A public status page, a stated availability or SLA, hosting regions named, encryption in transit and at rest, ISO 27001 or SOC 2 stated, and data retention described.

8 — An SLA with credits published, the incident history public, multi-region failover or redundancy documented, redundant notification carriers named, certifications with their scope, a trust centre with reports on request, and a DORA or NIS2 addendum or mapping offered.

10 — Operation evidenced end to end: failover tested and published, independent audits (ISO 27001, SOC 2 Type II, BSI C5) with reports available, regulatory obligations for financial and critical-infrastructure customers explained in plain language, and the vendor's own post-incident reviews public.

Report an error

The SRE Lead

The pager's own operations are visible: a public status page with twenty-three components and history, an SLA that grants service credits, SOC 2 Type II, ISO 27001 and FedRAMP Low authorization, TLS 1.2+ in transit and AES 256+ at rest, customer-selectable regions, and an Assurance Portal for certifications and audit reports. We found no public information on multi-region failover being documented or tested, on the vendor's own post-incident reviews being public, or on anything offered for DORA or NIS2 customers. 9 10 12 16 25

Report an error

The IT Operations Manager

There is a public status page with per-service status and history, a standard SLA paying service credits, SOC 2 Type II and ISO 27001 statements, FedRAMP Low authorization, encryption at rest and in transit, region choice, and three named SMS and voice carriers on the subprocessor list — a hosted service independent of our own plant network. An assurance portal and on-request security practices support audits; we found no public information on multi-region failover, penetration tests or a DORA and NIS2 mapping, which is the part that would prove the pager survives its own outage. 9 10 12 14 15 16

Report an error

The MSP NOC Lead

A public status page with per-service history and subscriptions, an SLA with service credits, SOC 2 Type II requestable through an assurance portal, ISO 27001 and FedRAMP Low authorization, AES 256 at rest and TLS 1.2 in transit, and three named SMS and voice carriers (Twilio, MessageBird, Vonage) give me most of an audit file. We found no public information on multi-region failover testing, penetration test results, or a DORA or NIS2 addendum, and data center regions are offered as a customer choice rather than documented redundancy. 9 10 12 15 16 25

Report an error

The ICT Risk Officer

There is a public status page with per-service status and history, a standard SLA with service credits referenced in the terms, SOC 2 Type II examinations requestable, ISO 27001 stated, FedRAMP Low authorization, AES 256 at rest, TLS 1.2+ in transit, environment separation and an Assurance Portal for audit reports. Under the DPA, audit rights are limited to once annually, on-site, and the customer reimburses PagerDuty at then-current professional services rates — terms I would negotiate. We found no public information on multi-region failover, and no public DORA or NIS2 addendum or mapping, which is what I would need before signing a Frankfurt payments company. 9 10 12 14 16 25

Report an error

The Engineering Manager

A public status page with per-service status and history, service credits under a published SLA, SOC 2 Type II, ISO 27001 and FedRAMP Low authorization, AES 256 at rest and TLS 1.2+ in transit, customer choice of hosting region, an assurance portal with reports on request, and three named telecom carriers for SMS and voice give a strong compliance picture. We found no public information on multi-region failover, penetration tests, or support for DORA and NIS2 obligations. 9 10 12 15 16 25

Report an error

The Skeptic

A public status page with per-service status and history, an SLA whose stated remedy is service credits, AES-256 at rest and TLS 1.2 in transit, SOC 2 Type II and ISO 27001 stated, FedRAMP Low authorization, and an assurance portal with reports available on request are all published. We found no public information on multi-region failover or tested failover, penetration tests, or a DORA or NIS2 addendum, and the contractual audit right allows one on-site audit per year with the customer reimbursing PagerDuty at then-current professional services rates. 9 10 12 14 16 25 26

Report an error

European sovereignty panel opinion

Show reasoning
How this is scored

Who the contracting entity and the parent company are, where alerts, incident timelines, chat transcripts, contact data, phone numbers and account data are stored and processed, and who the subprocessors are (hosting, SMS and voice carriers, push services, email delivery, AI summary and transcription models, analytics, support and payment tools). Independently sourced by the sovereignty pipeline. Telephony and push providers needed to reach a responder in another country are part of what the product does and are not counted against it; where the data is stored and who processes it is. A self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.

3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.

5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (SMS and voice, AI, support, payment) run through non-EU providers without a stated safeguard.

8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every record on the customer's own servers.

10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor including the AI models and notification carriers, or a self-hosted edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.

Report an error

The SRE Lead

The contracting entity is PagerDuty, Inc. of San Francisco under California law, but the chain is unusually transparent for a US vendor: an EU Service Region customers can choose, a published data processing agreement incorporating the Standard Contractual Clauses with transfer impact assessments, a full subprocessor list with locations, and ISO 27001 and SOC 2 stated, with an EU representative named. The generative-AI chain (AWS, Google, Microsoft, OpenAI) and much of analytics and support run through US providers, which keeps this below the top of the range. 12 13 14 15 16

Report an error

The IT Operations Manager

The contracting entity is PagerDuty, Inc. of San Francisco with an EU representative appointed, customers may choose a service region, and the subprocessor list is published with locations including AWS in Germany and Ireland — but the AI chain runs through Amazon, Google, Microsoft and OpenAI in the United States, with Standard Contractual Clauses and transfer impact assessments as the stated safeguard. A published data processing addendum, Data Privacy Framework certification and ISO 27001 give the chain documentation, while the entity and ownership stay American. 12 13 14 15 16

Report an error

The MSP NOC Lead

The contracting entity is PagerDuty, Inc. of San Francisco under California law, but customers can choose an EU service region hosted on named AWS infrastructure in Germany and Ireland, the subprocessor list is published with locations and an RSS feed, and a data processing addendum incorporating the EU Standard Contractual Clauses with transfer impact assessments is public. The chain still runs through United States providers for the generative AI models (AWS, Google, Microsoft, OpenAI) and much of the telephony, with SCCs as the stated safeguard rather than a European entity, which for my German customer base is why I sit in the middle band. 12 13 14 15 16

Report an error

The ICT Risk Officer

The contracting party is PagerDuty, Inc. of San Francisco under California law, but customers can choose an EU service region, the subprocessor list is published with each provider's countries (hosting on AWS including Germany and Ireland, several SMS and voice carriers including European locations), and a DPA incorporating SCCs modules 2 and 3 with transfer impact assessments is part of the terms, with an EU representative named. Where I look hardest — the AI summaries of incident channels — the generative AI subprocessors are AWS, Google, Microsoft and OpenAI in the United States, with transcription through Hyperdoc in the US and Canada, and much of the analytics and support chain likewise US-based. The chain is transparent and safeguarded contractually, but the entity is American and the AI processing of incident content is documented as outside the EU. 12 13 14 15 16

Report an error

The Engineering Manager

The contracting entity is PagerDuty, Inc. of San Francisco under California law, but an EU service region is offered, the subprocessor list is published with locations — including AWS in Germany and Ireland and three SMS and voice carriers — and a data processing agreement incorporating the Standard Contractual Clauses with transfer impact assessments is public, alongside a named EU representative. The published list shows the generative AI services run through United States providers (AWS, Google, Microsoft and OpenAI), which my works council will want to weigh before approving AI features. 12 13 14 15 16

Report an error

The Skeptic

The contracting party is PagerDuty, Inc. of San Francisco under California law, an EU representative is named, a published data processing addendum incorporates the EU Standard Contractual Clauses with transfer impact assessments, customers choose a US or EU service region, and the sub-processor list gives locations including AWS in Germany and Ireland. The generative AI features run on OpenAI, Google, Microsoft and AWS in the United States and SMS and voice on Twilio and Vonage, so the chain outside hosting runs through US providers under contractual safeguards rather than a European entity or European infrastructure end to end. 12 13 14 15 16

Report an error

Pricing transparency

Show reasoning
How this is scored

Whether a buyer can compute the real annual cost from public pages alone: price per user or responder and per plan, whether stakeholders and viewers are free, how many SMS and voice notifications are included and what the rest cost per country, which features (incident response, status pages, AI, live call routing, SSO, audit logs) are add-ons or in higher plans, platform fees, minimum seats, annual versus monthly billing, and the currency and VAT treatment.

0 — No public prices at all; every customer is a sales call.

3 — A starting price per user exists, but notification limits, add-ons and the enterprise tier are unclear.

5 — Plans are public with their price per user and main inclusions, but at least one commonly needed piece (SMS and voice volume, status pages, AI, SSO or the top tier) is unpriced or "contact sales".

8 — Every plan priced publicly with its scaling rule, notification limits and overage prices stated, add-ons priced, stakeholder seats explained, minimum term and billing options and VAT treatment stated.

10 — Complete price computability: annual cost derivable for a given number of responders, stakeholders, notifications and status pages, with every add-on, overage and support fee and the cancellation and data-export terms published.

Report an error

The SRE Lead

Plans are public down to the numbers: a free tier, Professional at $25 per user per month and $21 billed annually, and platform tiers from a $2,800 to a $48,000 annual platform fee with quantified seats, AI Actions, Signal Intelligence Events and Live Call Routing lines, credit packs for scaling, and billing, minimum-commitment and VAT treatment in the terms. We found no public information on SMS and voice volumes or per-country prices, on prices for the separately purchased add-ons like AIOps, Status Pages and Runbook Automation, or on anything but "Custom Pricing" for the Ultimate tier. 4 6 8 12

Report an error

The IT Operations Manager

The pricing page publishes a free tier, per-user Professional pricing and platform fees for the reliability tiers with included seats, AI Actions, Signal Intelligence events and Live Call Routing lines, credit packs and a usage report, and the terms state annual invoicing in advance with the customer bearing taxes. The top tier is custom-priced, and we found no public information on SMS and voice volumes per country, add-on prices or overage unit prices. 8 12

Report an error

The MSP NOC Lead

Published prices are unusually concrete in places — a free plan at $0, Professional at $25 per user per month or $21 billed annually, and platform fees of $2,800, $12,000 and $48,000 per year with stated seats, Signal Intelligence events and AI Actions included — plus annual-in-advance billing, net 30 terms and taxes as the customer's responsibility. But the top tier is custom pricing, add-ons such as status pages, AIOps and Advance are named without prices, stakeholder seats and SMS or voice volumes are not explained, so I cannot compute the real annual cost for my sixty customers from the public pages alone. 8 12

Report an error

The ICT Risk Officer

Prices are public and unusually granular: Free at $0, Professional at $25 per user per month or $21 annually with the 16% discount stated, and platform tiers of $2,800, $12,000 and $48,000 per year, each with stated seats, Signal Intelligence Events, AI Actions and Live Call Routing lines, plus credit packs, annual invoicing in advance at net 30, a 1% monthly late charge, 60-day price-increase notice and customer responsibility for VAT. The top tier is custom pricing, and we found no public information on prices for the named add-ons (AIOps, Advance, Runbook Automation, Status Pages, Live Call Routing). We found no public information on included SMS or voice volumes or per-country overage prices. 8 12

Report an error

The Engineering Manager

The Free plan, Professional at "$25" per user per month monthly and "$21" annually, and platform tiers of "$2,800", "$12,000" and "$48,000" per year with "Custom Pricing" for Ultimate are public, including seat counts, included Signal Intelligence Events, AI Actions and live call routing lines, billing annually in advance, and taxes on the customer. The top tier is custom-priced, the separately purchased add-ons such as status pages, AI and live call routing carry no public prices, and we found no public information on SMS and voice volumes, overage rates per country, or what a seat for a manager who only reads along costs. 8 12 6

Report an error

The Skeptic

Plans are public: Free at "$0 per year", Professional at "$25" per user per month or "$21" annually, and PD Reliability Platform tiers at a "$2,800 platform fee per year" for Starter, "$12,000" for Essential and "$48,000 / year" for Plus, each with stated seat, Signal Intelligence Event, AI Action and Live Call Routing line allowances, credit packs, upfront annual invoicing at net 30, a 1% per month late charge and customer-paid taxes including value-added tax. Ultimate is "Custom Pricing", the separately purchased add-ons (AIOps, PagerDuty Advance, Runbook Automation, Status Pages, Live Call Routing) carry no public prices, and we found no per-country SMS or voice notification prices or any explanation of what stakeholder seats cost. 4 8 12

Report an error

European sovereignty — proven facts

3 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Not determined unverified
Why unverified?

Not confirmed on the vendor’s own pages as captured.

— uncited Report an error
Hosting options Self-hostable unverified
Why unverified?

The on-premises option covers only certain products (e.g. Runbook Automation/Rundeck) while the core platform is delivered as Hosted Services, and SaaS customers can additionally choose an EU Service Region.

1/1 pts 12 Report an error
Open source Not determined — uncited Report an error
Data processing agreement Published, self-serve unverified
Why unverified?

The DPA is published on the website and self-incorporates, but it only binds customers whose agreement expressly incorporates it.

1/1 pts 14 Report an error
Transfer impact assessment Not determined unverified
Why unverified?

Not confirmed on the vendor’s own pages as captured.

— uncited Report an error

Questions about PagerDuty

Is PagerDuty European?

No. whats-best.ai classifies PagerDuty as Rest of world. Its vendor, PagerDuty, Inc., is incorporated in the United States, per the vendor’s page captured 6 Nov 2026.

Where does PagerDuty store data?

Not stated on the vendor’s pages as of 6 Nov 2026.

Does PagerDuty have a free plan?

Yes. PagerDuty has a free plan, per the vendor’s page captured 6 Nov 2026.

What are the best alternatives to PagerDuty?

As of 18 Nov 2026, the panel rates ilert (4/5), All Quiet (3.5/5) and OneUptime (3.5/5) highest among the other 16 On-Call & Incident Management products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is ilert (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: PagerDuty alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (26)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage www.pagerduty.com Checked 6 Nov 2026 Details →
  2. 2 Features page (on-call management) www.pagerduty.com Checked 6 Nov 2026 Details →
  3. 3 Features page (incident management) www.pagerduty.com Checked 6 Nov 2026 Details →
  4. 4 Features page (alert noise reduction) www.pagerduty.com Checked 6 Nov 2026 Details →
  5. 5 Integrations page www.pagerduty.com Checked 6 Nov 2026 Details →
  6. 6 Documentation (escalation policies) docs.pagerduty.com Checked 6 Nov 2026 Details →
  7. 7 API documentation docs.pagerduty.com Checked 6 Nov 2026 Details →
  8. 8 Pricing page www.pagerduty.com Checked 6 Nov 2026 Details →
  9. 9 Security / trust page www.pagerduty.com Checked 6 Nov 2026 Details →
  10. 10 Public status page status.pagerduty.com Checked 6 Nov 2026 Details →
  11. 11 About page www.pagerduty.com Checked 6 Nov 2026 Details →
  12. 12 Terms of service (names the operating company) www.pagerduty.com Checked 6 Nov 2026 Details →
  13. 13 Privacy policy www.pagerduty.com Checked 6 Nov 2026 Details →
  14. 14 Data processing agreement (dpa) www.pagerduty.com Checked 6 Nov 2026 Details →
  15. 15 Subprocessor list www.pagerduty.com Checked 6 Nov 2026 Details →
  16. 16 GDPR page www.pagerduty.com Checked 6 Nov 2026 Details →
  17. 17 On-call schedules, rotations & escalation — found from sitemap www.pagerduty.com Checked 6 Nov 2026 Details →
  18. 18 On-call schedules, rotations & escalation — found from sitemap docs.pagerduty.com Checked 6 Nov 2026 Details →
  19. 19 Alert delivery, routing & noise reduction — found from sitemap docs.pagerduty.com Checked 6 Nov 2026 Details →
  20. 20 Alert delivery, routing & noise reduction — found from sitemap docs.pagerduty.com Checked 6 Nov 2026 Details →
  21. 21 Incident response, status pages & post-incident review — found from sitemap docs.pagerduty.com Checked 6 Nov 2026 Details →
  22. 22 Incident response, status pages & post-incident review — found from sitemap docs.pagerduty.com Checked 6 Nov 2026 Details →
  23. 23 Integrations, API & administration — found from sitemap docs.pagerduty.com Checked 6 Nov 2026 Details →
  24. 24 Integrations, API & administration — found from sitemap docs.pagerduty.com Checked 6 Nov 2026 Details →
  25. 25 Platform reliability, security & compliance — found from sitemap docs.pagerduty.com Checked 6 Nov 2026 Details →
  26. 26 Platform reliability, security & compliance — found from sitemap www.pagerduty.com Checked 6 Nov 2026 Details →