ilert vs PagerDuty

ilert

EU-Made

Sovereignty: 3 of 6 dimensions proven

Full evaluation →

PagerDuty

Rest of world

Sovereignty: 3 of 6 dimensions proven

Full evaluation →

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

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.

ilert

This judge's pick

PagerDuty

Criterion by criterion

On-call schedules, rotations & escalation

ilert

Follow-the-sun rotations, shift swaps and overrides managed from the mobile app, escalation policies with timeouts and user, team or schedule targets, shift reminders, calendar sync and on-call reports are all documented, and schedules run as code through the Terraform provider with schedule and escalation resources in the API. We found no public information on round-robin escalation, coverage gaps flagged before they happen, or per-person on-call hours exported for pay and working-time rules.

PagerDuty

Escalation mechanics are documented in real depth: layered schedules with precedence, round-robin assignment, easy shift overrides, handoff notices up to 48 hours before a shift, reminders, and calendar export to Outlook, Google Calendar and iCal, plus hard limits like twenty rules and nine repeats per policy with timeout minimums. We found no public information on exporting on-call hours per person for pay and working-time rules, on coverage gaps flagged before they happen, or on schedules managed as code beyond a listed FAQ question.

Alert delivery, routing & noise reduction

ilert

Push, SMS, voice, email, WhatsApp and Telegram with critical alerts overriding do-not-disturb on Android and iOS, acknowledgement by SMS reply or keypad, heartbeats, maintenance windows and delayed escalation are all documented, and noise reduction is real: AI semantic grouping with a tunable similarity setting and event filters, time-window grouping, and event flows that branch on payload fields and time conditions behind a per-alert audit-grade notification timeline. SMS and voice run over named redundant carriers — Twilio, Vonage, Bird — with automatic failover, and volumes are stated per plan (100 SMS and voice on free, unlimited from Pro). We found no public information on delivery receipts or measured noise-reduction results.

PagerDuty

Push, phone, SMS, email and WhatsApp all land, with acknowledge, resolve and escalate from the phone keypad or by SMS reply, bundling on every channel, live call routing into the same schedules, and alert grouping whose logic is documented across five named techniques plus auto-pause and suppression — the noise-reduction story is the strongest part. We found no public information on heartbeat monitoring, delivery receipts, or the countries and channels where SMS and voice are delivered.

Incident response, status pages & post-incident review

ilert

An incident is declared from an alert or from scratch with title, services and responders pre-filled, opens a dedicated channel by default at SEV1 and SEV2, carries a commander role, timeline and stakeholder updates, and publishes to public, private or audience-specific status pages from the same place; the AI drafts the postmortem from the incident channel and alert timeline into five sections with a draft-to-published workflow. The AI chain is disclosed — X.AI and Fly.io process only for accounts with AI enabled, in EU regions — which is exactly the data handling I want documented. We found no public information on runbooks or follow-up actions tracked into Jira or Linear.

PagerDuty

This is close to what I run on: declare an incident from Slack, the web app, mobile or the API; a filterable timeline per incident; roles like Incident Commander and Customer Liaison assignable to one accountable responder in Slack and Teams; public and private status pages from the Starter tier upward; post-incident reviews plus the Jeli analysis service; and GenAI features whose data handling is disclosed, with a stated choice and no customer data used for training. We found no public information on status-page subscribers, follow-up actions tracked into Jira or Linear, or a service catalogue with dependencies.

Integrations, API & administration

ilert

More than 150 inbound integrations including Prometheus, Checkmk, Datadog, Zabbix and PRTG, chat and ITSM outbound integrations, bi-directional sync with ServiceNow, Autotask, Zabbix and Auvik on Enterprise, a Terraform provider with export of UI resources, and a documented REST API with OpenAPI spec, rate limits and resources covering schedules, escalation policies, incidents and postmortems. There is an importer from Atlassian Statuspage and an Opsgenie relay for migrations, with roles at team and account level. We found no public information on SCIM provisioning or account-level audit logs.

PagerDuty

