Uptimeify vs. ilert
ilert is a German alerting and on-call tool with plenty of integrations and its own app. ilert has discontinued its uptime monitoring, though, and it hosts on AWS. On Uptimeify, monitoring and incident management run on one platform, with no US subprocessors and with NIS2-ready exports.
For agencies and MSPs
- No US subprocessors, hosting in the EU
- Monitoring, incident management and status pages on one platform
- NIS2-ready exports, you file the report
- Incident roles, postmortems and audit log
- On-call scheduling with rotations (beta) and escalation tiers
For IT and DevOps teams
- Customer data on AWS in Frankfurt and Stockholm
- Own monitoring only as heartbeats
- Own app plus Slack and Teams workflows
- Incident roles and postmortem library from Scale, 39 USD per user a month
- Audit trail on the Enterprise plan, from 49 USD per user a month
As of November 2026. Details on ilert are based on publicly available information and may change. Prices in the source's original currency, not converted, with annual billing. On Uptimeify, on-call scheduling, acknowledgement and incident timeline are currently in beta. If something is wrong, we are glad to hear about it.
In short
ilert is a mature on-call and alerting tool built for IT and DevOps teams. More than 150 integrations, its own app and workflows in Slack and Teams make it strong when your monitoring is already in place and you mainly need the alerting chain. Customer data sits in AWS data centers in Frankfurt and Stockholm.
For agencies and MSPs, something is missing from the same platform: ilert has discontinued its uptime monitoring, and heartbeat monitoring is what remains. And much of what comes after the alert sits in higher plans: incident roles and the postmortem library from Scale, the audit trail on the Enterprise plan.
Uptimeify starts right there: your checks, incident management and your status pages run on one platform, with NIS2-ready exports. You file the report. Every provider that processes your incident data is a European company.
Feature by feature
As of November 2026. Details on ilert are based on publicly available information and may change. On Uptimeify, on-call scheduling, acknowledgement and incident timeline are currently in beta. All trademarks belong to their respective owners.
Where Uptimeify leads
Three things ilert solves differently, and that we built for your agency.
Monitoring and incident management on one platform. ilert discontinued its uptime monitoring, for new customers from January 2023 and for good after 30 June 2024. Heartbeat monitoring is what remains. On Uptimeify, your own checks are an alert source with no integration needed, and status page rules update your status page automatically from sev2, so you maintain one tool for websites, servers and the alerting chain.
NIS2-ready exports for your report cases. ilert documents general exports: reports as CSV, print to PDF from Pro, the audit trail on the Enterprise plan. On Uptimeify, a report case tracks the 24-hour, 72-hour and one-month deadlines, prepares report drafts in German or English and freezes the submitted version with the BSI reference. You file the report, Uptimeify keeps the evidence.
No US subprocessors for your incident data. ilert stores customer data in the EU, on AWS in Frankfurt and Stockholm. AWS is a US group, and according to the subprocessor list, AI features run through OpenAI, Anthropic and xAI. Uptimeify hosts at Hetzner, OVH, netcup, UpCloud and IONOS, and SMS and calls go through seven.io with LOX24 in Germany. The optional app push runs encrypted through Apple and Google, and Apple and Google do not read the content.
Where ilert wins
No tool wins everywhere. Three points where ilert is the better choice.
Work alerts right in Slack and Teams. With ilert, you accept, reroute and resolve alerts in Slack and Microsoft Teams, and from Scale you also get dedicated incident channels. Uptimeify sends incidents to Slack and Microsoft Teams, but you can
A fully built-out app. ilert has its own iOS and Android apps with critical push notifications. You take or give away shifts right in the app, including overrides and coverage requests, and there is an on-call widget too.
Breadth and maturity. More than 150 integrations, a Terraform provider in the partner tier of the Terraform Registry and a hosted MCP server. According to ilert, companies such as REWE and adesso rely on it.
Frequently asked questions
Pro costs 19 USD per user and month with annual billing, 24 USD with monthly billing, with at least three users. Scale costs 39 USD annually or 49 USD monthly, and Enterprise starts at 49 USD annually, with the final price by quote. Status pages with subscribers come from Pro as an add-on by subscriber tier, inbound call routing for 10 USD per user a month. As of November 2026, according to ilert.com/pricing.
ilert stores customer data on AWS in Frankfurt and Stockholm. According to its subprocessor list, some providers process data in the US, mainly for AI features (OpenAI, Anthropic, xAI), and AWS is a US group. Uptimeify hosts in the EU at Hetzner, OVH, netcup, UpCloud and IONOS, SMS and calls go through seven.io with LOX24 in Germany, and email through Lettermint in the Netherlands. That means no US subprocessors for your incident data. The optional app push runs encrypted through Apple and Google, who do not read the content.
Usually, yes. ilert discontinued its uptime monitoring and now offers heartbeat monitoring only, an alert when expected signals stop arriving. On Uptimeify, monitoring and incident management run on the same platform: your checks report with no integration needed, and tools such as Zabbix, Datadog, Grafana, Prometheus, Sentry or Beszel report through presets, webhook, email or the events API.
Uptimeify has NIS2-ready exports. A report case groups the affected incidents, shows the 24-hour, 72-hour and one-month deadlines from the moment of awareness and prepares report drafts in German or English. The submitted version is frozen with the BSI reference, and you also get a quarterly management report as PDF plus audit log and incident reports as CSV. You file the report in the BSI portal yourself, Uptimeify submits nothing and never classifies an incident on its own. Whether and how NIS2 applies to you stays your assessment.
No. Uptimeify is a white-label monitoring platform with built-in incident management for your team. Client logins have no access to incident management. Your clients see their dashboard under your brand, the status page that status page rules keep up to date, and your reports.
Yes, with some manual work. There is no automatic import from ilert at the moment. You create teams, schedules, overrides, escalation tiers, routing rules and alert sources in the dashboard, via API or with the Uptimeify Terraform provider, and schedules and overrides are currently in beta. Then you point your monitoring tools to the Uptimeify presets, webhook or email address and test the chain with a dry run that wakes no one.
For the technical evaluator
From ilert to monitoring and incident management on one platform
Connect your checks and alert sources, set up your first team with escalation tiers and test the chain with a dry run. Your clients see your brand, your team owns the alerting chain.