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

Engineering manager at a logistics software company in Hamburg with developers in Germany, Portugal and Poland, where the works council has agreed an on-call policy with paid standby hours and rest periods after a night call. Wants a follow-the-sun rota across three time zones, swaps from the phone, on-call hours exported to payroll each month, a warning when the same person is paged three nights running, and a price per responder that does not charge for the managers who only read along.

ilert

This judge's pick

PagerDuty

Criterion by criterion

On-call schedules, rotations & escalation

ilert

Follow-the-sun schedules, shift swaps and overrides handled from the mobile app, escalation policies with timeouts, several targets per level and immediate escalation when coverage is missing, shift reminders and calendar export are all documented, and on-call reports give time on-call per person while schedules and escalation policies are manageable through the API and Terraform — that covers our three-time-zone rota and the monthly payroll export well enough. What I do not see for the works council is any fatigue dimension: we found no public information on fairness or fatigue reports that would warn when the same person is paged three nights running, or on rest-period rules.

PagerDuty

Schedules with layers, rotation templates, easy shift overrides, revert, calendar export to Outlook, Google Calendar and iCal, on-call handoff reminders up to 48 hours ahead, and escalation policies with up to 20 rules, adjustable timeouts and up to nine repeats are all documented, and the on-call pages also cover multi-timezone schedules, shift swaps, conflict detection, schedule templates and managing schedules by API, with round-robin assignment behind a feature gate. We found no public information on exporting on-call hours per person for payroll and working-time rules, nor on fatigue or rest-period warnings — both essential under our works council agreement.

Alert delivery, routing & noise reduction

ilert

Push, SMS, voice, email, WhatsApp and Telegram are documented with critical alerts overriding do-not-disturb on Android and iOS, acknowledgement by SMS reply or keypad, time-based and AI semantic grouping, maintenance windows, heartbeats, and event flows that branch on payload fields and time conditions; the telecom carriers are named with automatic failover between them. We found no public information on delivery receipts per notification or on measured noise-reduction results, and delivery statistics appear only as component uptime on the status page.

PagerDuty

Push, phone, SMS, email and WhatsApp delivery with acknowledgement by phone keypad or SMS reply, bundling across all channels, delays in personal notification rules, suppression and maintenance mode, and live call routing that turns voicemails into incidents are documented, and alert grouping has five named techniques with auto-pause for transient alerts, while each incident's timeline logs the notifications sent. We found no public information on heartbeats for silent failures, delivery receipts, critical alerts overriding do-not-disturb on mobile, or the countries where SMS and voice are delivered.

Incident response, status pages & post-incident review

ilert

Incidents with severities, an incident commander, dedicated channels, a timeline, public, private and audience-specific status pages with email, SMS and webhook subscribers, MTTA and MTTR reports and AI-drafted postmortems with five sections are documented, and the AI providers and their opt-in handling are listed publicly. For our process we found no public information on declaring an incident directly from Slack or Teams (alerts can be raised from chat), on runbooks, or on follow-up actions tracked into Jira, and the postmortem generation is marked beta with publishing settings the documentation says do not take effect yet.

PagerDuty

Incidents can be declared from Slack, the web and mobile apps, email or the API, with Incident Commander and Customer Liaison roles plus custom roles usable in Slack, Teams and workflows, severities, a filterable timeline, post-incident reviews and Jeli incident analysis, internal and external status pages, stakeholder communications, and incident workflows and runbook automation; the captured pages also state that no customer data is used for AI training, with a detailed AI disclosure available on request. We found no public information on follow-up actions tracked into Jira or Linear, subscribers and components on customer status pages, or MTTA and MTTR reporting.

Integrations, API & administration

ilert