750+ native integrations, a documented REST API with versioning and scoped OAuth, bi-directional ServiceNow sync with CMDB table endpoints, and a free self-service developer programme mean the fit into a Prometheus-to-Slack stack is not in doubt. But we found no public information on a Terraform provider, SCIM provisioning, audit logs, multi-tenant setups for service providers, or migration help from other tools, and single sign-on appears on the captured pages only as a component name on the status page.

Platform reliability, security & compliance

ilert

Active/active AWS in Frankfurt and Stockholm with Dublin as disaster recovery, RTO within 60 minutes and RPO within 15 minutes, failover tested quarterly under production-like conditions, a public status page with per-component history, ISO 27001:2022 with its stated scope, annual external penetration tests with reports on request, and a DORA compliance package and addendum with audit, exit and step-in rights. A published SLA targets 99.9% web uptime and 99.9% of first-responder alerts delivered within five minutes, extendable to 99.99% on Enterprise. We found no public information on SLA credits, and SOC 2 Type II is a 2026 roadmap item rather than a certification.

PagerDuty

The pager's own operations are visible: a public status page with twenty-three components and history, an SLA that grants service credits, SOC 2 Type II, ISO 27001 and FedRAMP Low authorization, TLS 1.2+ in transit and AES 256+ at rest, customer-selectable regions, and an Assurance Portal for certifications and audit reports. We found no public information on multi-region failover being documented or tested, on the vendor's own post-incident reviews being public, or on anything offered for DORA or NIS2 customers.

European sovereignty

ilert

ilert GmbH of Cologne is the contracting entity and processor, the platform runs active/active on named AWS regions in Frankfurt and Stockholm, a GDPR Article 28 data processing agreement is published in English and German, and the sub-processor list names every provider with address, role, data location and transfer mechanism — the telecom carriers, Stripe in Ireland, HubSpot in Berlin, and the AI providers X.AI and Fly.io, which process only for accounts that enable AI and in EU regions. Twilio remains a US option for telecom and the AI vendors are US entities, disclosed with safeguards rather than absent, so the chain is transparent and mostly European but not sovereign end to end.

PagerDuty

The contracting entity is PagerDuty, Inc. of San Francisco under California law, but the chain is unusually transparent for a US vendor: an EU Service Region customers can choose, a published data processing agreement incorporating the Standard Contractual Clauses with transfer impact assessments, a full subprocessor list with locations, and ISO 27001 and SOC 2 stated, with an EU representative named. The generative-AI chain (AWS, Google, Microsoft, OpenAI) and much of analytics and support run through US providers, which keeps this below the top of the range.

Pricing transparency

ilert

All four plans carry public per-user prices with minimum seats — free up to five users, 19 € per user per month on Pro, 39 € per user per month on Scale, and Enterprise starting from 49 € per user per month — with SMS and voice volumes quantified per plan (100 on free, unlimited from Pro), AI credits stated per plan, and add-ons priced: inbound call routing at 10 € per user, per month, private status page at 125 € per month, audience-specific page at 50 € per month. We found no public information on annual versus monthly billing, VAT treatment, stakeholder seat pricing, or SMS and voice overage prices per country.

PagerDuty

Plans are public down to the numbers: a free tier, Professional at $25 per user per month and $21 billed annually, and platform tiers from a $2,800 to a $48,000 annual platform fee with quantified seats, AI Actions, Signal Intelligence Events and Live Call Routing lines, credit packs for scaling, and billing, minimum-commitment and VAT treatment in the terms. We found no public information on SMS and voice volumes or per-country prices, on prices for the separately purchased add-ons like AIOps, Status Pages and Runbook Automation, or on anything but "Custom Pricing" for the Ultimate tier.

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.

Fact ilert PagerDuty
Compliance · Breach notification notify controller without undue delay1

captured 6 Nov 2026 · Report an error

without undue delay · yes2

captured 6 Nov 2026 · Report an error

Compliance · Encryption 1.2 · yes · AWS KMS3

captured 6 Nov 2026 · Report an error

AES 256+ · TLS 1.2+4

