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 Skeptic
Has seen "never miss an alert" from a pager that was down in the same cloud region as the outage it should have reported, "unlimited notifications" that meant twenty SMS a month outside the US, and an "AI incident assistant" that sent the whole response channel to a model nobody named. Asks which carriers deliver the calls, what the SLA pays, whether schedules and history can be exported when leaving — and what the plan costs once the stakeholders need seats.
ilert
This judge's pick
PagerDuty
Criterion by criterion
On-call schedules, rotations & escalation
ilert
Recurring and static schedules with drag-and-drop shifts, follow-the-sun rotations, overrides with documented role rules and mobile shift take-over, escalation policies with timeouts, several targets per level and a documented no-coverage behaviour, all manageable by API and Terraform. On-call reports give time on call, alert count and time on alerts, but we found no public information on round-robin escalation, coverage gaps flagged before they happen, or on-call hours exported for pay and working-time rules.
PagerDuty
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.
Alert delivery, routing & noise reduction
ilert
Push, SMS, voice, WhatsApp, Telegram and email with critical alerts bypassing do-not-disturb on both platforms, acknowledgement by SMS reply or keypad, event flows that branch on payload fields (up to eight branches plus Else) with waits and transforms, and documented AI and time-based grouping. Three telecom carriers are named with automatic failover, and the status page publishes notification-delivery uptime and a time-to-first-notification metric; we found no public information on per-country delivery lists, delivery receipts, or measured noise-reduction results.
PagerDuty
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.
Incident response, status pages & post-incident review
ilert
Incidents are declared from scratch or an alert with severities, an incident commander, a timeline and channels auto-created for the top severities; status pages come in public, private and audience-specific forms with subscribers, and postmortems are drafted by AI from chat channels, alerts and deployment events with review statuses and publishing to status pages, plus MTTA/MTTR reports. The AI processor is named as opt-in with its processing region stated. We found no public information on runbooks beyond templates and actions, or on follow-up action items being tracked into ticketing tools.
PagerDuty
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.
Integrations, API & administration
ilert
More than 150 inbound integrations, bidirectional sync with ServiceNow, Autotask, Zabbix and Auvik on the top plan, a Terraform provider with export and state import, and a documented REST API with rate limits, an OpenAPI specification and resources covering schedules, escalation policies, incidents and postmortems, alongside team-level roles, SAML single sign-on and migration paths from Atlassian Statuspage and Opsgenie. We found no public information naming SCIM provisioning or an account-level audit log with export.
PagerDuty
"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.
Platform reliability, security & compliance
ilert
Active/active AWS Frankfurt and Stockholm with Dublin as disaster recovery, RTO at most 60 minutes and RPO 15 minutes with quarterly failover tests under production-like conditions, three named telecom carriers with automatic failover, a 99.9 percent uptime SLA and a notification-delivery SLA, ISO 27001:2022 with its scope stated, penetration tests and the certificate on request, a public status page with per-component uptime and history, and a DORA addendum. We found no public information on what the SLA pays in credits, and SOC 2 Type II is on a 2026 roadmap rather than held.
PagerDuty
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.
European sovereignty
ilert
A German GmbH with Cologne registry details contracts directly, hosting runs active/active in Frankfurt and Stockholm with Dublin for recovery, a public Article 28 data processing agreement provides deletion or certified return on exit, and a subprocessor list names every provider with location and transfer mechanism, including the AI provider as opt-in-only processing in an EU region and EU telecom alternatives to a US carrier. The ISO certificate itself is on request rather than published, and the AI, sandbox and analytics steps run through US-incorporated entities with stated safeguards, which falls short of end-to-end European processing.
PagerDuty
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.
Pricing transparency
ilert
Four tiers are priced per user with minimums (Free up to 5 users with one status page and 100 SMS/voice notifications, Pro at 19 € per user per month with a minimum of 3 users, Scale at 39 €, Enterprise starting from 49 € per user per month), unlimited SMS and voice and unlimited viewers from Pro, priced add-ons for inbound call routing and private or audience-specific status pages, and per-feature plan gating published on the features page. VAT treatment, annual versus monthly billing, AI-credit overage and the cost of SMS beyond the free plan's hundred are not stated, and the Enterprise tier is a starting price.
PagerDuty
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.
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.