Uptimeify vs. Grafana IRM (OnCall)
Grafana has merged OnCall and Incident into Grafana IRM in Grafana Cloud, and the open source Grafana OnCall OSS has been archived since 24 March 2026. If you already work in Grafana Cloud, IRM gives you a strong tool for on-call and incidents. SMS, calls and email there run through the US provider Twilio, though, and there is no status page of its own. Uptimeify brings incident management for your team with no US subprocessors for your incident data, with monitoring and a status page on the same platform.
For agencies, MSPs and IT teams
- No US subprocessors, hosted in the EU
- Monitoring, incident management and status page on one platform
- Status page follows the incident, automatically from Sev2
- Audit log with before and after, kept for twelve months
- NIS2-ready exports, you file the report
For teams on the Grafana stack
- Part of Grafana Cloud, next to Alerting and Synthetic Monitoring
- Slack and Teams workflow with incident roles
- No status page of its own, only a link to Atlassian Statuspage
- EU regions available, SMS, calls and email through Twilio (US)
- Pro from $20 per active user and month
As of November 2026. Details on Grafana IRM are based on publicly available information and may change. Prices in the source's original currency, not converted. On-call scheduling, acknowledgement and incident timeline are currently in beta on Uptimeify. If something is wrong, we are glad to hear about it.
In short
Grafana IRM is built for teams that observe their systems with Grafana. Alerts from Grafana Alerting go straight to on-call, Synthetic Monitoring runs on the same platform, and you work the incident in Slack or Teams with clear roles.
Once your client asks who processes their incident data, the answer gets longer. Grafana Cloud also runs in EU regions, but on AWS, Google Cloud and Azure, and SMS, calls and email go through Twilio, located in the US. A status page for your clients is something you add on top, for example Atlassian Statuspage.
Uptimeify starts right there: monitoring, incident management for your team and the status page under your brand on one platform, run by European providers. If you use Grafana Alerting today, you forward the alerts by webhook and keep your dashboards.
Feature by feature
As of November 2026. Details on Grafana IRM are based on publicly available information and may change. On-call scheduling, acknowledgement and incident timeline are currently in beta on Uptimeify. All trademarks belong to their respective owners.
Where Uptimeify leads
Three things Grafana IRM solves differently, and that we built for your team.
No US subprocessors for your incident data. Grafana Cloud offers EU regions, but runs them on AWS, Google Cloud and Azure, US corporations subject to the US CLOUD Act. SMS, calls and email go through Twilio. Uptimeify has no US subprocessors for your incident data: hosting with Hetzner, OVH, netcup, UpCloud and IONOS, SMS and calls through German providers, email through Lettermint in the Netherlands. The optional app push runs through Apple and Google, encrypted, so neither can read the content.
The status page comes with it. Grafana IRM has no status page of its own and uses an integration to create an incident on Atlassian Statuspage, a third-party product. On Uptimeify, status page rules set the page per team and severity, automatically from Sev2, and reset it when the incident is resolved. Your clients see the status page under your brand, while incident management stays internal to your team.
An audit log without caveats. Grafana keeps configuration changes in IRM insight logs for 30 days, but according to its docs not for every stack. Uptimeify logs every change to teams, schedules, escalation tiers, sources and routing with before and after, keeps entries for twelve months and exports the organization log as CSV, so auditors and clients get clean evidence.
Where Grafana IRM wins
No tool wins everywhere. Three points where Grafana IRM is the better choice.
At home on the Grafana stack. IRM runs in Grafana Cloud next to Grafana Alerting and Synthetic Monitoring. If your team already maintains dashboards and alerts there, the path from alert to on-call schedule is short.
Slack and Teams as the workplace. With Grafana IRM, you acknowledge, resolve and escalate alerts right in Slack or Microsoft Teams and declare incidents there, with roles such as commander and investigator visible. Uptimeify sends incidents to Slack and Microsoft Teams, but you can
An entry point for small teams. For up to three active IRM users a month, the Grafana Cloud entry plan is enough, without IRM costing anything. After that, Grafana bills by usage per active user.
Frequently asked questions
On 21 April 2025, Grafana replaced the OnCall and Incident cloud apps with the unified Grafana IRM app in Grafana Cloud. The open source Grafana OnCall OSS went into maintenance mode on 11 March 2025 and was archived on 24 March 2026. Existing installations keep running, but according to Grafana, the Cloud Connection that OnCall OSS used for SMS, calls and push has stopped working since that date. If you self-host, you move to Grafana Cloud IRM or to another tool.
Grafana bills per active IRM user. Active means being in a schedule or escalation chain or working on alerts and incidents. The entry plan covers up to three active users a month. On Pro, each active user costs from $20 a month, plus a $19 monthly platform fee that covers three active users. Enterprise is on request, with an annual contract from $25,000.
Yes. You create an alert source in Uptimeify with the Grafana preset and add its URL in Grafana as a webhook contact point. Uptimeify reads alert name, severity, status and host from the standard payload and uses Grafana's fingerprint as the dedup key, so the same alert does not open several incidents. Your dashboards stay where they are.
By hand, in the dashboard, via API or with the Uptimeify Terraform provider. You recreate teams, schedules with rotations, overrides and escalation tiers, then connect your alert sources. The escalation dry run checks the chain without waking anyone. On-call scheduling is currently in beta on Uptimeify.
On Uptimeify, only European companies: hosting with Hetzner, OVH, netcup, UpCloud and IONOS, spread across several providers and locations in the EU, SMS and calls through seven.io with LOX24 as fallback, both in Germany, email through Lettermint in the Netherlands. That means no US subprocessors for your incident data. The optional app push runs through Apple and Google, encrypted, so neither can read the content. On Grafana Cloud you choose an EU region, but Twilio, located in the US, is on the subprocessor list for email and alerting.
Yes, with NIS2-ready exports. You file the report. Report cases track the deadlines of 24 hours, 72 hours and one month, prepare draft reports in German or English and freeze what you submitted with the BSI reference number. On top come a quarterly management report as PDF plus audit log and incident reports as CSV. Uptimeify does not classify any incident itself, and whether NIS2 applies to you remains your assessment.
For the technical evaluator
From Grafana OnCall to incident management hosted in the EU
Create your first team, connect Grafana Alerting as a source and test the escalation chain in a dry run. Monitoring, on-call and status page run on one platform, under one data processing agreement.