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 MSP NOC Lead

Leads the network operations centre of a managed service provider in Nuremberg that looks after sixty mid-sized customers, with Zabbix, Microsoft Sentinel and Autotask in the stack. Wants alerts routed by customer and contract hours, tickets opened and closed in the PSA without anyone copying text, a separate on-call rota for the night shift and for each key account, one customer never seeing another's data, and a monthly report per customer on response times.

ilert

This judge's pick

PagerDuty

Criterion by criterion

On-call schedules, rotations & escalation

ilert

Follow-the-sun rotations, shift swaps and one-time overrides handled from the mobile app, escalation timeouts across multiple levels with immediate escalation when a shift has no coverage, reminders before duty, calendar sync, and on-call reports of time on-call and alerts during it, with schedules and policies manageable through Terraform and the API. We found no public information on coverage gaps being flagged before they happen or on exporting on-call hours for pay and working-time rules, which keeps it below the top band.

PagerDuty

Schedules with layers, unlimited schedules and escalation policies on paid plans, easy shift overrides, calendar export to Outlook and iCal, and handoff reminders up to 48 hours ahead cover how I would build a night rota per key account; escalation policies with adjustable timeouts, up to 20 rules, nine repeats and optional round-robin assignment are well documented. We found no public information on exporting on-call hours for pay or working-time rules, and coverage-gap handling is only described as skipping to the next rule with an on-call responder, so I stop short of the top bands.

Alert delivery, routing & noise reduction

ilert

Redundant SMS and voice carriers are named (Twilio, Vonage, Bird) with automatic failover, notification limits per plan are stated (100 SMS/voice on Free, unlimited from Pro), and event flows route on payload fields and time conditions with transforms, waits and drops. AI merges similar alerts with a tunable similarity setting, heartbeats catch silent monitoring failures, acknowledgement works by SMS reply or keypad press, and the status page publishes notification-delivery uptime and a time-to-first-notification figure; we found no public information on delivery receipts per notification or measured noise-reduction results.

PagerDuty

Push, phone, SMS, email, WhatsApp and Slack delivery with acknowledgement by app, phone keypad or SMS reply, notification bundling and delays, suppression, maintenance mode, live call routing that follows the schedules, and alert grouping with five documented techniques gives me the routing-by-service behaviour I need for sixty customers. We found no public information on delivery receipts, heartbeat monitoring for silent failures, or the countries where SMS and voice are delivered, which is what separates a strong delivery story from a fully evidenced one.

Incident response, status pages & post-incident review

ilert

Incidents are declared from scratch or from an alert with pre-filled responders, severities, an incident commander, dedicated channels by default for the highest severities, timelines, public, private and audience-specific status pages with email, SMS and webhook subscribers, AI-drafted postmortems with action items, and MTTA/MTTR reports filterable by source and team. We found no public information on runbooks, per-incident video bridges or follow-up actions tracked into a tracker such as Jira, so it sits between the mid and high bands.

PagerDuty

Incidents declared from Slack, the app or by API with custom incident types, predefined Incident Commander and Customer Liaison roles plus custom roles, a filterable timeline, internal and public status pages with subscribers, post-incident reviews via Jeli, runbook automation and stakeholder communications are all documented, and the AI data handling states no customer data is used for training with customer choice offered. We found no public information on follow-up actions tracked into Jira or on MTTA and MTTR as reportable metrics, though analytics and a 70 percent MTTR reduction claim are published.

Integrations, API & administration

ilert

More than 150 inbound integrations including Zabbix, Checkmk, PRTG and Azure Sentinel, Datto Autotask named, and bi-directional sync with ServiceNow, Autotask and Zabbix on the Enterprise plan that writes acknowledgements and resolutions back to the source system — the ticketing round-trip my PSA runs on. A documented REST API with OpenAPI specification covering schedules, escalation policies, incidents and teams, a Terraform provider, SAML single sign-on and team-level plus account-wide roles are all documented; we found no public information on SCIM provisioning or account-level audit logs.

PagerDuty

750-plus native integrations, a documented REST API with ServiceNow endpoints including bi-directional CMDB sync on the top tier, Slack and Microsoft Teams ChatOps, teams tied to escalation policies and a sign-in with SSO service give me most of the plumbing, though the captured pages never name Autotask or ConnectWise specifically. We found no public information on audit logs, SCIM provisioning, a Terraform provider, multi-tenant separation for service providers, or migration help from other tools — the last matters most to me as an MSP.

Platform reliability, security & compliance

ilert

A public status page with component uptime and history, a 99.9% web and notification-delivery commitment per calendar month (up to 99.99% on Enterprise), active/active Frankfurt and Stockholm with Dublin as disaster recovery, quarterly failover testing, RTO and RPO targets, ISO 27001:2022 with its scope stated and the certificate on request, annual penetration tests, and a DORA addendum with audit rights. We found no public information on SLA credits, SOC 2 is only on a 2026 roadmap, and published failover test results or the vendor's own post-incident reviews are not shown.

PagerDuty

A public status page with per-service history and subscriptions, an SLA with service credits, SOC 2 Type II requestable through an assurance portal, ISO 27001 and FedRAMP Low authorization, AES 256 at rest and TLS 1.2 in transit, and three named SMS and voice carriers (Twilio, MessageBird, Vonage) give me most of an audit file. We found no public information on multi-region failover testing, penetration test results, or a DORA or NIS2 addendum, and data center regions are offered as a customer choice rather than documented redundancy.

European sovereignty

ilert

ilert GmbH in Cologne is the contracting entity, hosting runs on named AWS regions in Frankfurt and Stockholm, the data processing agreement is published, and the subprocessor list is public with roles and locations: Bird and Vonage in the Netherlands for telecoms, Stripe in Ireland, and the AI providers X.AI and Fly.io processing in EU regions only for accounts with AI enabled. Several chain members are US companies handled under standard contractual clauses and Twilio is marked optional for EU customers, and we found no public information on the ownership structure beyond the GmbH, so sovereignty is not proven end to end.

PagerDuty

The contracting entity is PagerDuty, Inc. of San Francisco under California law, but customers can choose an EU service region hosted on named AWS infrastructure in Germany and Ireland, the subprocessor list is published with locations and an RSS feed, and a data processing addendum incorporating the EU Standard Contractual Clauses with transfer impact assessments is public. The chain still runs through United States providers for the generative AI models (AWS, Google, Microsoft, OpenAI) and much of the telephony, with SCCs as the stated safeguard rather than a European entity, which for my German customer base is why I sit in the middle band.

Pricing transparency

ilert

All four plans carry a public per-user price with minimum seats, the free tier states its 100 SMS/voice notifications and single status page, and add-ons are priced (inbound call routing at 10 € per user, per month, private status page at 125 € per month, audience-specific page at 50 € per month) alongside per-plan AI credits. We found no public information on annual versus monthly billing, VAT treatment, stakeholder seat pricing, per-country SMS costs or what happens beyond the free 100 notifications, which blocks full cost computability.

PagerDuty

Published prices are unusually concrete in places — a free plan at $0, Professional at $25 per user per month or $21 billed annually, and platform fees of $2,800, $12,000 and $48,000 per year with stated seats, Signal Intelligence events and AI Actions included — plus annual-in-advance billing, net 30 terms and taxes as the customer's responsibility. But the top tier is custom pricing, add-ons such as status pages, AIOps and Advance are named without prices, stakeholder seats and SMS or voice volumes are not explained, so I cannot compute the real annual cost for my sixty customers from the public pages alone.

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.