Grafana IRM
Rest of world Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Raintank Inc. (Grafana Labs) · grafana.com
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.
Grafana IRM at a glance
- Vendor
- Raintank Inc. (Grafana Labs)
- Headquarters
- Incorporated in the United States source, captured 6 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 6 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 6 Nov 2026
- Panel verdict
- The AI panel rates Grafana IRM 3/5, the mean of 6 judges. Grafana IRM is the on-call and incident-response add-on to Grafana Cloud from Raintank Inc., d/b/a Grafana Labs of New York. 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
Grafana IRM is the on-call and incident-response add-on to Grafana Cloud from Raintank Inc., d/b/a Grafana Labs of New York. Strongest is on-call scheduling: layered time-zone-aware rotations, escalation chains with wait steps, Terraform-managed schedules and a 0-100 quality score documented. Reliability and compliance scored 7 on a published 99.5% availability SLA, ISO 27001 and SOC 2 Type 2 audits through A-LIGN, and a public status page. Sovereignty is the outlier at 3: a US contracting entity, a privacy policy stating information may be transferred to, stored and processed in the United States and other countries, hosting for IRM data not confirmed on the captured pages, and only payment and analytics subprocessors named, though a GDPR data processing agreement and EU-US Data Privacy Framework participation are documented. Alerting and routing and integration and administration scored 5-6, incident response 6, pricing transparency 6-7 — the pricing low end computable at "Starts at $20 / active IRM user", with no public information on SMS, voice and VAT costs. The judges did not meaningfully split: no criterion spans more than one point.
Speaks for it
- On-call scheduling scored 7-8, covering layered time-zone-aware rotations, escalation chains with wait steps and repeats, shift swaps from Slack or the mobile app, and schedules managed as code with Terraform and the API.
- A 0-100 schedule-quality score flags coverage gaps, empty shifts and teammates carrying too much of the load.
- A published SLA commits to 99.5% of requests succeeding per monthly billing period, with credits rising to 100% of monthly revenue.
- ISO 27001 and SOC 2 Type 2 are certified through A-LIGN, alongside FedRAMP compliance, independent penetration testing and a public status page with incident history.
- The low end of pricing is computable: always free to 3 active IRM users a month, a platform fee of $19 per month including 3 active users, then "Starts at $20 / active IRM user", with stakeholders who only follow along not billed and Enterprise from a $25,000 per year minimum commit.
Held against it
- Sovereignty scored 3: the contracting entity is Raintank Inc. of New York, the privacy policy states information may be transferred to, stored and processed in the United States and other countries, and hosting for IRM data is not confirmed on the captured pages.
- Only the payment processor and website-analytics providers are named as subprocessors, with no public information on the SMS, voice, push and AI providers in the notification chain.
- We found no public information on SAML or OIDC single sign-on, SCIM provisioning, audit logs or granular team roles — sign-on is documented only as GitHub and Google login.
- We found no public information on SMS and voice notification volumes, per-country overage prices or VAT treatment, so a paging-heavy annual total is not computable.
- We found no public information on exporting on-call hours per person for payroll and working-time rules, on delivery receipts, or on the countries SMS and voice reach.
Best for
- You run time-zone-spanning on-call rotations and want schedules managed as code with Terraform, with coverage gaps and burnout flagged by a 0-100 quality score.
- You already alert from Prometheus, Alertmanager, Datadog or ServiceNow and want paging, incident response and auto-converted post-incident reviews with MTTA, MTTR and MTTD reporting in one platform.
- You want a self-serve start: always free to 3 active IRM users a month, then per-active-user billing that does not charge stakeholders who only follow along.
Avoid if
- You must warrant where responders' phone numbers and shift data are hosted — ask the vendor: the public pages we read do not show it
- Your access policy requires SAML or OIDC single sign-on with SCIM provisioning and audit logs before rollout — the captured pages document only GitHub and Google login.
- You must budget the full paging bill before committing — ask the vendor: the public pages we read do not show it
The scores
| Criterion | Panel median |
|---|---|
| On-call schedules, rotations & escalation | 4 of 5 |
| Alert delivery, routing & noise reduction | 3 of 5 |
| Incident response, status pages & post-incident review | 3 of 5 |
| Integrations, API & administration | 3 of 5 |
| Platform reliability, security & compliance | 3.5 of 5 |
| European sovereignty | 1.5 of 5 |
| Pricing transparency | 3 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
On-call schedules come with rotations, layers, time zones and overrides, shift swaps picked up from Slack or the mobile app, and Google Calendar out-of-office events that become swap requests. Escalation chains support wait steps, round-robin, repeats and time-of-day conditions, schedules can be managed as code with Terraform and the API, and schedule-quality reports flag coverage gaps, empty shifts and teammates carrying too much load — most of what I need across eight teams. We found no public information on on-call hours exported per person for pay or working-time rules, which a Berlin payroll will ask me for. 1 3
The IT Operations Manager
Rotations, shift layers, time zones, overrides and Slack/mobile shift swaps are documented, escalation chains combine several notify-schedule steps with wait steps plus round-robin, time-of-day conditions and repeats, and schedules run as code via Terraform and the API with quality reports flagging gaps and burnout — my weekly standby and a delayed deputy step are fully covered. We found no public information on exporting on-call hours per person for pay and working-time rules, rest-period rules, or HR schedule imports. 1 2 3
The MSP NOC Lead
The schedules documentation covers rotation layers, overrides, shift swaps picked up from Slack or the mobile app, time-zone-aware rotations, and escalation chains with wait steps, round-robin, repeats and time-of-day conditions — enough to run a separate night rota per key account. Schedules as code through Terraform and the API, iCal import with priority levels for overlapping shifts, and a schedule quality score out of 100 with reports that flag gaps, empty shifts and teammates carrying too much of the load are all described. We found no public information on exporting on-call hours per person for pay and working-time rules. 1 2 3
The ICT Risk Officer
Rotations with multiple layers, time-zone awareness and real-time coverage preview are documented, escalation chains support wait steps, round-robin, time-of-day conditions and repeats, and schedules are managed as code with Terraform and the API, with quality reports flagging gaps, empty shifts and teammates carrying too much of the load. I found no public information on exporting on-call hours per person for pay or working-time rules, which is what I would need for our working-time compliance. 1 3
The Engineering Manager
The documentation covers layered, time-zone-aware rotations with shift swaps from Slack or the mobile app, round-robin escalation chains with wait steps, repeats and time-of-day conditions, real-time coverage previews with quality scores that flag gaps, unbalanced workload and burnout, and schedules managed as code with Terraform and the API — enough to build the three-time-zone rota I need. I found no public information on on-call hours exported per person for payroll and working-time rules, which our works council's paid-standby and rest-period policy makes essential. 1 2 3
The Skeptic
Multi-step escalation chains with wait steps, round-robin, repeats and time-of-day conditions, schedules as Terraform or API code, iCal import, mobile shift swaps and Google Calendar out-of-office auto-swaps, and a 0-100 schedule-quality score flagging coverage gaps, empty shifts and teammates carrying too much of the load are all documented. We found no public information on exporting on-call hours per person for pay or working-time rules, or on rest-period enforcement — the gap a European employer cannot ignore. 1 3 2
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
Notifications go out by mobile app, Slack, Microsoft Teams, Telegram, SMS, phone and email, alerts can be acknowledged, escalated and resolved from the app, and related alerts are grouped, auto-resolved and routed by label or template to the owning team — the grouping one database outage demands. The vendor's own public status page shows SMS, mobile push and voice calls actually operating in production. We found no public information on critical alerts overriding do-not-disturb, personal notification rules with retries and fallbacks, delivery receipts, suppression or maintenance windows, or the countries where SMS and voice are delivered. 1 2 4 8
The IT Operations Manager
Notifications by mobile app, Slack, Teams, Telegram, SMS, phone and email are documented, voice delivery is confirmed by the status page working a Brazil voice outage, and alert grouping, auto-resolve and routing by label or template are described. We found no public information on keypad acknowledgement during a voice call, do-not-disturb override, delivery receipts, customer-side maintenance or suppression windows, heartbeat monitoring, or the countries SMS and voice reach. 1 2 8
The MSP NOC Lead
Notifications go out by mobile app, Slack, Microsoft Teams, Telegram, SMS, phone and email, with acknowledge, escalate and resolve from the app, grouping of related alerts with auto-resolve, and routing by label or template to the team that owns the problem. A status-page incident about voice calls to Brazil shows voice delivery is country-dependent and real. We found no public information on personal notification rules with retries and fallbacks, on suppression and maintenance windows, on heartbeats for silent failures, or on delivery receipts. 1 2 4 8
The ICT Risk Officer
Notifications are documented across mobile push, SMS, phone, email, Telegram, Slack and Microsoft Teams, with acknowledgement and escalation from the app, and alerts are grouped, auto-resolved and routed by label or template into user-defined escalation chains. Personal notification rules with retries, delivery receipts, suppression and maintenance windows, heartbeat monitoring, and the countries where SMS and voice are delivered are not described on the captured pages, so I cannot verify delivery assurance for a regulator. 1 2 4 8
The Engineering Manager
Every channel my teams rely on is documented — mobile app, Slack, Microsoft Teams, Telegram, SMS, phone and email — with acknowledge, escalate and resolve from the phone and grouping plus routing by label or template to the owning team. I found no public information on personal notification rules with retries, maintenance windows or suppression rules, delivery receipts, or which countries SMS and voice reach, so the evidence sits in the middle of the scale rather than high. 1 2 4 8
The Skeptic
Notifications go out by mobile push, SMS, phone, email and Telegram alongside Slack and Teams, with acknowledge, escalate and resolve from the phone, alert grouping and routing by label or template. We found no public information on delivery receipts, do-not-disturb override for critical alerts, maintenance windows, suppression, heartbeats, or the countries and carriers that deliver the SMS and voice — though the vendor's own status page incident on voice calls to Brazil at least proves voice is a real path. 1 2 8
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 can be declared from Slack, Microsoft Teams, a dashboard panel or the phone, with roles assigned, a dedicated channel, a timeline and stakeholder updates — and the timeline converts automatically into a structured post-incident review whose status is tracked, which is the auto-drafted postmortem I want. MTTA, MTTR and MTTD are reported by team, severity and label, AI investigations launch when an alert fires or an incident is declared, and Jira, ServiceNow and GitHub integrate for workflows and issue-status sync. We found no public information on a customer-facing status page updated from the incident itself, or on runbooks. 1 2 4
The IT Operations Manager
Incidents are declared from a dashboard panel, Explore or the phone, roles assigned and coordination run from Slack, Teams or the phone, with timelines auto-converted into structured post-incident reviews, review-status tracking, MTTA/MTTR/MTTD reporting by team and severity, and AI investigations producing structured reports on likely causes. We found no public information on runbooks, automated response workflows, incident types with their own process, or a status page the buyer can offer its own users, and the captured pages do not describe how the AI features handle data. 1 2 4
The MSP NOC Lead
Incidents can be declared from a dashboard panel, in Explore, from Slack, Microsoft Teams or the phone, with roles assigned, a timeline, and automatic conversion of that timeline into a structured post-incident review whose status is tracked; MTTA, MTTR and MTTD trends break down by team, severity and label, which is close to the per-customer response report I owe monthly. AI investigations and root-cause exploration start when an alert fires and return an investigation summary with a link to the full report, and Jira or GitHub can track incidents and sync issue status. We found no public information on runbooks or automated response workflows, or on status pages my customers could subscribe to. 1 2 4
The ICT Risk Officer
Incidents can be declared from a dashboard panel, in Explore, from chat or from the phone, with roles, severities, a timeline, dedicated channels, stakeholder updates, automatic post-incident review with status tracking, MTTA/MTTR/MTTD trends, and AI investigations that test hypotheses and produce a summary report. Runbooks and task workflows and a customer-facing status page are not described, and where the AI summaries of the response channel are processed and by which model is not stated — for a DORA register entry that is the open question I would put to the vendor. 1 2 4
The Engineering Manager
Declaration from any dashboard or the phone, incident roles, dedicated Slack or Teams channels for coordination, timelines auto-converted into structured post-incident reviews with status tracking, and MTTA, MTTR and MTTD broken down by team, severity and label are all documented, alongside AI investigations that test hypotheses across metrics, logs and traces. I found no public information on a public status page for our customers, or on runbooks, incident types with their own process, and follow-up actions tracked into a tracker. 1 2 4 5
The Skeptic
Declaring from a dashboard, Explore, Slack, Teams or the phone, assigning roles, dedicated channels, timelines auto-converted into structured post-incident reviews with tracked review status, MTTA/MTTR/MTTD by team and severity, and AI root-cause investigations that explore metrics, logs and traces are documented. We found no public information on public or internal status pages for a customer's own incidents, on runbooks, or on how the AI features handle data — the terms only disclaim that chatbot outputs may contain errors. 1 2 4 10
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
Integrations cover twenty-plus alert sources including Alertmanager, Datadog, ServiceNow and webhooks, with native Prometheus and OpenTelemetry support, Slack, Microsoft Teams, Zoom, Jira and GitHub, and incoming and outgoing webhooks for the rest — a good fit for a Prometheus-and-Grafana shop. Schedules are managed as code with Terraform and the API, and multi-factor authentication is stated. We found no public information on single sign-on via SAML or OIDC, SCIM provisioning, audit logs, or teams with granular roles, which I would need for sixty engineers. 1 3 4 6 9
The IT Operations Manager
Twenty-plus alert-source integrations are claimed with Alertmanager, Datadog, ServiceNow and webhooks named, plus Slack, Teams, Zoom, Jira and GitHub, incoming and outgoing webhooks, iCal import, Terraform and API management of schedules, and MFA/2FA on the trust page. Neither Checkmk nor PRTG appears among the named integrations, and we found no public information on SAML or OIDC single sign-on, SCIM provisioning, granular per-team roles, audit logs, or migration help from another on-call tool. 1 3 4 6
The MSP NOC Lead
Twenty-plus integrations are claimed, with Alertmanager, Datadog and ServiceNow named for alert sources; Jira, GitHub, Slack, Microsoft Teams and Zoom for coordination and task tracking; plus incoming and outgoing webhooks, Terraform and API management of schedules, and Git Sync for configuration. Multi-factor authentication, GitHub or Google login and audited secure development are described. We found no public information naming connectors for Zabbix, Checkmk, PRTG, Azure Monitor or Autotask, and we found no public information on SAML or OIDC single sign-on with SCIM, on audit logs, or on multi-tenant separation between my sixty customers — as a service provider that decides the score. 1 3 4 6 9 12
The ICT Risk Officer
Twenty-plus integrations are named including Alertmanager, Datadog, ServiceNow, Jira and GitHub with incident and issue-status sync, incoming and outgoing webhooks, native Prometheus and OpenTelemetry, and schedules managed as code with Terraform and the API; two-factor authentication and GitHub or Google login are stated. Single sign-on with SAML or SCIM provisioning, audit logs, granular per-team roles and migration help from other on-call tools are not described on the captured pages, and audit logs are non-negotiable for my contract review. 1 3 4 6 9 12
The Engineering Manager
Twenty-plus alert-source integrations including Alertmanager, Datadog and ServiceNow, incident-status sync with Jira and GitHub, incoming and outgoing webhooks, Terraform-managed schedules with CI/CD, and multi-factor authentication are documented. I found no public information on the documented REST API's coverage, single sign-on, team roles and permissions, SCIM provisioning, audit logs, or a migration path from another on-call tool. 1 3 4 6
The Skeptic
Twenty-plus alert integrations including Alertmanager, Datadog and ServiceNow, Slack, Teams and Zoom for coordination, Jira and GitHub with incident tracking and issue-status sync, incoming and outgoing webhooks, Terraform for schedules, two-factor authentication and iCal import are documented. Sign-on appears only as GitHub and Google social login, and we found no public information on SAML or OIDC single sign-on, SCIM provisioning, audit logs or granular team roles and permissions. 1 4 3 6 12
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
The service level agreement publishes 99.5% availability with credit tiers rising to 100% of a month's fees, and a public status page with incident history, component detail for the IRM service itself and email subscription shows the operation running, including a real outage of voice calls to Brazil. Regions are named across GCP and AWS including Germany and EU-west locations, and ISO 27001, SOC 2 Type 2, FedRAMP, PCI DSS, penetration tests and a trust portal are stated. We found no public information on named redundant SMS or voice carriers, tested failover, or guidance for DORA or NIS2 customers. 6 7 8
The IT Operations Manager
A published SLA of 99.5% of requests per month carries a credit ladder rising to 100% of monthly revenue, the public status page shows incident history and component-level states for IRM itself, hosting spans named regions including AWS Germany and two EU-west zones, and ISO 27001 and SOC 2 Type 2 are certified through A-LIGN with a trust portal, penetration testing and FedRAMP stated — and the pager runs in the vendor's cloud, outside my plant network. We found no public information on redundant SMS or voice carriers with automatic failover, certification scope, or DORA and NIS2 documentation. 6 7 8
The MSP NOC Lead
A published service level agreement commits to 99.5% of requests succeeding within a monthly billing period with tiered credits up to 100% of the affected services' monthly revenue, and the public status page lists Incident Management and Response among its components, carries an incident history, and offers email or RSS subscription — I can watch my own pager's pager. ISO 27001 and SOC 2 Type 2 certified through A-LIGN, FedRAMP compliance, independent penetration testing and a trust portal are stated, and hosting regions including AWS Germany and EU-west locations appear in incident notices. We found no public information on redundant notification carriers with failover or on a DORA or NIS2 mapping. 1 6 7 8
The ICT Risk Officer
A 99.5% availability commitment is published with credit tiers up to 100% of monthly revenue, the status page is public with incident history and lists IRM as a monitored component, hosting spans named regions across the US, Australia and Europe, and ISO 27001 and SOC 2 Type 2 are certified through A-LIGN with a trust portal for reports. I found no public information on a DORA or NIS2 addendum or mapping, the notification carriers are unnamed, and the certification scope itself is not published — for a BaFin-supervised payment institution that gap has to be closed in contract before I register the service. 1 6 7 8
The Engineering Manager
There is a public status page with visible incident history including an IRM voice-call outage to Brazil, a published 99.5% availability commitment with a credit ladder rising to 100% of monthly revenue, ISO 27001 and SOC 2 Type 2 certified through A-LIGN, third-party penetration testing, a trust portal, and data retention and deletion described. I found no public information on redundant notification carriers, tested failover, or a DORA/NIS2 addendum, and scheduled maintenance can leave an instance unavailable for 5 to 15 minutes. 1 6 7 8 12
The Skeptic
The published service level agreement pays tiered credits — 10% below 99.5% availability rising to 100% below 97%, claimed within ten days or forfeited and capped at a month's revenue — and there is a public status page with incident history, regions named across GCP and AWS including Germany, ISO 27001 and SOC 2 Type 2 audited through A-LIGN, FedRAMP, and a trust portal. We found no public information on redundant notification carriers, on certification scope, or on a DORA or NIS2 mapping. 7 8 6 1
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
The contracting entity is Raintank Inc., d/b/a Grafana Labs at 165 Broadway, New York, and the privacy policy states personal information may be transferred to, stored and processed in the United States and other countries. A GDPR data processing agreement is published and some marketing and payment subprocessors are named. We found no public information on where alert, incident and phone-number data is hosted, or on the carriers and services in the notification chain. 6 10 12
The IT Operations Manager
The contracting entity is Raintank Inc. of New York, personal information is stated to be transferred to and stored in the United States and other countries, residency for IRM data is not confirmed on the vendor's own pages, and the product chain — hosting, SMS and voice carriers, push services — is not listed, with only website analytics tools and the payment processor named. A GDPR data processing agreement is available, EU-US Data Privacy Framework participation is stated, and ISO 27001/SOC 2 appear on the trust page, which is more than nothing, but my responders' phone numbers and shift data would sit under a US entity with the residency question open. 6 10 12
The MSP NOC Lead
The contracting entity is Raintank Inc., d/b/a Grafana Labs at 165 Broadway, New York, and the privacy policy states information may be transferred to, stored and processed in the United States and other countries. A GDPR data processing agreement and participation in the EU-US Data Privacy Framework are stated, and analytics tools plus the payment processor are named as subprocessors. We found no public information on where IRM alert, timeline and on-call data is hosted or on the SMS and voice carriers in the chain — with sixty German customers whose data residency I must answer for, that keeps the score low. 12 10 6 8
The ICT Risk Officer
The contracting entity is Raintank Inc. in New York and the privacy policy confirms information is transferred to, stored and processed in the United States and other countries, with the EU-US Data Privacy Framework as the stated safeguard and a GDPR data processing agreement available. Regions in Germany and EU-West appear on the status page, but where incident timelines, chat transcripts and the AI summaries are stored is not confirmed, and no subprocessor list covers hosting, SMS and voice carriers or the AI models — only website analytics tools and the payment processor are named. 6 8 10 12
The Engineering Manager
The contracting entity is Raintank Inc. in New York, the privacy policy states information may be transferred to, stored and processed in the United States and other countries, and a GDPR data processing agreement plus Data Privacy Framework participation are documented. Only marketing-analytics and payment subprocessors are named; I found no public information on where IRM data is hosted or who the hosting, SMS, voice and AI providers are, though European regions such as AWS Germany do appear in the incident history. 6 8 10 12
The Skeptic
The contracting entity is Raintank Inc., d/b/a Grafana Labs of 165 Broadway, New York, and the privacy policy states information may be transferred to, stored and processed in the United States and other countries. A GDPR data processing agreement and EU-US Data Privacy Framework participation are documented, but hosting location for the on-call schedules, timelines and contact data is not confirmed on the captured pages, no EU entity or representative is named, and the SMS, voice, push and AI subprocessors are not listed — only the payment processor NMI and website analytics providers are. 12 6 10 8
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
Pricing is unusually clear on who pays: you are only billed for people who are on call, get notified, or take action that month — not for stakeholders who only follow along — with Pro at '$20 / active IRM user', a '$19 per month' platform fee including three active users, an interactive calculator, automatic volume discounts, and the enterprise tier public as a '$25,000 / year' minimum commit with fees payable in United States Dollars. We found no public information on SMS and voice notification volumes or overage prices per country, VAT treatment, or the enterprise price beyond that minimum. 1 5 11
The IT Operations Manager
The model is unusually clear: 3 active IRM users per month free, "Starts at $20 / active IRM user", a platform fee of $19 per month including 3 active IRM users, stakeholders who only follow along free, USD billing, an interactive calculator, and a $25,000 per year minimum commit for the enterprise tier. What I cannot compute for a 24/7 plant is the paging itself — SMS and voice notification volumes, overage prices and per-country costs are not published, and VAT treatment is not stated. 1 5 11
The MSP NOC Lead
The IRM add-on is priced publicly at 'Starts at $20 / active IRM user', with a 'Platform fee of $19 per month' that includes three active IRM users and 8×5 email support, a free tier limited to three active IRM users, stakeholders who only follow along explicitly free, and Enterprise stated as custom pricing with a 'Minimum commit of $25,000 per year', an interactive calculator and automatic volume discounts. We found no public information on included SMS or voice notification volumes or their cost per country, or on VAT treatment, so I cannot compute the full annual paging cost from public pages alone. 1 5 11
The ICT Risk Officer
The add-on is priced publicly at $20 per active IRM user, stakeholders who only follow along are free, the Pro platform fee of $19 per month includes three active IRM users, the free tier allows three, and Enterprise starts at a $25,000 annual spend commit with custom unit pricing, billed in US States Dollars with an interactive calculator and automatic volume discounts. SMS and voice notification volumes and per-message costs and the VAT treatment are not stated on the captured pages, so the real annual total for a regulated buyer is not fully computable. 1 5 11
The Engineering Manager
The billing model fits us precisely — only people who are on call, get notified or take action that month are billed, "not for stakeholders who only follow along" — with a free tier of 3 active IRM users, a $19 per month platform fee covering 3 active users, then "Starts at $20 / active IRM user", Enterprise custom from a $25,000 per year minimum commit, an interactive calculator, and fees stated in United States Dollars. I found no public information on included SMS and voice volumes and their overage prices or VAT treatment, and the enterprise price itself is custom. 1 5 11
The Skeptic
The low end is fully computable: always free with up to 3 active IRM users a month, then a platform fee of $19 per month including 3 active users and $20 per active IRM user, with stakeholders who only follow along never billed, Enterprise starting at a $25,000 per year spend commit, fees stated in United States Dollars, automatic volume discounts and an interactive calculator. We found no public information on SMS and voice notification volumes, their overage prices per country, or VAT treatment — and the Enterprise rate above the minimum commit is custom. 1 5 11 2
European sovereignty — proven facts
2 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 US
unverified
Why unverified?The page gives a US street address for Raintank Inc., d/b/a Grafana Labs but names no register or state of incorporation. |
0/2 pts | 12 Report an error |
|---|---|---|---|
| Hosting location |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Hosting options |
Self-hostable
unverified
Why unverified?The "Cloud or self-hosted" line appears under Grafana Visualization on the pricing page, while IRM itself is described as a paid Grafana Cloud add-on (Enterprise offering "Deployment flexibility (Public Cloud, Federal Cloud, or Bring Your Own Cloud)"). |
1/1 pts | 5 Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Grafana IRM
Is Grafana IRM European?
No. whats-best.ai classifies Grafana IRM as Rest of world. Its vendor, Raintank Inc. (Grafana Labs), is incorporated in the United States, per the vendor’s page captured 6 Nov 2026.
Where does Grafana IRM store data?
Not stated on the vendor’s pages as of 6 Nov 2026.
Does Grafana IRM have a free plan?
Yes. Grafana IRM has a free plan, per the vendor’s page captured 6 Nov 2026.
What are the best alternatives to Grafana IRM?
As of 18 Nov 2026, the panel rates ilert (4/5), All Quiet (3.5/5) and OneUptime (3.5/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 ilert (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: Grafana IRM 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 — Data processing agreement, Hosting location. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Legal entity. The page gives a US street address for Raintank Inc., d/b/a Grafana Labs but names no register or state of incorporation.
- Weak sourcing — Hosting options. The "Cloud or self-hosted" line appears under Grafana Visualization on the pricing page, while IRM itself is described as a paid Grafana Cloud add-on (Enterprise offering "Deployment flexibility (Public Cloud, Federal Cloud, or Bring Your Own Cloud)").
- 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.
- 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
- 4 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
- 3 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
- 1 compliance 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 data 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
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
- We read 12 of the 24 pages we planned to read for this product; the others could not be captured yet. Everything on this page rests on the pages we read. 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 (12)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage (product page) grafana.com Checked 6 Nov 2026 Details →
- 2 Documentation grafana.com Checked 6 Nov 2026 Details →
- 3 Documentation (on-call schedules) grafana.com Checked 6 Nov 2026 Details →
- 4 Documentation (integrations) grafana.com Checked 6 Nov 2026 Details →
- 5 Pricing page grafana.com Checked 6 Nov 2026 Details →
- 6 Security / trust page grafana.com Checked 6 Nov 2026 Details →
- 7 Service level agreement grafana.com Checked 6 Nov 2026 Details →
- 8 Public status page status.grafana.com Checked 6 Nov 2026 Details →
- 9 About page grafana.com Checked 6 Nov 2026 Details →
- 10 Terms of service grafana.com Checked 6 Nov 2026 Details →
- 11 Terms of service (master services agreement) grafana.com Checked 6 Nov 2026 Details →
- 12 Privacy policy (names the operating company) grafana.com Checked 6 Nov 2026 Details →