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 ICT Risk Officer
ICT risk officer at a Frankfurt payments company supervised by BaFin, where DORA requires major ICT incidents to be classified and reported within hours. The incident tool is itself an ICT third-party service in the register. Reads the subprocessor list, asks where incident timelines and the AI summaries of the response channel are processed, wants an SLA, audit logs and a DORA addendum in the contract, and needs the timeline to hold up as evidence for the regulator.
ilert
This judge's pick
PagerDuty
Criterion by criterion
On-call schedules, rotations & escalation
ilert
Recurring and static rotations, follow-the-sun cover, overrides and shift swaps handled from the mobile app, and escalation policies with timeouts, several levels, delayed escalation and user, team or schedule targets are documented in real depth, and schedules and escalation policies are also reachable through the API and the Terraform provider. On-call reports give time on call, alert count and time on alerts, but we found no public information on exporting on-call hours per person for pay and working-time rules, on round-robin rotation, or on coverage gaps being flagged before they happen.
PagerDuty
Rotations, layer precedence, overrides, shift revert, reminders, handoff notices up to 48 hours ahead and calendar export to Outlook, Google Calendar and iCal are documented, alongside escalation policies with up to 20 rules, adjustable timeouts, up to nine repeats and round-robin assignment; the FAQ also covers multi-time-zone schedules, shift swaps, conflict detection and managing schedules through an API or infrastructure-as-code. We found no public information on on-call hours exported per person for pay and working-time rules, or on fairness and fatigue reporting, which a German works council would ask for.
Alert delivery, routing & noise reduction
ilert
Push, SMS, voice, WhatsApp, Telegram and email with acknowledgement by SMS reply or keypad, critical alerts that bypass do-not-disturb, time-window and AI semantic grouping with a configurable similarity setting, and event flows that branch on payload fields and time conditions are all documented. Redundant carriers are named — Twilio, Vonage and Bird — with automatic failover, and delivery is measured rather than merely promised, with a published target of 99.9% of first-responder alerts delivered within five minutes and a live time-to-first-notification figure on the status page. We found no public information on per-country SMS and voice delivery tables or on notification limits for every plan.
PagerDuty
Push, phone, SMS, email and WhatsApp delivery are documented channel by channel, with acknowledgement by app, by phone keypad (including bulk acknowledge and resolve) and by SMS reply, plus live call routing that sends inbound callers through the on-call schedules and turns voicemails into incidents. Alert grouping is documented in five techniques with its logic explained, auto-pause quiets transient alerts, and the incident timeline records every notification sent. We found no public information on delivery receipts, heartbeat monitoring, or the countries and channels where SMS and voice are delivered.
Incident response, status pages & post-incident review
ilert
Incidents are declared from the app or from an alert with pre-filled details, severities, an incident channel opening by default for the two highest, an incident commander, a timeline, and public, private and audience-specific status pages with email, SMS, webhook and RSS subscribers. AI drafts the summary, status updates and the postmortem with action items, and the subprocessor list names the AI provider, its EU processing region and its opt-in-only handling — exactly the disclosure I need before letting an AI model near an incident channel. We found no public information on runbooks or on major-incident and regulatory reporting templates, which a DORA-reportable operation would still have to build itself.
PagerDuty
Declaration from Slack, the web and mobile apps, API and email, a filterable timeline recording statuses, actions and every notification sent, incident roles from Incident Commander to custom roles across web, Slack, Teams and workflows, post-incident reviews, Jeli analysis, internal and external status pages, stakeholder communications and incident workflows are documented, with custom incident types and tasks on the upper tiers. The vendor commits to customer choice on generative AI and states no customer data is used for training, with a fuller AI disclosure available on request. We found no public information on follow-up actions tracked into Jira or Linear, or on major-incident and regulatory reporting templates.
Integrations, API & administration
ilert
More than 150 inbound integrations, bidirectional ServiceNow, Autotask, Zabbix and Auvik sync on the top plan, a documented REST API with an OpenAPI spec covering schedules, escalation policies and incidents, webhooks, a Terraform provider, SAML single sign-on and account-wide plus team-level roles cover most of what our stack and third-party register need. We found no public information on SCIM provisioning or an exportable administrator audit log, which I would require before signing.
PagerDuty
750+ native integrations are claimed with Slack and Microsoft Teams named, a REST API is documented with OAuth scopes, versioning and rate limits, ServiceNow CMDB enrichment endpoints exist, and bi-directional ServiceNow custom-field sync arrives on the top tier; teams, plan-based team fields and role administration are described. Single sign-on appears only as a line on the vendor's own status page, and we found no public information on audit logs, SCIM provisioning, a Terraform provider or documented migration from other tools. Before entering this tool in our ICT third-party register, the missing public information on audit logging is the part I would chase hardest.
Platform reliability, security & compliance
ilert
Active/active AWS Frankfurt and Stockholm with Dublin for disaster recovery, quarterly failover testing under production-like conditions, recovery within 60 minutes and a recovery point within 15, published service levels of 99.9% web uptime and 99.9% of first-responder alerts delivered within five minutes, ISO 27001:2022 with its scope, annual external penetration tests, and a DORA package with addendum, four-hour incident notice, TLPT cooperation and audit, exit and step-in rights — this is directly usable evidence for our BaFin reporting chain. We found no public information on service-level credits for missed targets, and SOC 2 is a 2026 roadmap item rather than a delivered certification.
PagerDuty
There is a public status page with per-service status and history, a standard SLA with service credits referenced in the terms, SOC 2 Type II examinations requestable, ISO 27001 stated, FedRAMP Low authorization, AES 256 at rest, TLS 1.2+ in transit, environment separation and an Assurance Portal for audit reports. Under the DPA, audit rights are limited to once annually, on-site, and the customer reimburses PagerDuty at then-current professional services rates — terms I would negotiate. We found no public information on multi-region failover, and no public DORA or NIS2 addendum or mapping, which is what I would need before signing a Frankfurt payments company.
European sovereignty
ilert
The contracting entity is a German GmbH in Cologne, hosting is active/active AWS in Frankfurt and Stockholm described as made and hosted in Germany, and a public subprocessor list names every processor with its role, location and transfer mechanism — including the AI providers, which process in an EU region and only for accounts with AI enabled, and the telecom carriers, with Twilio's US processing stated as optional for EU customers. A published Article 28 data processing agreement gives thirty days' notice of subprocessor changes with a right to object. We found no public information on the ownership structure beyond the German entity, and several processors are US companies that process in the EU under standard contractual clauses — sovereign in practice, but the chain is not European end to end.
PagerDuty
The contracting party is PagerDuty, Inc. of San Francisco under California law, but customers can choose an EU service region, the subprocessor list is published with each provider's countries (hosting on AWS including Germany and Ireland, several SMS and voice carriers including European locations), and a DPA incorporating SCCs modules 2 and 3 with transfer impact assessments is part of the terms, with an EU representative named. Where I look hardest — the AI summaries of incident channels — the generative AI subprocessors are AWS, Google, Microsoft and OpenAI in the United States, with transcription through Hyperdoc in the US and Canada, and much of the analytics and support chain likewise US-based. The chain is transparent and safeguarded contractually, but the entity is American and the AI processing of incident content is documented as outside the EU.
Pricing transparency
ilert
Plans are public with per-user prices and minimums where stated — Free up to five users with 100 SMS/voice notifications, Pro at 19 € per user per month and Scale at 39 € per user per month each with a minimum of three users, Enterprise starting from 49 € — plus priced add-ons such as inbound call routing at 10 € per user per month and a private status page at 125 € per month. We found no public information on annual versus monthly billing, VAT treatment, or overage prices for SMS, voice or AI credits, so the real annual cost is not derivable from public pages alone.
PagerDuty
Prices are public and unusually granular: Free at $0, Professional at $25 per user per month or $21 annually with the 16% discount stated, and platform tiers of $2,800, $12,000 and $48,000 per year, each with stated seats, Signal Intelligence Events, AI Actions and Live Call Routing lines, plus credit packs, annual invoicing in advance at net 30, a 1% monthly late charge, 60-day price-increase notice and customer responsibility for VAT. The top tier is custom pricing, and we found no public information on prices for the named add-ons (AIOps, Advance, Runbook Automation, Status Pages, Live Call Routing). We found no public information on included SMS or voice volumes or per-country overage prices.
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.