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 PagerTree LLC · pagertree.com

Report an error on this page Is this your product? →

Link to this page

PagerTree: AI-assisted analysis on whats-best.ai PagerTree: 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.

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

PagerTree alternatives, European ones first →

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

The SRE Lead

Weighted verdict

Leads site reliability at a Berlin SaaS company with sixty engineers in eight product teams, Prometheus and Grafana for metrics, Sentry for errors and everything discussed in Slack. Wants an incident declared with one command, a channel with roles and a timeline, the status page updated from the same place, alerts grouped so one database outage does not page five teams, schedules kept in Terraform, and a postmortem that writes its first draft.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The SRE Lead

Panel median The SRE Lead This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The SRE Lead
On-call schedules, rotations & escalation 3 of 5 3 of 5
Alert delivery, routing & noise reduction 3 of 5 3 of 5
Incident response, status pages & post-incident review 2 of 5 2 of 5
Integrations, API & administration 2 of 5 2.5 of 5
Platform reliability, security & compliance 3 of 5 3 of 5
European sovereignty 2 of 5 2 of 5
Pricing transparency 2.5 of 5 2.5 of 5

On-call schedules, rotations & escalation

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

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

Report an error

Alert delivery, routing & noise reduction

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, 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

Report an error

Incident response, status pages & post-incident review

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 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

Report an error

Integrations, API & administration

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

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

Report an error

Platform reliability, security & compliance

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 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

Report an error

European sovereignty

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

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

Report an error

Pricing transparency

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

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

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 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

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 (21)

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

  1. 1 Vendor homepage pagertree.com Checked 6 Nov 2026 Details →
  2. 2 Features page pagertree.com Checked 6 Nov 2026 Details →
  3. 3 Integrations page pagertree.com Checked 6 Nov 2026 Details →
  4. 4 Documentation pagertree.com Checked 6 Nov 2026 Details →
  5. 5 Pricing page pagertree.com Checked 6 Nov 2026 Details →
  6. 6 Security / trust page pagertree.com Checked 6 Nov 2026 Details →
  7. 7 Public status page status.pagertree.com Checked 6 Nov 2026 Details →
  8. 8 About page pagertree.com Checked 6 Nov 2026 Details →
  9. 9 Terms of service (names the operating company) pagertree.com Checked 6 Nov 2026 Details →
  10. 10 Privacy policy pagertree.com Checked 6 Nov 2026 Details →
  11. 11 EU privacy page pagertree.com Checked 6 Nov 2026 Details →
  12. 12 On-call schedules, rotations & escalation — found from sitemap pagertree.com Checked 6 Nov 2026 Details →
  13. 13 On-call schedules, rotations & escalation — found from sitemap pagertree.com Checked 6 Nov 2026 Details →
  14. 14 Alert delivery, routing & noise reduction — found from sitemap pagertree.com Checked 6 Nov 2026 Details →
  15. 15 Alert delivery, routing & noise reduction — found from sitemap pagertree.com Checked 6 Nov 2026 Details →
  16. 16 Incident response, status pages & post-incident review — found from sitemap pagertree.com Checked 6 Nov 2026 Details →
  17. 17 Incident response, status pages & post-incident review — found from sitemap pagertree.com Checked 6 Nov 2026 Details →
  18. 18 Integrations, API & administration — found from sitemap pagertree.com Checked 6 Nov 2026 Details →
  19. 19 Integrations, API & administration — found from sitemap pagertree.com Checked 6 Nov 2026 Details →
  20. 20 Platform reliability, security & compliance — found from sitemap pagertree.com Checked 6 Nov 2026 Details →
  21. 21 Platform reliability, security & compliance — found from sitemap pagertree.com Checked 6 Nov 2026 Details →