As of 6 Nov 2026, the panel rates ilert 4/5 and PagerDuty 3/5 in On-Call & Incident Management. Weighted by what each judge cares about, 6 of the 6 judges pick ilert and 0 pick PagerDuty. ilert scores higher on 7 of 7 criteria (European sovereignty, Alert delivery, routing & noise reduction, Integrations, API & administration, plus 4 more). Provenance — ilert: EU-Made, Germany; PagerDuty: Rest of world, United States. Ratings are the AI panel’s opinion, formed from public evidence: how scores are made.
The short answer
Both benches scored the same seven criteria, and the leans differ by criterion. ilert's widest margins are alerting and routing (8.7 vs 6.8), integration and administration (7.5 vs 6.0), reliability and compliance (8.0 vs 6.8) and sovereignty (8.3 vs 6.0); on these four, 6 judges lean ilert and 0 lean PagerDuty. The splits are on-call scheduling (7.0 vs 6.5: 3 lean ilert, 3 tie) and incident response (7.5 vs 7.0: 2 lean ilert, 4 tie), where PagerDuty's verdict credits Slack-declared incidents, Incident Commander and Customer Liaison roles and status pages. Pricing transparency: ilert 6.8, PagerDuty 5.8, with 5 leans ilert and 1 tie; the lean count for PagerDuty is 0 on the seven criteria. Sovereignty attributes: ilert lists a German legal entity with EU-default data residency; PagerDuty a US legal entity and a self-hostable option; both list self-serve DPAs. Per-judge weighted totals run ilert 7.4–8.1 against PagerDuty 5.8–6.8.
Choose ilert if
You need critical alerts to reach on-call staff over push, SMS, voice, WhatsApp, Telegram and email with automatic carrier failover — 6 judges lean ilert on alerting and routing (8.7 vs 6.8).
Your organisation must contract with a German (DE) legal entity and keep data in the EU by default — ilert's sovereignty attributes, with 6 judges leaning ilert on sovereignty (8.3 vs 6.0).
You want published tier prices before talking to sales — ilert lists Pro at 19 € and Enterprise from 49 € per user per month, and 5 judges lean ilert on pricing transparency.
Your team relies on a wide integration catalogue with Terraform support — PagerDuty's verdict cites 150-plus integrations with Terraform, and integration and administration leans ilert 6 to 0 (7.5 vs 6.0).
You need ISO 27001:2022 with an active/active setup across AWS Frankfurt and Stockholm — reliability and compliance leans ilert 6 to 0 (8.0 vs 6.8).
Choose PagerDuty if
You must be able to host the platform on your own infrastructure — PagerDuty's attributes list a self-hostable option; we found no public information on ilert's hosting options.
You want a published free tier to start — PagerDuty lists Free at $0 per year, with Professional at $25 per user per month or $21 annually.
Your response workflow centres on declaring incidents from Slack, the web and mobile apps, email or the API, with an Incident Commander role and a filterable timeline — incident response is where PagerDuty's verdict scored strongest, and 4 of the judges tied it against ilert.
You need internal and external status pages plus a Customer Liaison role for customer communication during incidents — documented end to end in PagerDuty's verdict.
You need live call routing through the same schedules you use for on-call — documented in PagerDuty's verdict, and on-call scheduling is the closest split in the table (3 judges lean ilert, 3 tie).
Read this comparison as one judge. Each weighs the same scores by what they care about.
The IT Operations Manager
Runs IT operations for a packaging manufacturer with 900 staff and three plants running around the clock, with Checkmk and PRTG watching servers, networks and the production line. Five administrators share a weekly standby. Wants a Checkmk alert to become a phone call that the right person acknowledges by keypad, the deputy called after ten minutes, no pages during planned maintenance, and an alerting service that still works when the plant's own network is the thing that is down.
ilert
This judge's pick
PagerDuty
Criterion by criterion
On-call schedules, rotations & escalation
ilert
The weekly standby our five administrators share is described almost verbatim — recurring schedules with a week-per-member example, static drag-and-drop shifts, overrides and shift swaps handled from the mobile app, and an escalation timeout that turns my ten-minute deputy rule into automatic escalation to the next level, with no-coverage times escalating immediately. Follow-the-sun scheduling, iCal calendar export, shift reminders by SMS, email and push, on-call reports with time on-call and alerts during duty, and management of schedules and policies through Terraform and the REST API are all documented. We found no public information on round-robin escalation, advance warning of coverage gaps before they happen, or exporting on-call hours for pay and working-time rules.
PagerDuty
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.
Alert delivery, routing & noise reduction
ilert
This is the closest match to my exact requirement I have read: alerts go out by push, SMS, voice call, WhatsApp, Telegram and email, with acknowledgement by "pressing a number during a phone call" or SMS reply, critical alerts that bypass do-not-disturb on Android and iOS, maintenance windows to stop pages during planned work, and heartbeat monitoring for silent failures — and the delivery side names Twilio, Vonage and Bird as telecom providers with automatic failover between them plus a published target of 99.9% of first-responder alerts delivered within five minutes. Grouping exists as time-based and AI-semantic with its logic and tunable similarity setting stated, routing on payload fields and time conditions is documented through event flows, and an SMS alert source accepts events without an internet connection. We found no public information on measurable noise-reduction results or per-channel delivery statistics, and delivery receipts per notification are not separately documented.
PagerDuty
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.
Incident response, status pages & post-incident review
ilert
Declaring an incident from an alert pre-fills the title, summary, affected services and responders, SEV1 and SEV2 open a dedicated channel by default, an incident commander role exists, and postmortems are drafted by AI from the timeline, linked alerts, deployment events and chat transcripts into sections including root cause analysis and action items. Public, private and audience-specific status pages with email, SMS and webhook subscribers, plus MTTA and MTTR reports filterable by source and team, are documented. The documentation itself states up front that the postmortem publishing settings do not take effect yet, and we found no public information on runbooks, incident types with their own process, service dependencies, or follow-up actions tracked into Jira or Linear.
PagerDuty
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.
Integrations, API & administration
ilert
Both of my monitoring stacks — Checkmk and PRTG Network Monitor — are named among more than 150 inbound integrations, outbound actions open Jira issues, call webhooks or send email, and bi-directional sync with ServiceNow, Autotask, Zabbix and Auvik is documented at the Enterprise tier. A REST API with an OpenAPI specification, documented rate limits and coverage of schedules, escalation policies and incidents, a Terraform provider included even in the free tier, account-wide and team-level roles with SAML single sign-on, and migration paths from Atlassian Statuspage and Opsgenie are all public. We found no public information on SCIM provisioning, administrative audit logs, or multi-tenant set-ups for service providers.
PagerDuty
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.
Platform reliability, security & compliance
ilert
The pager keeps working when our own plant network is the thing that is down: active/active hosting on AWS in Frankfurt and Stockholm with Dublin for disaster recovery, failover tested quarterly under production-like conditions, RTO within 60 minutes and RPO within 15 minutes, and named telecom providers with automatic failover. A public status page with per-component uptime and incident history, a 99.9% monthly uptime and notification-delivery SLA extendable to 99.99% at Enterprise, ISO 27001:2022 with its scope stated, annual external penetration tests, customer audit rights and a DORA addendum with exit and step-in rights are all documented. We found no public information on SLA credits, SOC 2 beyond a 2026 roadmap entry, or the vendor's own published post-incident reviews.
PagerDuty
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.
European sovereignty
ilert
The contracting entity is ilert GmbH in Cologne with a German commercial register number, the platform runs active/active on AWS in Frankfurt and Stockholm, and a published sub-processor list names each provider with its role, location and transfer mechanism — including Vonage and Bird in the Netherlands for telephony, X.AI processing AI features in an EU region on an opt-in-only basis, and Twilio as an explicitly optional United States choice for EU customers. A public data processing agreement offering deletion or certified return at the controller's choice, thirty days' notice of sub-processor changes with a right to object, and ISO 27001 certification round out the chain. United States entities such as HubSpot, PostHog and Fly.io appear in the list with EU processing locations and standard contractual clauses, and we found no public information on the ownership behind the GmbH.
PagerDuty
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.
Pricing transparency
ilert
Four plans carry public per-user prices — free up to 5 users with 100 SMS / voice notifications, Pro at 19 € per user per month with min. 3 users including unlimited SMS and voice and single sign-on, Scale at 39 € per user per month with min. 3 users, and Enterprise starting from 49 € per user per month — with priced add-ons such as inbound call routing at 10 € per user, per month and private status pages at 125 € per month, and support stated as included in all plans. What I still cannot compute is the true annual cost: we found no public information on annual versus monthly billing, VAT treatment, stakeholder seat pricing, or what happens past the 100 notifications on the free plan.
PagerDuty
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.
Sovereignty, side by side
Dimension
ilert
PagerDuty
Legal entity
Incorporated in DE
Incorporated in US
Hosting location
EU by default
Not determined
Hosting options
Not determined
Self-hostable
Open source
Not determined
Not determined
Data processing agreement
Published, self-serve
Published, self-serve
Transfer impact assessment
Not determined
Not determined
Facts, side by side
Only facts both products carry under the same definition — anything else would not be a fair row.
As of 6 Nov 2026, the panel rates ilert higher: 4/5 against 3/5. Weighted by what each judge cares about, 6 of the 6 judges pick ilert and 0 pick PagerDuty. Which one fits depends on the criteria that matter to you; the table on this page shows both side by side, and each judge’s reading has its own page. Both were scored by the same AI bench under the same rubric, from public evidence only, as the methodology describes.
Is ilert or PagerDuty European?
ilert is European (EU-Made, Germany). PagerDuty is not European by provenance (Rest of world, United States). Provenance is read from each company’s own legal pages: who builds it and who owns it.
Where do ilert and PagerDuty store customer data?
Per the vendors’ own pages as captured — ilert: In the EU by default. PagerDuty: its pages as captured do not say.
Do ilert and PagerDuty have a free plan?
As of 6 Nov 2026, both vendors’ own pages state a free plan. Each product page links the pricing page it was read from.