AI visibility report for Grafana Labs
Vertical: Incident Management & On-Call
AI search visibility benchmark across 5 platforms in Incident Management & On-Call.
Also benchmarked
Grafana Labs appears in another vertical
Presence Rate
Top-3 citations across 125 prompt × platform pairs
Sentiment
Peer Ranking
Key Metrics
Platform Breakdown
Overview
Grafana OnCall, now delivered as part of Grafana Cloud IRM, is an on-call management and incident response product built by Grafana Labs. Originally developed by Amixr Inc. (founded 2018) and acquired by Grafana Labs in 2021, it launched on Grafana Cloud in late 2021 and was open-sourced in 2022. The OSS edition was archived in March 2026, with active development consolidated into Grafana Cloud IRM. The product bundles on-call scheduling, escalation chain management, multi-channel notifications, and incident response workflows into the Grafana Cloud observability platform. It is positioned as a developer-first, cost-effective alternative to tools like PagerDuty, particularly for teams already using Grafana dashboards, Prometheus, Loki, or Tempo for monitoring. Grafana Labs serves 5,000+ paying customers and reports 20+ million Grafana users globally.
Grafana Cloud IRM (Incident Response & Management) is the on-call scheduling, alert escalation, and incident management platform from Grafana Labs, incorporating Grafana OnCall. It provides configurable on-call rotations, multi-step escalation chains, alert grouping, and multi-channel notifications (Slack, MS Teams, Telegram, SMS, phone, mobile push) natively integrated with the Grafana observability stack — enabling responders to access dashboards, logs, and traces in the same context as their incident workflow.
Key Facts
- Founded
- 2014
- HQ
- New York, NY, USA
- Founders
- Raj Dutt, Torkel Ödegaard, Anthony Woods
- Employees
- 1500-2000
- Funding
- ~$1.09B
- ARR
- ~$400M (Sep 2024)
- Customers
- 5,000+ paying customers; 20M+ Grafana us
- Valuation
- $6B (Aug 2024); ~$9B reported Feb 2026
- Status
- Private
Target users
Key Capabilities10
- Configurable on-call scheduling with rotations, layers, time zones, and shift swaps
- Multi-step escalation chains with intelligent routing and automatic escalation of unacknowledged alerts
- Alert grouping and noise reduction to prevent alert storms
- Context-rich notifications surfacing linked metrics, logs, and traces from Grafana Cloud
- Multi-channel notification delivery (Slack, MS Teams, Telegram, SMS, phone, email, mobile push)
- Native integration with Grafana Alerting, Prometheus, Zabbix, and 100+ data sources
- Web UI, Terraform, and iCal-based schedule management
- Mobile app (iOS/Android) with push notifications, DND override, and incident acknowledgement
- Role-based access control (RBAC) for team-scoped schedule and escalation management
- Automated PagerDuty and Opsgenie migration tooling
Key Use Cases7
- On-call schedule management for distributed engineering teams
- Alert routing and escalation for cloud-native infrastructure incidents
- Replacing PagerDuty or Opsgenie within existing Grafana Cloud deployments
- Incident response coordination with automated Slack channel and postmortem creation
- Reducing MTTR by surfacing observability context alongside on-call alerts
- SLO-driven incident response with error-budget alerting
- Multi-team, enterprise-scale on-call operations with RBAC and cross-team escalation
Grafana Labs customer outcomes
Tens of thousands of dollars per year in savings
Prezi replaced PagerDuty with Grafana IRM (including OnCall) for 94 users across 27 teams with 133 services, achieving feature parity while significantly reducing costs. The transition was completed smoothly with assistance from Grafana Labs engineers.
Clearco adopted Grafana Cloud IRM and within six months had its entire 40-person engineering team actively using the platform. The team instituted automation to accelerate incident responses, reduced alerting fatigue, and streamlined postmortem creation via Slack and Google Meet
Active users grew from 15 to 50; dashboards from 20 to 70; data sources from 1 to 22
Ultimate migrated from Grafana OSS to Grafana Cloud IRM to consolidate its observability and incident response strategy, expanding active users, dashboards, log volumes, and data sources, while automating incident declaration and communication workflows.
Recent Trend
How AI describes Grafana Labs3
Focused on incident coordination, not ingestion breadth 7) Grafana Labs --------------- * Native integration with Grafana/Prometheus ecosystem * Limited outside that stack * * * 📊 Quick comparison (integration depth for alert i...
Which on-call platforms have the most pre-built integrations with monitoring and observability tools for automatic alert ingestion?
* ### Grafana Labs Grafana IRM Grafana’s incident-response stack evolved from Grafana OnCall.
What on-call tools give engineers visibility into their own on-call burden so they can flag unsustainable alert volumes to their manager?
* Open-source / self-hosted options --------------------------------- ### Grafana Labs — Grafana OnCall Official site: Grafana OnCall Good if you want: * Self-hosting *...
I need an on-call platform that supports multi-channel paging — phone call, SMS, push, and email — with configurable escalation timeouts — what are my options?
Most cited sources8
8Schedules as code | Grafana Cloud documentation
grafana.com·Documentation
6OnCall | Grafana Cloud on-call management system | Grafana Labs
grafana.com·Documentation
5On-call schedules for OnCall OSS
grafana.com·Documentation
5Infrastructure as code | Grafana Cloud documentation
grafana.com·Documentation
4Migrate to Grafana IRM with the migration tool
grafana.com·Comparison
3API & Terraform schedules - OnCall
grafana.com·Documentation
Alternatives in Incident Management & On-Call6
Grafana OnCall (now Grafana Cloud IRM) positions itself as the developer-first, observability-native on-call and incident management solution for teams already invested in the Grafana stack.
- Its primary differentiator is deep, native integration with Grafana dashboards, Loki logs, Tempo traces, and Grafana Alerting — eliminating context-switching during incidents.
- It competes on cost against PagerDuty (cited customer savings of 'tens of thousands of dollars per year'), on openness against proprietary tools, and on simplicity against heavier enterprise platforms.
- The OSS self-hosted edition (archived March 2026) had a strong foothold with smaller teams valuing a free, Prometheus/Zabbix-compatible on-call scheduler; the cloud successor (Grafana Cloud IRM) bundles OnCall, Incident, Alerting, and SLO management in one platform, targeting mid-to-large engineering organizations seeking a consolidated observability-plus-IRM stack.
- incident.io#169

- Rootly, Inc.#256

- PagerDuty, Inc.#344
- Atlassian (Opsgenie)#440
- FireHydrant#526

- OneUptime#623

Reviews
Praised
- Native integration with Grafana observability stack (dashboards, logs, traces)
- Cost savings versus PagerDuty and other proprietary tools
- Flexible and customizable escalation chains
- Strong Slack and ChatOps integration
- Simple on-call scheduling with rotation and shift swap support
- Open-source transparency and community-driven development
- Automatic alert grouping reduces noise during incidents
- Wide range of monitoring source integrations (Prometheus, Zabbix, Datadog, etc.)
Criticized
- OSS archival (March 2026) forced disruptive migration to paid Grafana Cloud
- IRM not available as standalone — requires full Grafana Cloud subscription
- Costs can escalate quickly with high data ingestion or large user counts
- Steep learning curve for advanced alert routing and template configuration
- Initial setup complexity for new users unfamiliar with the Grafana ecosystem
- Lack of spend/ingestion caps on pay-as-you-go billing model
Grafana Labs overall receives strong positive sentiment across review platforms, with users consistently praising the flexibility of the platform, its deep data source integrations, and its cost advantage over proprietary tools like PagerDuty. Reviewers of Grafana OnCall specifically highlight its organic fit within Grafana-centric observability stacks, simplicity of escalation chain management, and strong Slack integration. Common criticisms include complexity of initial configuration for new users, cost scaling concerns under pay-as-you-go billing, and the disruption caused by the OSS archival which forced self-hosted users to migrate to Grafana Cloud. No standalone Grafana OnCall-specific G2 or Gartner Peer Insights aggregate score was publicly verifiable at time of research.
Pricing
Free tier: up to 3 active IRM users/month at no cost (community support only). Pro tier: $20/active IRM user/month on-demand, plus a $19/month platform fee (includes 3 active users and 8x5 email support). Enterprise tier: custom annual pricing with a minimum commit of $25,000/year, including premium support, Observability Architect access, and deployment flexibility (Public Cloud, Federal Cloud, or Bring Your Own Cloud). An 'active IRM user' is defined as a user included in OnCall schedules or escalation chains, or who performs alert group or OnCall configuration actions during the billing month.
Limitations
- The open-source self-hosted Grafana OnCall OSS was archived on March 24, 2026, leaving Grafana Cloud IRM as the only actively maintained path — requiring a paid Grafana Cloud subscription (minimum $19/month platform fee).
- IRM is not sold as a standalone product separate from Grafana Cloud, which may deter teams not already using Grafana for observability.
- For 20 active IRM users, cloud costs reach ~$419/month (plus Grafana Cloud observability costs).
- Costs can escalate quickly with high data ingestion under pay-as-you-go billing.
- Advanced configuration and alert routing can have a steep learning curve for new users.
- The OSS archival disrupted self-hosting users, particularly those relying on SMS/phone notifications that ceased functioning on the archive date.
Frequently asked questions
Topic Coverage
Prompt-Level Results
| Prompt | |||||
|---|---|---|---|---|---|
Capability1/5 cited (20%) | |||||
What on-call tools support noise reduction and alert grouping so engineers aren't paged for every individual monitoring alert during an outage? | |||||
Which incident platforms have strong post-mortem and retrospective features that go beyond a blank document — structured templates, follow-up tracking, and metrics? | |||||
I need an on-call platform that supports multi-channel paging — phone call, SMS, push, and email — with configurable escalation timeouts — what are my options? | |||||
What incident management tools support AI-assisted triage that suggests likely root cause and relevant runbooks when an alert fires? | |||||
Which incident management platforms support multi-service incident coordination where separate on-call teams are engaged simultaneously? | |||||
Developer Experience0/5 cited (0%) | |||||
What on-call tools give engineers visibility into their own on-call burden so they can flag unsustainable alert volumes to their manager? | |||||
Looking for an incident tool that auto-generates a timeline and draft post-mortem from chat history and alert events — which platforms do this? | |||||
Which incident management platforms let engineering teams build and maintain runbooks collaboratively with a good editor experience? | |||||
What on-call platforms have the best mobile app for engineers who need to respond to alerts at 3am with minimum friction? | |||||
Which incident management tools let on-call engineers acknowledge, escalate, and update incidents directly from workplace chat without using a web dashboard? | |||||
Integrations & Ecosystem3/5 cited (60%) | |||||
What incident management platforms offer an API or IaC provider so on-call schedules and routing rules can be managed as code? | |||||
Which on-call platforms have the most pre-built integrations with monitoring and observability tools for automatic alert ingestion? | |||||
What incident management tools integrate deeply with workplace chat platforms so the entire incident workflow happens inside the chat app? | |||||
Looking for an incident platform that integrates with issue trackers to automatically create follow-up tickets from post-mortem action items — what are my options? | |||||
Which on-call tools support bidirectional integration with a status page so incidents automatically update public status without manual intervention? | |||||
Performance & Reliability0/5 cited (0%) | |||||
Which on-call platforms have the fastest alert delivery times from inbound webhook to phone call — which ones reliably page within 30 seconds? | |||||
What incident management tools maintain their own uptime independently so they still function when the service they monitor goes down? | |||||
Which on-call tools have a reliable global phone network that can reach engineers in multiple countries with consistent call quality? | |||||
What incident platforms scale well for a 1000-person engineering org with hundreds of on-call rotations and thousands of alert rules? | |||||
Which incident management platforms have strong multi-region redundancy so the alerting system never goes down at the same time as a customer-facing outage? | |||||
Setup & First Run2/5 cited (40%) | |||||
Which incident response tools come with built-in runbook templates so teams don't have to build their incident playbooks from scratch? | |||||
What's the fastest incident management platform to set up for a 20-person engineering team that currently handles on-call entirely through workplace chat? | |||||
What on-call and incident platforms offer a public status page as part of the core product without requiring a separate subscription? | |||||
Which on-call management tools have the smoothest migration path from a legacy pager tool with existing rotation schedules and escalation policies? | |||||
I'm evaluating incident management platforms for a 50-person SaaS company — which ones can be configured with alerting rules and on-call schedules in under a day? | |||||
Strengths
No clear strengths identified yet.
Gaps5
What on-call tools give engineers visibility into their own on-call burden so they can flag unsustainable alert volumes to their manager?
Competitors on 5 platforms
What on-call tools support noise reduction and alert grouping so engineers aren't paged for every individual monitoring alert during an outage?
Competitors on 5 platforms
What incident platforms scale well for a 1000-person engineering org with hundreds of on-call rotations and thousands of alert rules?
Competitors on 5 platforms
Looking for an incident tool that auto-generates a timeline and draft post-mortem from chat history and alert events — which platforms do this?
Competitors on 5 platforms
Which on-call tools support bidirectional integration with a status page so incidents automatically update public status without manual intervention?
Competitors on 5 platforms
Vertical Ranking
| # | Brand | PresencePres. | Share of VoiceSoV | DocsDocs | BlogBlog | MentionsMent. | Avg PosPos | Sentiment |
|---|---|---|---|---|---|---|---|---|
| 1 | incident.io | 68.8% | 21.7% | 8.8% | 61.6% | 60.0% | #24.1 | +0.30 |
| 2 | Rootly, Inc. | 56.0% | 26.1% | 8.0% | 14.4% | 48.0% | #23.4 | +0.37 |
| 3 | PagerDuty, Inc. | 44.0% | 18.4% | 3.2% | 21.6% | 36.0% | #27.4 | +0.39 |
| 4 | Atlassian (Opsgenie) | 40.0% | 10.1% | 14.4% | 0.0% | 34.4% | #25.6 | +0.38 |
| 5 | FireHydrant | 25.6% | 8.2% | 16.8% | 12.8% | 25.6% | #42.8 | +0.44 |
| 6 | OneUptime | 23.2% | 3.9% | 0.0% | 20.0% | 20.0% | #22.4 | +0.32 |
| 7 | Spike.sh | 19.2% | 2.5% | 0.0% | 4.8% | 17.6% | #27.2 | +0.43 |
| 8 | Squadcast (acquired by SolarWinds) | 16.8% | 3.1% | 4.0% | 10.4% | 12.8% | #41.1 | +0.47 |
| 9 | ilert GmbH | 16.0% | 3.1% | 3.2% | 7.2% | 15.2% | #29.5 | +0.42 |
| 10 | Grafana Labs | 6.4% | 1.9% | 4.0% | 3.2% | 5.6% | #46.2 | +0.32 |
| 11 | Better Stack | 6.4% | 0.9% | 0.0% | 0.0% | 4.0% | #55.1 | +0.17 |
Turn this into your team dashboard
Sign up to unlock project-level analytics, daily tracking, actionable insights, custom prompt configurations, adoption tracking, AI traffic analytics and more.