captured 6 Nov 2026 · Report an error

Compliance · SOC 2 2026 · roadmap · annual3

captured 6 Nov 2026 · Report an error

Type II · yes5

captured 6 Nov 2026 · Report an error

Integrations · API base URL api.ilert.com/api · https6

captured 6 Nov 2026 · Report an error

https://api.pagerduty.com/7

captured 6 Nov 2026 · Report an error

Integrations · API reference yes8

captured 6 Nov 2026 · Report an error

yes9

captured 6 Nov 2026 · Report an error

Legal · Copyright ilert, copyright 2011-20268

captured 6 Nov 2026 · Report an error

2026 · PagerDuty, Inc.10

captured 6 Nov 2026 · Report an error

Legal · Entity address ilert GmbH · Bayenstr. 65, 50678 Köln11

captured 6 Nov 2026 · Report an error

94103 · San Francisco · CA · PagerDuty, Inc. · 600 Townsend St. #200 · USA12

captured 6 Nov 2026 · Report an error

Pricing · Free plan limit yes13

captured 6 Nov 2026 · Report an error

1 · none · yes14

captured 6 Nov 2026 · Report an error

Pricing · Free trial yes8

captured 6 Nov 2026 · Report an error

yes · no15

captured 6 Nov 2026 · Report an error

Product · Escalation policies intelligent escalation policies with routing rules based on priority and context16

captured 6 Nov 2026 · Report an error

yes15

captured 6 Nov 2026 · Report an error

Product · Escalation policy purpose Escalation policies guarantee alerts are delivered through various channels until acknowledged or resolved17

captured 6 Nov 2026 · Report an error

Escalation policies connect services to on-call schedules and ensure the right people are notified at the right time18

captured 6 Nov 2026 · Report an error

Product · Free features 1 · 10013

captured 6 Nov 2026 · Report an error

basic chat, limited email, push, SMS & phone notifications19

captured 6 Nov 2026 · Report an error

Product · Free trial Start for free option16

captured 6 Nov 2026 · Report an error

yes20

captured 6 Nov 2026 · Report an error

Product · Modules Alerting & Notifications · On-call Management & Escalations · Call Routing · Status Pages · Integrations · ChatOps · ilert AI21

captured 6 Nov 2026 · Report an error

Incident Management · Signal Intelligence · Runbook Automation · On-Call Management · Stakeholder Comms · Jeli15

captured 6 Nov 2026 · Report an error

Product · Notification channels push · SMS · phone call · WhatsApp · Telegram · email22

captured 6 Nov 2026 · Report an error

push · phone · slack · email · sms23

captured 6 Nov 2026 · Report an error

Product · Status page provider ilert24

captured 6 Nov 2026 · Report an error

PagerDuty9

captured 6 Nov 2026 · Report an error

Product · Status pages public · private · audience-specific25

captured 6 Nov 2026 · Report an error

yes15

captured 6 Nov 2026 · Report an error

Subprocessors · Aws Amazon Web Services EMEA SARL · Cloud Hosting · Frankfurt, Stockholm, Dublin · Privacy Framework, SCCs26

captured 6 Nov 2026 · Report an error

Amazon Web Services, Inc. · United States · Germany · Ireland · Cloud Computing/Data Warehouse Services/Telecom/Email Notification Services27

captured 6 Nov 2026 · Report an error

Subprocessors · Twilio Twilio Inc. · Telecommunication · United States (optional for EU customers) · SCCs, BCRs, Privacy Framework26

captured 6 Nov 2026 · Report an error

Twilio Inc. · United States · SMS & Voice/Telecom/Email Notification Services/User Experience Tools27

captured 6 Nov 2026 · Report an error

Subprocessors · Vonage Vonage B.V. · Telecommunication · Netherlands · N/A (EU-based)26

captured 6 Nov 2026 · Report an error

Vonage Business, Inc. · United States · United Kingdom · SMS & Voice/Telecom Notification Services27

captured 6 Nov 2026 · Report an error

Questions about ilert and PagerDuty

Which is better, ilert or PagerDuty?

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.