More than 150 inbound integrations including our stack names (Prometheus, Datadog, Zabbix, Checkmk, PRTG), a documented REST API with an OpenAPI spec covering schedules, escalation policies, incidents and status pages, a Terraform provider, client libraries, team-level and account-wide roles, SAML single sign-on, two-factor authentication, bidirectional ServiceNow and Autotask sync on Enterprise, and migration paths from Atlassian Statuspage and Opsgenie. We found no public information on SCIM provisioning, on audit logs as an administrative feature, or on multi-tenant administration for service providers.

PagerDuty

750+ integrations including Slack and Microsoft Teams, a documented REST API with versioning, rate limits and scoped OAuth, teams with roles and permissions, and ServiceNow bi-directional custom field sync on the top platform tier are evidenced, and single sign-on appears as a live service on the vendor's status page. We found no public information on SCIM provisioning, audit logs, a Terraform provider, two-factor authentication details, or migration help from other tools.

Platform reliability, security & compliance

ilert

Active/active AWS Frankfurt and Stockholm with Dublin as disaster recovery, recovery targets of 60 minutes and 15 minutes, quarterly failover tests, a published SLA of 99.9% web availability (up to 99.99% on Enterprise) plus 99.9% of first-responder alerts delivered within five minutes, a public status page with incident history, ISO 27001:2022 with its scope stated, annual penetration tests with reports on request, and a DORA addendum alongside NIS2 support. We found no public information on SLA credits, and SOC 2 Type II is shown on a 2026 roadmap rather than held.

PagerDuty

A public status page with per-service status and history, service credits under a published SLA, SOC 2 Type II, ISO 27001 and FedRAMP Low authorization, AES 256 at rest and TLS 1.2+ in transit, customer choice of hosting region, an assurance portal with reports on request, and three named telecom carriers for SMS and voice give a strong compliance picture. We found no public information on multi-region failover, penetration tests, or support for DORA and NIS2 obligations.

European sovereignty

ilert

ilert GmbH of Cologne is the contracting entity, hosting runs active/active in AWS Frankfurt and Stockholm with Dublin recovery, the public sub-processor list names every provider with location and transfer mechanism — telecoms (Vonage and Bird in the Netherlands, Twilio optional), AI (X.AI in an EU region, only for accounts with AI enabled) and payments (Stripe Ireland) — and a public data processing agreement plus ISO 27001 with scope are in place. We found no public information on the ownership structure, and Twilio, X.AI, Fly.io and PostHog are US-incorporated companies processing in the EU under stated safeguards.

PagerDuty

The contracting entity is PagerDuty, Inc. of San Francisco under California law, but an EU service region is offered, the subprocessor list is published with locations — including AWS in Germany and Ireland and three SMS and voice carriers — and a data processing agreement incorporating the Standard Contractual Clauses with transfer impact assessments is public, alongside a named EU representative. The published list shows the generative AI services run through United States providers (AWS, Google, Microsoft and OpenAI), which my works council will want to weigh before approving AI features.

Pricing transparency

ilert

All four plans carry a public price per user per month with minimum seats (Free up to 5 users; Pro and Scale from 3 users at 19 € and 39 €; Enterprise from 49 €), notification volumes are stated (100 SMS and voice on Free, unlimited from Pro up), add-ons are priced (inbound call routing 10 € per user, per month; private status page 125 € per month), AI credits per plan are listed, and Pro includes unlimited read-only viewer users — which matters to us, since managers who only follow along would cost nothing. We found no public information on VAT treatment, on annual-versus-monthly billing options, or on the minimum term.

PagerDuty

The Free plan, Professional at "$25" per user per month monthly and "$21" annually, and platform tiers of "$2,800", "$12,000" and "$48,000" per year with "Custom Pricing" for Ultimate are public, including seat counts, included Signal Intelligence Events, AI Actions and live call routing lines, billing annually in advance, and taxes on the customer. The top tier is custom-priced, the separately purchased add-ons such as status pages, AI and live call routing carry no public prices, and we found no public information on SMS and voice volumes, overage rates per country, or what a seat for a manager who only reads along costs.

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.