PagerTree
Rest of world Report an errorPanel 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 PagerTree LLC · pagertree.com
Report an error on this page Is this your product? →
Link to this page
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.
PagerTree at a glance
- Vendor
- PagerTree LLC
- Headquarters
- Not stated on the vendor’s pages as of 6 Nov 2026
- Data hosting
- Outside the EU by default source, captured 6 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 6 Nov 2026
- Panel verdict
- The AI panel rates PagerTree 2.5/5, the mean of 6 judges. PagerTree is an on-call scheduling and alerting service whose strength is paging: alerting and routing and reliability and compliance score 6 to 7, covering push, email, SMS, voice, WhatsApp and Slack delivery, routing on custom match conditions, Twilio and Plivo named as carriers, a 99.9% monthly uptime commitment with service credits and a public status page. how scores are made
- As of
- Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
PagerTree is an on-call scheduling and alerting service whose strength is paging: alerting and routing and reliability and compliance score 6 to 7, covering push, email, SMS, voice, WhatsApp and Slack delivery, routing on custom match conditions, Twilio and Plivo named as carriers, a 99.9% monthly uptime commitment with service credits and a public status page. On-call scheduling scores 5 to 6 on escalation documentation — per-layer timeouts, up to three repeats, a reassign destination. Incident response is weakest at 3 to 4: severity levels, stakeholders and per-user MTTA/MTTR reports are documented, with no public information on incident channels, roles, timelines or postmortem templates. Sovereignty is a flat 4: Fly.io hosting in multiple USA regions, every listed sub-processor in the USA, Arizona law, and the vendor stating it has no plans for EU servers, though a DPA with Standard Contractual Clauses is offered to EU customers. Pricing transparency scores 5 to 6: Basic at $0/user/mo, Pro at $15/user/mo and Elite at $19/user/mo are public, and no SMS or voice volumes. No criterion spans more than a point; no meaningful disagreements emerged.
Speaks for it
- Escalation policies documented in depth, with per-layer timeouts, up to three repeats and a reassign destination
- Push, email, SMS, voice, WhatsApp and Slack delivery, with Twilio and Plivo named as notification providers
- 99.9% monthly uptime commitment with 5%, 10% and 20% service credits and a public status page with incident history
- Basic at $0/user/mo for up to 5 users, Pro at $15/user/mo for up to 25 and Elite at $19/user/mo for unlimited users, with a 14-day free trial requiring no credit card
- SAML 2.0 single sign-on documented in detail, including enforcement and single logout
Held against it
- Incident tooling is documented only as severity levels, stakeholders and broadcasts, with no public information on incident channels, roles, timelines, customer status pages or postmortem templates
- Every listed sub-processor is located in the USA, and the vendor states it has no plans for EU servers and no nominated EU representative under Article 27
- The SOC 2 Type 1 named belongs to the data centers used, with the vendor's own policies described only as aligned with SOC 2 and ISO 27001
- Public pricing names channels per plan but no SMS or voice volumes or overage prices, so annual notification cost is not computable from public pages
- We found no public information on audit logs, SCIM provisioning, two-factor authentication or granular team roles
Best for
- You run a team of up to 25 users and need SMS, voice and WhatsApp paging with detailed escalation controls
- You want a paging vendor with a published uptime commitment, service credits and its own public status page
- Your monitoring stack sends alerts by email or webhook, or includes PRTG, SolarWinds, Zendesk or Honeybadger
- You are switching off OpsGenie and want migration help
Avoid if
- You need structured incident management — chat-declared incidents, a commander role, timelines, customer status pages and postmortem templates
- You require EU-resident hosting or a nominated EU representative — the vendor states it has no plans for EU servers and names no Article 27 representative
- Your audit requires certification held by the vendor itself rather than the data centers used
- You must budget SMS and voice costs before purchase — public pages name channels per plan but no included volumes or overage prices
The scores
| Criterion | Panel median |
|---|---|
| On-call schedules, rotations & escalation | 3 of 5 |
| Alert delivery, routing & noise reduction | 3 of 5 |
| Incident response, status pages & post-incident review | 2 of 5 |
| Integrations, API & administration | 2 of 5 |
| Platform reliability, security & compliance | 3 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 2.5 of 5 |
On-call schedules, rotations & escalation
Show reasoningHide 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.
The SRE Lead
The scheduling documentation is genuinely solid: regular, repeating and rotating events with hour-to-year frequencies, drag-and-drop edits, overrides, and escalation policies with one to many layers, configurable timeouts, up to three repeats and a reassign destination. Shift reminders, calendar sync to Google, Outlook and iCal, and per-user time-on-call metrics with CSV export are all documented. We found no public information on time-zone handling, coverage-gap warnings, or managing schedules as code, which is where my bar sits. 2 4 12 13 5
The IT Operations Manager
The scheduler covers what my five-admin standby rotation needs: drag-and-drop calendars with regular, repeating and rotating events, one-off overrides, and escalation policies with configurable timeouts per layer plus up to three repeats and a reassign destination. Going-on-call reminders, calendar sync to Google, Outlook and iCal, and time-on-call reporting with CSV export are all documented. I found no public information on time-zone or follow-the-sun handling, coverage-gap warnings, or on-call hours exported for pay and working-time rules. 2 5 12 13
The MSP NOC Lead
The drag-and-drop scheduler supports regular, repeating and rotating events with frequencies from hours to years, per-event overrides and going-on-call reminders, and escalation policies are documented in real depth — one-to-many layers, per-layer timeouts, up to three repeats, a reassignment destination and a dropped state — which covers a separate night rota per key account. Calendar sync to Google, Outlook and iCal plus per-user time-on-call reports handle hand-offs and the monthly on-call accounting. We found no public information on follow-the-sun coverage checks, round-robin or conditional escalation, or managing schedules and policies by API. 2 5 12 13
The ICT Risk Officer
The scheduler is documented in real depth: drag-and-drop calendars with regular, repeating and rotating events, per-event overrides, sync to Google, Outlook and iCal, going-on-call reminders and per-user time-on-call reporting, with escalation policies of any number of layers, configurable timeouts, up to three repeats and a reassign destination. We found no public information on follow-the-sun hand-offs, time-zone handling, coverage-gap warnings or on-call hours exported for pay and working-time rules. 2 5 12 13
The Engineering Manager
The scheduler documentation covers regular, repeating and rotating events with drag-and-drop editing and overrides, escalation policies with per-layer timeouts, up to three repeats and a reassign destination, calendar sync to Google, Outlook and iCal, going-oncall reminders, and per-user time-oncall reports exportable as CSV. For my follow-the-sun rota across three sites the captured pages give no information on time-zone handling, swaps from the phone, coverage-gap warnings, or on-call hours exported per person for payroll and rest-period rules. 2 5 12 13
The Skeptic
Escalation mechanics are documented in real depth — per-layer timeouts, zero to three repeat cycles, a reassign destination, a dropped end-state — alongside regular, repeating and rotating events, overrides, calendar sync to Google, Outlook and iCal, going-oncall reminders, and per-user time-oncall reports exportable as CSV. We found no public information on time-zone handling, coverage-gap warnings, schedules managed as code, or handing a shift over from the mobile app. 2 12 13
Alert delivery, routing & noise reduction
Show reasoningHide 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.
The SRE Lead
Push, email, SMS, voice and WhatsApp delivery with per-user notification rules, do-not-disturb bypass on both phone platforms, acknowledgement by SMS or app, routing rules on custom match conditions, deduplication with aggregation windows from fifteen minutes to thirty days, suppression and maintenance windows are all documented, plus live call routing that escalates missed calls through the same policy. Delivery and read receipts are documented for WhatsApp only, and we found no public information on heartbeat monitoring, a per-alert notification log, or the countries where SMS and voice are delivered. Two providers, Twilio and Plivo, are named for notification redundancy. 2 4 12 14 15
The IT Operations Manager
A monitoring alert can become a phone call: voice notifications, SMS acknowledgable by reply, do-not-disturb bypass on both phone platforms, routing rules on custom match conditions, deduplication, aggregation windows, suppression and maintenance windows that re-enable affected integrations automatically are all documented. Escalation timeouts are configurable per layer, so paging the deputy after ten minutes is a settings change, and notifications can go through Twilio or Plivo — the pager is a hosted service independent of our plant network. I found no public information on heartbeats for silent failures, delivery receipts beyond WhatsApp, or the countries where SMS and voice are delivered. 2 4 6 12 14 15
The MSP NOC Lead
Push, email, SMS, voice, WhatsApp and Slack delivery with per-user channel choices, do-not-disturb bypass on Android and Apple, deduplication windows from fifteen minutes to thirty days, suppression, and maintenance windows with automatic re-enable are all documented, and routing rules match on custom conditions — close to what I need for routing by customer and severity. Live call routing to personal phones that escalates missed calls through the same policy as alerts, plus named carriers Twilio and Plivo for redundancy, strengthen delivery. We found no public information on heartbeat monitoring, a per-alert notification log, or the countries where SMS and voice are delivered. 2 4 6 14 15
The ICT Risk Officer
Push, email, SMS, voice, WhatsApp and Slack delivery with do-not-disturb bypass on Android and Apple, per-user channel choices, acknowledgement by SMS and one-click WhatsApp replies, routing rules on custom match conditions, deduplication with aggregation windows, suppression and maintenance windows, plus live call routing that escalates missed calls like alerts — and Twilio and Plivo are named as notification providers. We found no public information on heartbeat monitoring, delivery receipts for SMS and voice, a notification log per alert, or the countries in which SMS and voice are delivered. 2 3 6 14 15
The Engineering Manager
Push, email, SMS, voice, WhatsApp and Slack are documented, with do-not-disturb bypass on iOS and Android, acknowledgement by app and SMS, routing rules on custom match conditions, deduplication, suppression and maintenance windows with automatic re-enable. Live call routing feeds missed calls into the same escalation policy and both Twilio and Plivo are named as providers; delivery and read receipts are shown only for WhatsApp, and we found no public information on heartbeat monitoring or the countries where SMS and voice are delivered. 2 6 14 15
The Skeptic
The security page names multiple notification providers — Twilio and Plivo — which is more than most vendors publish, and do-not-disturb bypass, SMS acknowledgement, deduplication with aggregation windows of fifteen minutes to thirty days, suppression, maintenance windows, routing on custom match conditions and live call routing to personal phones with missed-call escalation are all documented. Delivery and read receipts are documented for WhatsApp only; we found no public information on heartbeat monitoring, a per-alert notification log, or the countries where SMS and voice are delivered. 2 12 14 15 6
Incident response, status pages & post-incident review
Show reasoningHide 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.
The SRE Lead
This is the thin part for how I run incidents: the product documents marking alerts as incidents with severity levels and attached stakeholders, broadcasts to the team, and per-user MTTA and time-on-call reporting, but we found no public information on declaring an incident from Slack or Teams, a dedicated channel and commander role, a timeline, a customer-facing status page, or postmortem templates with tracked follow-ups. The status page and post-incident review described on the vendor's pages are about PagerTree's own service rather than product features. 2 5 17
The IT Operations Manager
The product side shows alerts automatically marked as incidents with severity levels and attached stakeholders, plus per-user MTTR and time-on-call reporting. The incident response policy and post-incident review process describe how the vendor handles its own outages, not a process my team runs in the product. I found no public information on declaring incidents from chat, dedicated channels and roles, runbooks, customer-facing status pages or postmortem templates. 1 2 16 17
The MSP NOC Lead
Alerts can be automatically marked as incidents with severity levels and attached stakeholders, and MTTA and MTTR are documented down to their formulas with per-user reports exportable as CSV — that gives me the monthly response-time report per customer I owe my accounts. We found no public information on declaring incidents from chat, dedicated incident channels, incident roles, runbooks, a customer-facing status page product or postmortem templates; the post-incident review described is the vendor's own internal security process rather than a feature I could run for customers. 2 16 17
The ICT Risk Officer
The incident record goes only a step beyond the alert: alerts can be automatically marked as incidents with severity levels and stakeholders attached, broadcasts with files and custom response options reach the wider team, and reporting covers alert volume, trending issues and per-user mean time to respond. We found no public information on declaring from Slack or Teams, incident channels, roles or a commander, runbooks or automated workflows, customer status pages with subscribers, an incident timeline, post-incident review templates or AI summaries — which is where my DORA evidence needs would bite. 2 5 17
The Engineering Manager
Alerts can be marked as incidents with severity levels and attached stakeholders, broadcasts reach the whole team, and per-user MTTA and MTTR reporting exists. The detailed post-incident review process in the captured security policy describes the vendor's own operations rather than a product capability, and we found no public information on incident channels, roles, timelines, customer status pages, postmortem templates or AI summaries. 2 16 17
The Skeptic
Severity levels, stakeholders attached to incidents, per-user MTTR reports and broadcasts with custom response options are documented. We found no public information on declaring incidents from chat, incident channels, roles, timelines, customer-facing status pages, postmortem templates or tracked follow-ups — the detailed incident-response and post-incident-review documents describe the vendor's own internal security process, and the MTTA and MTTR formulas sit in an educational article rather than product analytics. 1 2 16 17
Integrations, API & administration
Show reasoningHide 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.
The SRE Lead
Slack, Microsoft Teams, Zendesk, Twilio, SolarWinds, Honeybadger and PRTG are named, with email and webhook intake as fallbacks, a documented Open API, outgoing webhooks, teams, and unusually deep SAML single sign-on documentation including enforcement and single logout. Open-source integrations with vendor-built additions in one to two business days and help for teams switching from OpsGenie are described. We found no public information on Jira, a Terraform provider, SCIM provisioning, audit logs, or roles within teams, so there is no schedules-in-Terraform story for me. 2 3 18 19
The IT Operations Manager
PRTG is a named integration, which matters to me directly, and the email, webhook and custom webhook fallbacks give my Checkmk stack a way in; the Open API, outgoing webhooks and an open-source integration model where the vendor builds new connectors in one to two business days are documented. SAML 2.0 single sign-on with enforced login and single logout, teams grouping users, schedules and escalation policies, and migration help for OpsGenie customers are all there. I found no public information on roles and permissions, two-factor authentication, SCIM provisioning, audit logs or a Terraform provider. 1 2 3 5 18 19
The MSP NOC Lead
Named integrations include Slack, Microsoft Teams, Zendesk, PRTG, SolarWinds and Honeybadger, with email, webhook and custom-webhook intake, an Open API, outgoing webhooks and a documented OpsGenie migration path — PRTG fits my monitoring estate, but we found no public information on Zabbix, Autotask or bidirectional PSA ticket sync, which is exactly what would open and close tickets without anyone copying text. SAML 2.0 single sign-on is documented in detail for Azure, Okta and Google, including enforcement and single logout. We found no public information on roles and permissions, two-factor authentication, SCIM provisioning, audit logs, or multi-tenant separation for service providers. 2 3 5 18 19
The ICT Risk Officer
There is a documented Open API, outgoing webhooks, email and custom-webhook intake for anything unlisted, named integrations including Slack, Microsoft Teams, Zendesk, Twilio, PRTG, SolarWinds and Honeybadger, an OpsGenie migration offer, and SAML 2.0 single sign-on documented down to enforcement, single logout and IdP troubleshooting. We found no public information on two-factor authentication, granular team roles, SCIM provisioning, audit logs, a Terraform provider or bidirectional ticketing sync — the audit log gap alone would concern me in a regulated environment. 2 3 18 19
The Engineering Manager
A documented Open API, outgoing webhooks, a full SAML 2.0 single sign-on guide with enforcement and single logout, and OpsGenie migration help are documented, with named integrations for Slack, Teams, Zendesk, Twilio, PRTG, SolarWinds and Honeybadger plus open-source integrations the vendor will build in one to two business days. The captured pages name a handful of tools rather than a broad catalogue, and we found no public information on SCIM, Terraform, bidirectional ticketing sync, audit logs or per-team roles. 2 3 5 18 19
The Skeptic
SAML 2.0 single sign-on is documented down to Azure and KeyCloak troubleshooting and can be enforced for members, an Open API and outgoing webhooks exist, email and webhook intake catch unlisted tools, and OpsGenie switchers are offered migration help. The integrations actually named on the captured pages are single digits, and we found no public information on SCIM, audit logs, a Terraform provider, bidirectional ticketing sync or role-based permissions. 18 2 3 19
Platform reliability, security & compliance
Show reasoningHide 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.
The SRE Lead
The terms commit to a 99.9 percent monthly uptime with tiered service credits of five, ten and twenty percent and a concrete unavailability definition, and the security page documents high availability across multiple availability zones, hourly encrypted backups at multiple data centers, and redundant notification through Twilio and Plivo. The vendor's own public status page shows a three-month incident history with resolution times, which I respect. What holds it back for an audit is that the only certification stated is SOC 2 Type 1 for the data centers with PagerTree's own policies said to align with SOC 2 and ISO 27001; we found no public information on a vendor-held certification, a trust centre, or DORA and NIS2 support. 6 7 9 21
The IT Operations Manager
The resilience story is documented, not just promised: a 99.9% monthly uptime commitment with published service credits and a concrete definition of unavailability, a public status page with recent incident history, high availability across multiple availability zones, and two named notification providers in Twilio and Plivo. Encryption in transit and at rest, hourly encrypted backups, vulnerability remediation timelines and a detailed data retention policy complete the picture. The certifications named belong to the datacenters (SOC2 Type 1) and to Stripe for payments; I found no public information on PagerTree's own certification scope or on DORA and NIS2 documentation. 6 7 9 11 21
The MSP NOC Lead
A published SLA commits to 99.9% monthly uptime with tiered service credits of 5, 10 and 20 percent and a five-minute unavailability definition, the public status page shows three months of incident history, and the platform runs in a high-availability configuration across multiple availability zones in several USA regions with redundant notification providers Twilio and Plivo named. Security documentation covers AES-256 at rest, SSL with HSTS, hourly encrypted backups, vulnerability remediation timelines and a detailed retention policy from three-day operational logs to one-year alert history. The SOC 2 statement covers only the data centres and policies are described as aligned with ISO 27001 rather than certified, and we found no public information on DORA or NIS2 mappings. 6 7 9 11 21
The ICT Risk Officer
A 99.9% monthly uptime commitment with tiered service credits and a precise unavailability definition sits alongside a public status page with months of incident history, high-availability deployment across multiple availability zones, hourly encrypted backups, Twilio and Plivo named as carriers, published security policies, vulnerability remediation timelines and a detailed data-retention schedule. For my DORA register the gaps matter: we found no public information on the vendor's own ISO 27001 or SOC 2 certification with its scope, a DORA or NIS2 addendum or mapping, or tested failover — the SOC 2 Type 1 reference covers the data centres used, and the vendor's policies are described only as aligned with SOC 2 and ISO 27001. 6 7 9 16 21
The Engineering Manager
A 99.9% monthly uptime commitment with 5/10/20% service credits and a defined unavailability window is published, a public status page shows recent incidents with resolution times, the service runs in a high-availability configuration across multiple availability zones with Twilio and Plivo named for notification delivery, and a retention policy details alert, backup, log and support-data lifetimes. The stated SOC 2 Type 1 belongs to the data centers rather than PagerTree itself, and we found no public information on the vendor's own certification scope, penetration-test reports or a DORA or NIS2 mapping. 6 7 9 21
The Skeptic
The SLA pays: 99.9% monthly uptime with 5%, 10% and 20% service credits, a five-minute unavailability definition, and a public status page whose history lists real incidents including SMS failures to T-Mobile customers resolved in 22 hours. Multiple availability zones across several USA regions, redundant notification providers named, encryption in transit and at rest, and concrete retention numbers are documented; we found no public information on the vendor's own ISO 27001 or SOC 2 certification — the pages speak of data centers showing SOC2 Type 1 and policies aligning with SOC 2 and ISO 27001 — on penetration-test reports, or on DORA and NIS2 guidance. 6 7 9 21
European sovereignty
panel opinion
Show reasoningHide 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.
The SRE Lead
For a Berlin buyer the chain is fully American: PagerTree LLC of Tempe, Arizona hosts its primary data at Fly.io across USA regions, states it has no plans to add servers in the EU, and lists every sub-processor — Cloudflare, AWS, Twilio, Plivo, Mailgun, Postmark, OneSignal, Slack — as located in the USA, with Arizona governing law and United States export controls. Credit where due: the sub-processor list with locations and purposes is published, a data processing addendum with Standard Contractual Clauses is offered for EU customers, data-subject requests are answered within fourteen days, and there is a right to object to new sub-processors. The vendor states it does not process enough data to warrant a nominated EU representative. 6 8 9 11
The IT Operations Manager
The chain is transparent but entirely American: primary hosting on Fly.io in multiple USA regions, all nine listed sub-processors located in the USA, an explicit statement that there are no plans to add EU servers, and no nominated EU representative. A data processing addendum with Standard Contractual Clauses is offered for EU customers, though the vendor states it cannot sign customers' own DPAs. For my plants that means every alert, phone number and timeline sits under US processing with the contractual clauses as the safeguard. 6 8 9 11
The MSP NOC Lead
PagerTree LLC of Tempe, Arizona hosts primary data at Fly.io in several USA regions and states it has no plans for EU servers, and every listed sub-processor — Cloudflare, AWS, Fly.io, Twilio, Plivo, Mailgun, Postmark, OneSignal and Slack — is located in the USA. Credit where due: a data processing addendum containing the Standard Contractual Clauses is offered to EU customers, sub-processors are listed with a right to object, and breach notification without delay is promised, though the vendor will not sign customer-supplied DPAs and has no nominated EU representative. For sixty German customers under my roof that is a USA-only chain end to end. 6 9 10 11
The ICT Risk Officer
The chain is transparent and entirely American: PagerTree LLC of Tempe, Arizona under Arizona law, hosting at Fly.io in multiple USA regions, and a published sub-processor list — Cloudflare, AWS, Fly.io, Twilio, Plivo, Mailgun, Postmark, OneSignal, Slack — all located in the USA, with phone numbers and SMS/voice content going to Twilio and Plivo and payments through Stripe. A data processing addendum with Standard Contractual Clauses is offered for EU customers with a right to object to new sub-processors, but the vendor states it has no plans for EU servers and states that it has no nominated EU representative under Article 27. 6 9 10 11
The Engineering Manager
The contracting entity is PagerTree LLC under Arizona law, data and servers sit with Fly.io across multiple USA regions, and every listed sub-processor — Cloudflare, AWS, Twilio, Plivo, Mailgun, Postmark, OneSignal, Slack — is in the USA, with the vendor stating it has no plans for EU servers. An EU-facing DPA with Standard Contractual Clauses, a sub-processor objection right and 14-day data-subject responses are documented, though the vendor names no EU representative and will not sign customer-supplied DPAs. 6 9 11
The Skeptic
The chain is fully traceable and entirely American: PagerTree LLC of Tempe, Arizona under Arizona law, hosting at Fly.io in several USA regions, and a published subprocessor list — Cloudflare, AWS, Twilio, Plivo, Mailgun, Postmark, OneSignal, Slack — every one located in the USA, with the EU page stating there are no plans for EU servers and no nominated EU representative. The DPA for EU customers carries Standard Contractual Clauses and new subprocessors can be objected to, though customers' own DPAs will not be signed; we found no public information on a self-hosted edition. 11 8 9 6
Pricing transparency
Show reasoningHide 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.
The SRE Lead
Per-user prices are public with the main inclusions per plan: Basic at $0/user/mo up to five users, Pro at $15/user/mo up to twenty-five users, Elite at $19/user/mo for unlimited users, Enterprise as 'Custom', plus team limits, unlimited integrations on all plans, credit-card or NET 30 invoicing, a yearly option advertised as 'Yearly Get 2 months free!', and terms stating fees exclude taxes. What I cannot compute from the public pages: included SMS and voice volumes and per-country overage costs, stakeholder or viewer seats, or any add-on pricing. Cancellation, auto-renewal and the thirty-day notice for non-monthly plans are documented. 1 5 9
The IT Operations Manager
Three plans are priced publicly — Basic $0/user/mo up to 5 users, Pro $15/user/mo up to 25 users, Elite $19/user/mo unlimited — with user and team limits, main inclusions, payment options, a yearly option giving two months free, and terms that state taxes are excluded and how cancellation and auto-renewal work. Enterprise is custom-priced, and I found no public information on included SMS and voice volumes or what additional notifications cost. I can price the first three tiers but cannot compute the full annual cost of a paging service at three plants. 1 2 5 9
The MSP NOC Lead
All three self-service plans are public — Basic at $0/user/mo for up to 5 users, Pro at $15/user/mo for up to 25, Elite at $19/user/mo with unlimited users — with per-plan team and user limits, support tiers, payment options, two months free on yearly billing, taxes excluded and clear cancellation and auto-renewal terms. Enterprise is quoted as Custom with NET 30 invoicing and PO support, and we found no public information on included SMS or voice volumes, overage prices per country, or whether stakeholder and viewer seats are free — so I cannot compute the real annual cost for my responder count from public pages alone. 1 5 9
The ICT Risk Officer
Four tiers are public — Basic at $0/user/mo for up to 5 users, Pro at $15/user/mo for up to 25, Elite at $19/user/mo with unlimited users, Enterprise listed as "Custom" — with user and team limits, notification channels per plan, yearly billing at two months free, card or NET 30 invoicing, and terms stating that fees exclude taxes, along with auto-renewal, notice periods and no downgrade refunds. We found no public information on included SMS and voice volumes or per-country overage prices, stakeholder seats, or add-on pricing, so the real annual cost for a team that depends on SMS is not computable from public pages alone. 2 5 9
The Engineering Manager
The three lower plans are priced publicly — Basic $0/user/mo up to 5 users, Pro $15/user/mo up to 25 users, Elite $19/user/mo unlimited users — with per-plan channels, team caps, payment options, a two-months-free yearly option and published cancellation and tax treatment. The Enterprise tier is custom-priced only, and we found no public information on included SMS or voice volumes and overage prices, free read-along seats for managers, or VAT treatment. 1 2 5 9
The Skeptic
Three tiers are priced publicly — "$0/user/mo" up to 5 users, "$15/user/mo" up to 25 users, "$19/user/mo" unlimited — with team limits, support tiers, payment options, "Yearly Get 2 months free!", a 14-day trial without a credit card, and terms covering auto-renewal, cancellation, no downgrade refunds and that fees exclude taxes. No buyer can compute notification cost: the pages say only which channels ship with which plan, with no SMS, voice or WhatsApp volumes or per-country overage prices, the Enterprise tier is "Custom" with no figure, and we found no public information on stakeholder or viewer seats. 5 2 9 1
European sovereignty — proven facts
3 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location |
Outside the EU
unverified
Why unverified?The word "primary" leaves the location of any secondary data undefined, though the sub-processor list places the server and database host (Fly.io) and every other sub-processor in the USA. |
0/4 pts | 11 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source |
Proprietary
unverified
Why unverified?The page never names a licence for the product; "proprietary" rests on this IP-ownership clause asserting exclusive proprietary rights rather than an explicit "closed source" statement. |
0/1 pts | 9 Report an error |
| Data processing agreement |
On request
unverified
Why unverified?No DPA text is shown in the excerpts — the GDPR section says "You can find it here", but the only stated way to receive and conclude one is an emailed request followed by electronic signature. |
0/1 pts | 11 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about PagerTree
Is PagerTree European?
No. whats-best.ai classifies PagerTree as Rest of world.
Where does PagerTree store data?
PagerTree stores customer data outside the EU by default, per the vendor’s page captured 6 Nov 2026.
Does PagerTree have a free plan?
Yes. PagerTree has a free plan, per the vendor’s page captured 6 Nov 2026.
What are the best alternatives to PagerTree?
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: PagerTree alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 6 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. No DPA text is shown in the excerpts — the GDPR section says "You can find it here", but the only stated way to receive and conclude one is an emailed request followed by electronic signature.
- Weak sourcing — Open source. The page never names a licence for the product; "proprietary" rests on this IP-ownership clause asserting exclusive proprietary rights rather than an explicit "closed source" statement.
- Weak sourcing — Hosting location. The word "primary" leaves the location of any secondary data undefined, though the sub-processor list places the server and database host (Fly.io) and every other sub-processor in the USA.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
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.
- 2 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 compliance fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (21)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage pagertree.com Checked 6 Nov 2026 Details →
- 2 Features page pagertree.com Checked 6 Nov 2026 Details →
- 3 Integrations page pagertree.com Checked 6 Nov 2026 Details →
- 4 Documentation pagertree.com Checked 6 Nov 2026 Details →
- 5 Pricing page pagertree.com Checked 6 Nov 2026 Details →
- 6 Security / trust page pagertree.com Checked 6 Nov 2026 Details →
- 7 Public status page status.pagertree.com Checked 6 Nov 2026 Details →
- 8 About page pagertree.com Checked 6 Nov 2026 Details →
- 9 Terms of service (names the operating company) pagertree.com Checked 6 Nov 2026 Details →
- 10 Privacy policy pagertree.com Checked 6 Nov 2026 Details →
- 11 EU privacy page pagertree.com Checked 6 Nov 2026 Details →
- 12 On-call schedules, rotations & escalation — found from sitemap pagertree.com Checked 6 Nov 2026 Details →
- 13 On-call schedules, rotations & escalation — found from sitemap pagertree.com Checked 6 Nov 2026 Details →
- 14 Alert delivery, routing & noise reduction — found from sitemap pagertree.com Checked 6 Nov 2026 Details →
- 15 Alert delivery, routing & noise reduction — found from sitemap pagertree.com Checked 6 Nov 2026 Details →
- 16 Incident response, status pages & post-incident review — found from sitemap pagertree.com Checked 6 Nov 2026 Details →
- 17 Incident response, status pages & post-incident review — found from sitemap pagertree.com Checked 6 Nov 2026 Details →
- 18 Integrations, API & administration — found from sitemap pagertree.com Checked 6 Nov 2026 Details →
- 19 Integrations, API & administration — found from sitemap pagertree.com Checked 6 Nov 2026 Details →
- 20 Platform reliability, security & compliance — found from sitemap pagertree.com Checked 6 Nov 2026 Details →
- 21 Platform reliability, security & compliance — found from sitemap pagertree.com Checked 6 Nov 2026 Details →