ilert
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 3 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by ilert GmbH · www.ilert.com
Compare with PagerDuty → Compare with All Quiet → Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
ilert at a glance
- Vendor
- ilert GmbH
- Headquarters
- Incorporated in Germany source, captured 6 Nov 2026
- Data hosting
- In the EU by default source, captured 6 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 6 Nov 2026
- Panel verdict
- The AI panel rates ilert 4/5, the mean of 6 judges. ilert, an on-call and incident management platform from ilert GmbH, scores highest on alerting and routing and sovereignty: judges credit push, SMS, voice, WhatsApp, Telegram and email, critical alerts that bypass do-not-disturb, carriers Twilio, Vonage and Bird with automatic failover, and, in sovereignty, a public data processing agreement and a subprocessor list naming every provider — judges weigh US-incorporated processors under safeguards differently. how scores are made
- As of
- Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
ilert, an on-call and incident management platform from ilert GmbH, scores highest on alerting and routing and sovereignty: judges credit push, SMS, voice, WhatsApp, Telegram and email, critical alerts that bypass do-not-disturb, carriers Twilio, Vonage and Bird with automatic failover, and, in sovereignty, a public data processing agreement and a subprocessor list naming every provider — judges weigh US-incorporated processors under safeguards differently. Reliability and compliance is a flat 8 (active/active AWS Frankfurt and Stockholm, Dublin recovery, ISO 27001:2022, SOC 2 Type II a 2026 roadmap item). On-call scheduling is flat at 7: we found no public information on round-robin escalation, coverage-gap warnings or on-call hours exported for pay and working-time rules. Pricing transparency scores 6–7 — tier prices are public (Pro 19 €, Enterprise from 49 € per user per month), but annual-versus-monthly billing, VAT treatment and overages are not. Judges split 7–8 on incident response and integration: higher scores credit status pages, AI postmortems and 150-plus integrations with Terraform; lower ones cite no public information on runbooks, follow-up tracking, SCIM or audit logs. flagged splits: none.
Speaks for it
- Notification runs across push, SMS, voice, WhatsApp, Telegram and email, with critical alerts bypassing do-not-disturb and acknowledgement by SMS reply or keypad.
- Named carriers Twilio, Vonage and Bird with automatic failover, and a published target of 99.9 percent of first-responder alerts delivered within five minutes.
- Active/active AWS Frankfurt and Stockholm with Dublin disaster recovery, quarterly failover tests under production-like conditions, and recovery targets of 60 minutes and 15 minutes.
- A public Article 28 data processing agreement offering deletion or certified return on exit, and a public subprocessor list naming every provider with location and transfer mechanism.
- More than 150 inbound integrations, a Terraform provider, a documented REST API with an OpenAPI specification, and migration paths from Atlassian Statuspage and Opsgenie.
Held against it
- We found no public information on round-robin escalation, coverage gaps flagged before they happen, or exporting on-call hours for pay and working-time rules.
- We found no public information on annual-versus-monthly billing, VAT treatment, or SMS, voice and AI-credit overage prices, so the true annual cost is not derivable from public pages.
- We found no public information on SCIM provisioning or an exportable account-level audit log.
- SOC 2 Type II appears on a 2026 roadmap rather than held, and we found no public information on SLA credits for missed targets.
- US-incorporated companies (Twilio, X.AI, Fly.io, PostHog) appear in the subprocessor list under stated safeguards, and we found no public information on the ownership behind the GmbH.
Best for
- You page people at night and need critical alerts to bypass do-not-disturb, with named carrier failover behind SMS and voice.
- You are an EU financial-sector operator: judges found a DORA addendum with audit, exit and step-in rights, a four-hour incident notice and TLPT cooperation directly usable for reporting.
- You manage schedules and escalation policies as code, through a Terraform provider and a documented REST API with an OpenAPI specification.
- Your monitoring stack is Zabbix, Checkmk, PRTG, Prometheus or Datadog, with bidirectional ServiceNow and Autotask sync available on the Enterprise plan.
Avoid if
- You need SOC 2 Type II certification in hand today — it appears as a 2026 roadmap item rather than a held certificate.
- Your process depends on publishing AI-drafted postmortems to status pages automatically — the feature is marked beta and its publishing settings are documented as not taking effect yet.
- You must export per-person on-call hours for payroll and working-time compliance — on-call scheduling scored a flat 7 and we found no public information on such exports.
- You must compute the full annual cost from public pages — ask the vendor: the public pages we read do not show it
The scores
| Criterion | Panel median |
|---|---|
| On-call schedules, rotations & escalation | 3.5 of 5 |
| Alert delivery, routing & noise reduction | 4.5 of 5 |
| Incident response, status pages & post-incident review | 4 of 5 |
| Integrations, API & administration | 4 of 5 |
| Platform reliability, security & compliance | 4 of 5 |
| European sovereignty | 4 of 5 |
| Pricing transparency | 3.5 of 5 |
On-call schedules, rotations & escalation
Show reasoningHide reasoning
How this is scored
Who is on call and what happens when nobody answers: schedules with daily, weekly and custom rotations, layers and follow-the-sun hand-offs across time zones, overrides, swaps and holiday cover, escalation policies with timeouts, repeat and fallback levels, round-robin and team escalation, calendar export and sync, reminders before a shift, on-call reports and hours exported for on-call pay and working-time rules, and a mobile app that shows the shift and lets a responder hand it over.
0 — No schedules or escalation of any kind; alerts go to a fixed list of people.
3 — A simple weekly rotation and one escalation step; overrides, layers, time zones and on-call reports are basic or not described.
5 — Schedules with several rotation types and layers, overrides and swaps from the app, escalation policies with timeouts and several levels, time-zone handling, calendar export, shift reminders, and a report of who was on call when.
8 — Follow-the-sun and multi-team schedules, round-robin and conditional escalation, coverage gaps flagged before they happen, schedules and policies managed as code or by API, and on-call hours exported per person for pay and working-time rules, all documented.
10 — Scheduling a large organisation runs on: every feature above with fairness and fatigue reports, rest-period rules enforced or warned, schedules imported from HR or workforce tools, and every scheduling limit documented per plan.
The SRE Lead
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. 1 2 3 19 20
The IT Operations Manager
The weekly standby our five administrators share is described almost verbatim — recurring schedules with a week-per-member example, static drag-and-drop shifts, overrides and shift swaps handled from the mobile app, and an escalation timeout that turns my ten-minute deputy rule into automatic escalation to the next level, with no-coverage times escalating immediately. Follow-the-sun scheduling, iCal calendar export, shift reminders by SMS, email and push, on-call reports with time on-call and alerts during duty, and management of schedules and policies through Terraform and the REST API are all documented. We found no public information on round-robin escalation, advance warning of coverage gaps before they happen, or exporting on-call hours for pay and working-time rules. 19 20 2 3 26
The MSP NOC Lead
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. 1 2 3 19 20
The ICT Risk Officer
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. 1 2 3 19 20
The Engineering Manager
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. 3 19 20 2 26
The Skeptic
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. 19 20 3 2 26
Alert delivery, routing & noise reduction
Show reasoningHide reasoning
How this is scored
Whether the alert reaches a human and only the right one: notification by push, SMS, voice call, email and chat, critical alerts that override do-not-disturb on iOS and Android, personal notification rules with retries and fallbacks, acknowledgement by app, SMS reply or keypad, delivery receipts, live call routing for a hotline, routing rules by service, severity, payload and time, deduplication, grouping and correlation of related alerts, suppression and maintenance windows, heartbeats for silent failures, and inbound email and webhook endpoints.
0 — Sends no alerts to people; a dashboard or log viewer only.
3 — Push and email notifications with acknowledgement; SMS, voice, routing rules and noise reduction are basic or not described.
5 — Push, SMS, voice and email with personal notification rules and retries, critical alerts on mobile, acknowledgement from the app or by phone, routing by service and severity, deduplication, and maintenance windows.
8 — Alert grouping or correlation with its logic documented, routing on payload fields and time conditions, delivery receipts and a notification log per alert, live call routing, heartbeat monitoring, suppression rules, and the countries and channels where SMS and voice are delivered stated.
10 — Delivery that is evidenced, not promised: redundant SMS and voice carriers named with automatic failover, delivery statistics published, AI or rule-based noise reduction with measurable results, and every notification limit per plan documented.
The SRE Lead
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. 2 4 21 22 28
The IT Operations Manager
This is the closest match to my exact requirement I have read: alerts go out by push, SMS, voice call, WhatsApp, Telegram and email, with acknowledgement by "pressing a number during a phone call" or SMS reply, critical alerts that bypass do-not-disturb on Android and iOS, maintenance windows to stop pages during planned work, and heartbeat monitoring for silent failures — and the delivery side names Twilio, Vonage and Bird as telecom providers with automatic failover between them plus a published target of 99.9% of first-responder alerts delivered within five minutes. Grouping exists as time-based and AI-semantic with its logic and tunable similarity setting stated, routing on payload fields and time conditions is documented through event flows, and an SMS alert source accepts events without an internet connection. We found no public information on measurable noise-reduction results or per-channel delivery statistics, and delivery receipts per notification are not separately documented. 2 4 20 21 22 18 28
The MSP NOC Lead
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. 2 4 8 12 22 28
The ICT Risk Officer
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. 2 4 8 12 21 22 28
The Engineering Manager
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. 2 4 22 28
The Skeptic
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. 2 4 22 28 12
Incident response, status pages & post-incident review
Show reasoningHide reasoning
How this is scored
What happens once the alert is a real incident: declaring an incident from Slack, Microsoft Teams or the app, a dedicated channel and video bridge, incident roles and commander, severities and incident types, runbooks, tasks and automated workflows, stakeholder updates, public and internal status pages with subscribers, a timeline, post-incident reviews and postmortem templates with follow-up actions, analytics such as MTTA and MTTR, and AI features that summarise, suggest causes or draft the review.
0 — No incident record of any kind beyond the alert itself.
3 — An incident list with status and notes; channels, roles, status pages and post-incident reviews are basic or not described.
5 — Incidents declared from chat or the app with severities, a Slack or Teams channel created, incident roles, a timeline, a public status page, stakeholder notifications, postmortem templates, and MTTA and MTTR reports.
8 — Workflows and runbooks that automate the response, incident types with their own process, internal and public status pages with components and subscribers, follow-up actions tracked into Jira or Linear, service catalogue and dependencies, and AI summaries with their data handling described.
10 — A response process a regulated enterprise runs on: every feature above with major-incident and regulatory reporting templates, cross-team analytics and learning reviews, AI features documented with model provider, data handling and an opt-out, and every limit per plan stated.
The SRE Lead
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. 2 5 6 18 23 24
The IT Operations Manager
Declaring an incident from an alert pre-fills the title, summary, affected services and responders, SEV1 and SEV2 open a dedicated channel by default, an incident commander role exists, and postmortems are drafted by AI from the timeline, linked alerts, deployment events and chat transcripts into sections including root cause analysis and action items. Public, private and audience-specific status pages with email, SMS and webhook subscribers, plus MTTA and MTTR reports filterable by source and team, are documented. The documentation itself states up front that the postmortem publishing settings do not take effect yet, and we found no public information on runbooks, incident types with their own process, service dependencies, or follow-up actions tracked into Jira or Linear. 23 24 2 5 6
The MSP NOC Lead
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. 2 5 6 23 24
The ICT Risk Officer
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. 2 5 6 18 23 24
The Engineering Manager
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. 23 2 24 6 18
The Skeptic
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. 23 24 2 5 6
Integrations, API & administration
Show reasoningHide reasoning
How this is scored
How the tool fits the stack and the organisation: inbound integrations with monitoring and observability tools (Prometheus, Grafana, Datadog, Zabbix, Checkmk, PRTG, Azure Monitor, CloudWatch, Sentry), outbound integrations with chat, ticketing and ITSM tools (Slack, Microsoft Teams, Jira, ServiceNow, ConnectWise, Autotask), bidirectional sync, a documented REST API, webhooks and a Terraform provider, teams and services, roles and permissions, single sign-on (SAML or OIDC) and SCIM, audit logs, multi-tenant or customer separation for service providers, and migration help from other tools.
0 — No integrations and no administration beyond a single shared account.
3 — Email and webhook intake and a few named integrations; the API, roles and single sign-on are basic or not described.
5 — Dozens of named inbound and outbound integrations including Slack or Teams and Jira, a documented REST API and webhooks, teams with roles, two-factor authentication, single sign-on, and an import path from at least one other tool.
8 — Bidirectional ITSM and ticketing sync, a Terraform provider or configuration as code, SCIM provisioning, granular roles per team, audit logs, service-provider or multi-tenant set-ups, and API coverage of schedules, escalations and incidents documented.
10 — Administration that scales across many teams and customers: every setting reachable by API with parity stated, audit logs exportable to a SIEM, SSO enforced with SCIM, white-label or sub-account management for service providers, and documented migration from the major competitors.
The SRE Lead
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. 2 6 7 22 25 26
The IT Operations Manager
Both of my monitoring stacks — Checkmk and PRTG Network Monitor — are named among more than 150 inbound integrations, outbound actions open Jira issues, call webhooks or send email, and bi-directional sync with ServiceNow, Autotask, Zabbix and Auvik is documented at the Enterprise tier. A REST API with an OpenAPI specification, documented rate limits and coverage of schedules, escalation policies and incidents, a Terraform provider included even in the free tier, account-wide and team-level roles with SAML single sign-on, and migration paths from Atlassian Statuspage and Opsgenie are all public. We found no public information on SCIM provisioning, administrative audit logs, or multi-tenant set-ups for service providers. 4 8 25 26 2 6 7
The MSP NOC Lead
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. 2 7 8 25 26
The ICT Risk Officer
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. 2 7 8 10 25 26
The Engineering Manager
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. 8 2 26 10 7
The Skeptic
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. 8 7 26 2 10
Platform reliability, security & compliance
Show reasoningHide reasoning
How this is scored
Whether the pager works on the day everything else is down and holds up in an audit: an architecture independent of the customer's own cloud, multi-region or multi-zone hosting with failover, a stated availability or SLA with credits, the vendor's own public status page and incident history, delivery via redundant carriers, encryption in transit and at rest, security certifications (ISO 27001, SOC 2, BSI C5), penetration tests, data retention and deletion, audit trails, and what the vendor documents for DORA, NIS2, HIPAA or other regulated customers.
0 — Nothing on availability, security or how the service is operated.
3 — A claim of high availability or "enterprise security"; the SLA, status page, certifications and architecture are basic or not described.
5 — A public status page, a stated availability or SLA, hosting regions named, encryption in transit and at rest, ISO 27001 or SOC 2 stated, and data retention described.
8 — An SLA with credits published, the incident history public, multi-region failover or redundancy documented, redundant notification carriers named, certifications with their scope, a trust centre with reports on request, and a DORA or NIS2 addendum or mapping offered.
10 — Operation evidenced end to end: failover tested and published, independent audits (ISO 27001, SOC 2 Type II, BSI C5) with reports available, regulatory obligations for financial and critical-infrastructure customers explained in plain language, and the vendor's own post-incident reviews public.
The SRE Lead
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. 10 11 12 27 28
The IT Operations Manager
The pager keeps working when our own plant network is the thing that is down: active/active hosting on AWS in Frankfurt and Stockholm with Dublin for disaster recovery, failover tested quarterly under production-like conditions, RTO within 60 minutes and RPO within 15 minutes, and named telecom providers with automatic failover. A public status page with per-component uptime and incident history, a 99.9% monthly uptime and notification-delivery SLA extendable to 99.99% at Enterprise, ISO 27001:2022 with its scope stated, annual external penetration tests, customer audit rights and a DORA addendum with exit and step-in rights are all documented. We found no public information on SLA credits, SOC 2 beyond a 2026 roadmap entry, or the vendor's own published post-incident reviews. 28 11 12 10 27 18
The MSP NOC Lead
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. 11 12 27 28
The ICT Risk Officer
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. 10 11 12 28
The Engineering Manager
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. 28 11 12 10
The Skeptic
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. 28 11 12 10
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where alerts, incident timelines, chat transcripts, contact data, phone numbers and account data are stored and processed, and who the subprocessors are (hosting, SMS and voice carriers, push services, email delivery, AI summary and transcription models, analytics, support and payment tools). Independently sourced by the sovereignty pipeline. Telephony and push providers needed to reach a responder in another country are part of what the product does and are not counted against it; where the data is stored and who processes it is. A self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (SMS and voice, AI, support, payment) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every record on the customer's own servers.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor including the AI models and notification carriers, or a self-hosted edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.
The SRE Lead
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. 10 11 14 17 18
The IT Operations Manager
The contracting entity is ilert GmbH in Cologne with a German commercial register number, the platform runs active/active on AWS in Frankfurt and Stockholm, and a published sub-processor list names each provider with its role, location and transfer mechanism — including Vonage and Bird in the Netherlands for telephony, X.AI processing AI features in an EU region on an opt-in-only basis, and Twilio as an explicitly optional United States choice for EU customers. A public data processing agreement offering deletion or certified return at the controller's choice, thirty days' notice of sub-processor changes with a right to object, and ISO 27001 certification round out the chain. United States entities such as HubSpot, PostHog and Fly.io appear in the list with EU processing locations and standard contractual clauses, and we found no public information on the ownership behind the GmbH. 14 15 11 18 17 10 28
The MSP NOC Lead
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. 10 11 17 18
The ICT Risk Officer
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. 1 11 14 17 18
The Engineering Manager
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. 18 14 11 17 10
The Skeptic
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. 18 17 14 11 16
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per user or responder and per plan, whether stakeholders and viewers are free, how many SMS and voice notifications are included and what the rest cost per country, which features (incident response, status pages, AI, live call routing, SSO, audit logs) are add-ons or in higher plans, platform fees, minimum seats, annual versus monthly billing, and the currency and VAT treatment.
0 — No public prices at all; every customer is a sales call.
3 — A starting price per user exists, but notification limits, add-ons and the enterprise tier are unclear.
5 — Plans are public with their price per user and main inclusions, but at least one commonly needed piece (SMS and voice volume, status pages, AI, SSO or the top tier) is unpriced or "contact sales".
8 — Every plan priced publicly with its scaling rule, notification limits and overage prices stated, add-ons priced, stakeholder seats explained, minimum term and billing options and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given number of responders, stakeholders, notifications and status pages, with every add-on, overage and support fee and the cancellation and data-export terms published.
The SRE Lead
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. 2 9 28
The IT Operations Manager
Four plans carry public per-user prices — free up to 5 users with 100 SMS / voice notifications, Pro at 19 € per user per month with min. 3 users including unlimited SMS and voice and single sign-on, Scale at 39 € per user per month with min. 3 users, and Enterprise starting from 49 € per user per month — with priced add-ons such as inbound call routing at 10 € per user, per month and private status pages at 125 € per month, and support stated as included in all plans. What I still cannot compute is the true annual cost: we found no public information on annual versus monthly billing, VAT treatment, stakeholder seat pricing, or what happens past the 100 notifications on the free plan. 9 2 28
The MSP NOC Lead
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. 2 9
The ICT Risk Officer
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. 2 9
The Engineering Manager
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. 9 2
The Skeptic
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. 9 2 28
European sovereignty — proven facts
3 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Incorporated in DE | 2/2 pts | 14 Report an error |
|---|---|---|---|
| Hosting location |
EU by default
unverified
Why unverified?Platform hosting itself is stated to run exclusively on EU data centres (Frankfurt/Stockholm/Dublin per the security page); only optional sub-processor paths such as Twilio place data outside the EU. |
2/4 pts | 18 Report an error |
| Hosting options |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Published, self-serve | 1/1 pts | 10 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about ilert
Is ilert European?
Yes. whats-best.ai classifies ilert as EU-Made. Its vendor, ilert GmbH, is incorporated in Germany, per the vendor’s page captured 6 Nov 2026.
Where does ilert store data?
ilert stores customer data in the EU by default, though not exclusively, per the vendor’s page captured 6 Nov 2026.
Does ilert have a free plan?
Yes. ilert has a free plan, per the vendor’s page captured 6 Nov 2026.
What are the best alternatives to ilert?
As of 18 Nov 2026, the panel rates All Quiet (3.5/5), OneUptime (3.5/5) and FireHydrant (3/5) highest among the other 16 On-Call & Incident Management products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is All Quiet (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: ilert alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 6 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Hosting location. Platform hosting itself is stated to run exclusively on EU data centres (Frankfurt/Stockholm/Dublin per the security page); only optional sub-processor paths such as Twilio place data outside the EU.
- Weak sourcing — Hosting options. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 35 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 6 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 5 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 5 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 5 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 hosting fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (28)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.ilert.com Checked 6 Nov 2026 Details →
- 2 Features page www.ilert.com Checked 6 Nov 2026 Details →
- 3 Features page (on-call and escalations) www.ilert.com Checked 6 Nov 2026 Details →
- 4 Features page (alerting) www.ilert.com Checked 6 Nov 2026 Details →
- 5 Features page (incident management) www.ilert.com Checked 6 Nov 2026 Details →
- 6 Features page (status pages) www.ilert.com Checked 6 Nov 2026 Details →
- 7 Integrations page www.ilert.com Checked 6 Nov 2026 Details →
- 8 Documentation docs.ilert.com Checked 6 Nov 2026 Details →
- 9 Pricing page www.ilert.com Checked 6 Nov 2026 Details →
- 10 Security / trust page www.ilert.com Checked 6 Nov 2026 Details →
- 11 Compliance page (DORA) www.ilert.com Checked 6 Nov 2026 Details →
- 12 Public status page status.ilert.com Checked 6 Nov 2026 Details →
- 13 About page www.ilert.com Checked 6 Nov 2026 Details →
- 14 Legal notice www.ilert.com Checked 6 Nov 2026 Details →
- 15 Terms of service www.ilert.com Checked 6 Nov 2026 Details →
- 16 Privacy policy www.ilert.com Checked 6 Nov 2026 Details →
- 17 Data processing agreement (dpa) www.ilert.com Checked 6 Nov 2026 Details →
- 18 Subprocessor list www.ilert.com Checked 6 Nov 2026 Details →
- 19 On-call schedules, rotations & escalation — found from sitemap docs.ilert.com Checked 6 Nov 2026 Details →
- 20 On-call schedules, rotations & escalation — found from sitemap docs.ilert.com Checked 6 Nov 2026 Details →
- 21 Alert delivery, routing & noise reduction — found from sitemap docs.ilert.com Checked 6 Nov 2026 Details →
- 22 Alert delivery, routing & noise reduction — found from sitemap docs.ilert.com Checked 6 Nov 2026 Details →
- 23 Incident response, status pages & post-incident review — found from sitemap docs.ilert.com Checked 6 Nov 2026 Details →
- 24 Incident response, status pages & post-incident review — found from sitemap docs.ilert.com Checked 6 Nov 2026 Details →
- 25 Integrations, API & administration — found from sitemap docs.ilert.com Checked 6 Nov 2026 Details →
- 26 Integrations, API & administration — found from sitemap docs.ilert.com Checked 6 Nov 2026 Details →
- 27 Platform reliability, security & compliance — found from sitemap docs.ilert.com Checked 6 Nov 2026 Details →
- 28 Platform reliability, security & compliance — found from sitemap docs.ilert.com Checked 6 Nov 2026 Details →