AI visibility report
Rootly ranks #2 in Incident Management & On-Call AI search.
Outside the top three on 7 of the 25 prompts buyers actually ask.
incident.io is cited on 6 of those losses.
Free trial. Setup comes pre-filled for Rootly.
Track Rootly across these prompts daily.
Start free trial#2 among 11 vendors · still absent from 74% of tracked prompt responses
Top-3 citations across 150 prompt × platform pairs
Peer Ranking
Key Metrics
Platform Breakdown
Google AI Mode
Gemini Search
Bing Copilot
Perplexity
ChatGPT
GrokVisible, but narrative can improve. Rootly ranks #2 on presence but #4 on sentiment. The brand appears relatively often, but competitors may be getting more favorable language when they appear.
Where Rootly is losing
Prompts where competitors are visible and Rootly is not.
These prompt-level losses are the first prompts to track and repair.
Where Rootly is winning5
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?
Avg # 1.0 · 1 platform
What on-call tools support noise reduction and alert grouping so engineers aren't paged for every individual monitoring alert during an outage?
Avg # 1.0 · 1 platform
What incident management tools support AI-assisted triage that suggests likely root cause and relevant runbooks when an alert fires?
Avg # 1.0 · 2 platforms
Which incident response tools come with built-in runbook templates so teams don't have to build their incident playbooks from scratch?
Avg # 1.5 · 2 platforms
What incident management tools integrate deeply with workplace chat platforms so the entire incident workflow happens inside the chat app?
Avg # 1.5 · 2 platforms
Where Rootly is losing5
What on-call platforms have the best mobile app for engineers who need to respond to alerts at 3am with minimum friction?
Competitors on 4 platforms
Track this promptWhich incident management tools let on-call engineers acknowledge, escalate, and update incidents directly from workplace chat without using a web dashboard?
Competitors on 4 platforms
Track this promptWhich on-call tools support bidirectional integration with a status page so incidents automatically update public status without manual intervention?
Competitors on 3 platforms
Track this promptWhich on-call platforms have the most pre-built integrations with monitoring and observability tools for automatic alert ingestion?
Competitors on 3 platforms
Track this promptWhich on-call platforms have the fastest alert delivery times from inbound webhook to phone call — which ones reliably page within 30 seconds?
Competitors on 3 platforms
Track this prompt
Track Rootly daily before the next report refresh.
Track these gapsResearch dossierCapabilities, use cases, sources, reviews, pricing, and FAQ
Overview
Rootly, Inc. is an AI-native incident management and on-call platform founded in 2020 in San Francisco by JJ Tang and Quentin Rousseau, both former Instacart employees. The platform covers the full incident lifecycle—on-call scheduling, Slack- and Teams-native incident response, AI-powered root cause analysis via its AI SRE agents, automated retrospectives, and customer-facing status pages—in a single purpose-built product. Rootly's AI SRE correlates alerts with code changes and past incidents to surface probable root causes and suggested fixes, reducing toil for SRE and DevOps teams. Trusted by enterprise customers including NVIDIA, LinkedIn, Figma, Tripadvisor, Dropbox, and Canva, Rootly positions itself as a modern, affordable alternative to legacy tools like PagerDuty and Opsgenie. A Y Combinator S21 graduate, Rootly has raised $15.2M and earned top-10 placement in Deloitte Canada's 2025 Technology Fast 50 program.
Rootly is an AI-native, end-to-end incident management platform comprising five integrated products: On-Call (scheduling, alerting, escalation policies, mobile paging), Incident Response (Slack/Teams-native coordination, workflow automation, stakeholder communications), AI SRE (automated root cause analysis, alert correlation with deploys/configs, remediation suggestions via MCP), Retrospectives (AI-generated postmortems, timeline reconstruction, action item tracking), and Status Pages (automated customer-facing and internal status communication). The platform is designed for SRE, DevOps, and platform engineering teams and is distinguished by its deep ChatOps-first architecture, opinionated best-practice defaults, and growing AI agent capabilities.
Key Facts
- Founded
- 2020
- HQ
- San Francisco, CA, USA
- Founders
- JJ Tang, Quentin Rousseau
- Employees
- 51-100
- Funding
- $15.2M
- Customers
- hundreds (exact count undisclosed)
- Status
- Private
Target users
Key Capabilities10
- AI SRE agents for automated root cause analysis with confidence scores and suggested remediations
- Slack-native and Microsoft Teams-native incident response with auto-channel creation, role assignment, and workflow automation
- AI-powered on-call scheduling with PTO-aware overrides, shadow rotations, live call routing, and mobile app (iOS/Android)
- Automated retrospective/postmortem generation with smart timelines, collaborative editing, and bi-directional Jira sync
- Customizable no-code workflow builder for incident automation across the full lifecycle
- Customer-facing and internal status pages with automated updates
- AI scribe and real-time meeting bot for in-incident documentation
- Advanced metrics and MTTR dashboards with DORA-aligned insights
- 70+ native integrations across observability, ticketing, deployment, and collaboration tools
- SOC 2 Type II, GDPR, CCPA, and HIPAA compliance with SSO/SAML/SCIM and audit logs
Key Use Cases8
- Replacing PagerDuty or Opsgenie with a unified on-call and incident response platform
- Automating incident response coordination within Slack or Microsoft Teams for distributed SRE/DevOps teams
- AI-assisted root cause analysis and remediation to reduce mean time to resolution (MTTR)
- Structured blameless postmortem and retrospective processes at scale
- Enterprise incident compliance and audit logging for regulated industries
- Proactive reliability culture-building with incident trend analytics and DORA metrics
- On-call health monitoring and burnout reduction for engineering teams
- Consolidating fragmented incident tooling into a single platform
Rootly customer outcomes
50% reduction in resolution times
Tripadvisor adopted Rootly as a core part of its incident response process, crediting it with allowing the team to spend more time on resolution and less time on manual administrative work.
Incident setup reduced from 15–60+ minutes to seconds; 99.99% reliability achieved at scale
Motive replaced Opsgenie with Rootly On-Call and integrated Rootly AI into its incident response workflows, eliminating manual setup steps and enabling responders to focus on resolution rather than logistics.
Recent Trend
How AI describes Rootly3
Rootly: Designed for end-to-end incident management with collaborative runbooks and conditional logic, plus Slack/Teams integrations for coordinated responses.
Which incident management platforms let engineering teams build and maintain runbooks collaboratively with a good editor experience?
Direct answer: For migrating from a legacy pager with existing rotation and escalation policies, incident.io On‑Call and Rootly are commonly cited as smooth upgrade paths, with built-in migration tooling to import schedules and policies and strong suppor...
Which on-call management tools have the smoothest migration path from a legacy pager tool with existing rotation schedules and escalation policies?
Rootly * Pros: AI-assisted post-mortems and automation, modern UI, strong incident context in alerts.
What on-call platforms have the best mobile app for engineers who need to respond to alerts at 3am with minimum friction?
Most cited sources8
20Rootly | Best Incident Postmortem Software for Downtime Management
rootly.com·Comparison
- 12
Rootly | Rootly AI SRE: Faster Incident Response & Automation
rootly.com·Comparison
- 9
AI-native incident management platform | Rootly
rootly.com·Comparison
- 7
Rootly | 2026 Guide: Best On‑Call Scheduling Tools for Every Team
rootly.com·Listicle
- 7
Rootly Guide | Incident Responses - Incident Response Runbooks: Templates, Examples & Guide
rootly.com·Comparison
- D6
PagerDuty Migration - Rootly
docs.rootly.com·Documentation
Alternatives in Incident Management & On-Call6
Rootly positions itself as a modern, AI-native alternative to legacy incident management incumbents (PagerDuty, Opsgenie), emphasizing a Slack/Teams-native workflow, opinionated defaults that enable rapid setup, and a unified platform spanning on-call, incident response, AI SRE agents, retrospectives, and status pages.
- It targets mid-market and enterprise engineering teams seeking to replace fragmented or high-cost legacy tooling with a purpose-built, automation-first platform at a price it markets as roughly half of incumbent costs.
- Rootly explicitly runs comparison pages against PagerDuty, Opsgenie, and Jira Service Management, and differentiates via its AI Labs research, MCP server integration, and BYOK (Bring Your Own AI Key) flexibility for enterprise buyers.
Reviews
Praised
- Slack-native integration reduces context switching
- Fast setup and time to first incident (under 2 hours reported)
- Powerful workflow automation eliminates manual admin work
- Highly responsive and knowledgeable customer support
- AI scribe and postmortem automation saves hours per incident
- Consistent and standardized incident process across teams
- Strong Jira bi-directional sync for action item tracking
- Visibility and metrics across the incident lifecycle
Criticized
- Advanced workflow configuration complexity requires multiple iterations
- Documentation gaps slow down building advanced workflows
- Fewer native out-of-box integrations than some legacy competitors
- UI can feel overwhelming when many workflows are active
- Microsoft Teams features limited to Enterprise tier
- Learning curve for complex multi-team enterprise rollouts
Rootly holds a 4.8/5 rating on G2 from 65 verified reviews, with 87% being 5-star ratings. Reviewers consistently praise its Slack-native workflow, automation capabilities, ease of initial setup (some users report getting up and running in under two hours), and highly responsive customer support. G2 has awarded Rootly badges including High Performer (Enterprise and Mid-Market), Momentum Leader, Best Support, and High User Adoption across multiple consecutive quarters in 2025 and 2026. Critical feedback clusters around advanced workflow configuration complexity—users note dependencies between workflows require careful management—and documentation gaps that slow down advanced use cases. Crozdesk scores the platform 92/100 in the ITSM category with 96/100 user satisfaction.
Pricing
Rootly prices Incident Response and On-Call as separate products, each with an Essentials tier at $20/user/month and an Enterprise tier at custom pricing. AI SRE is priced separately via custom quote. Discounts are offered when all three modules (IR, On-Call, AI SRE) are bundled. Startup discounts of up to 50% are available for companies with fewer than 100 employees, less than $50M raised, and less than 5 years in business; companies with fewer than 25 employees can pay what they can. A 14-day free trial with full feature access is available. Rootly is listed on the AWS Marketplace for EDP-eligible procurement. Third-party data from Vendr (cited in an incident.io competitive review) indicates an average contract value of approximately $13,066, with Essentials contracts for 20–50 users typically ranging from $15,000–$30,000 annually; this data should be treated as approximate and unverified by Rootly.
Limitations
- Advanced workflow configuration introduces dependency complexity that G2 reviewers note requires multiple iterations to match real-world team processes.
- Documentation gaps can slow down advanced workflow builds.
- Microsoft Teams features are gated to the Enterprise tier.
- Native out-of-box integration count may be lower than some legacy competitors, requiring webhook workarounds for unsupported tools.
- As a growth-stage company with ~75 employees, Rootly has a smaller review corpus on enterprise review platforms than incumbents like PagerDuty, and some users note the UI can feel overwhelming when many workflows are active.
- Revenue and financial metrics are undisclosed, making ROI benchmarking harder for procurement teams.
Frequently asked questions
Topic coverageCoverage by buyer topic
Topic Coverage
Prompt-Level Results
| Prompt | Perplexity | Google AI Mode | ChatGPT | Gemini Search | Bing Copilot | Grok |
|---|---|---|---|---|---|---|
Capability5/5 cited (100%) | ||||||
Which incident platforms have strong post-mortem and retrospective features that go beyond a blank document — structured templates, follow-up tracking, and metrics? | ||||||
What on-call tools support noise reduction and alert grouping so engineers aren't paged for every individual monitoring alert during an outage? | ||||||
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 Experience5/5 cited (100%) | ||||||
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 tools give engineers visibility into their own on-call burden so they can flag unsustainable alert volumes to their manager? | ||||||
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 & Ecosystem4/5 cited (80%) | ||||||
Which on-call tools support bidirectional integration with a status page so incidents automatically update public status without manual intervention? | ||||||
Which on-call platforms have the most pre-built integrations with monitoring and observability tools for automatic alert ingestion? | ||||||
What incident management platforms offer an API or IaC provider so on-call schedules and routing rules can be managed as code? | ||||||
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? | ||||||
Performance & Reliability5/5 cited (100%) | ||||||
What incident platforms scale well for a 1000-person engineering org with hundreds of on-call rotations and thousands of alert rules? | ||||||
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? | ||||||
Which on-call platforms have the fastest alert delivery times from inbound webhook to phone call — which ones reliably page within 30 seconds? | ||||||
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 Run5/5 cited (100%) | ||||||
Which on-call management tools have the smoothest migration path from a legacy pager tool with existing rotation schedules and escalation policies? | ||||||
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? | ||||||
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? | ||||||
Turn this matrix into daily prompt monitoring.
Track prompt changesVertical Ranking
| # | Brand | PresencePres. | Share of VoiceSoV | DocsDocs | BlogBlog | MentionsMent. | Avg PosPos | Sentiment |
|---|---|---|---|---|---|---|---|---|
| 1 | incident.io | 46.0% | 36.5% | 4.7% | 42.0% | 41.3% | #5.5 | +0.52 |
| 2 | Rootly | 26.0% | 21.8% | 2.0% | 5.3% | 20.7% | #5.4 | +0.45 |
| 3 | Opsgenie | 22.7% | 14.7% | 4.0% | 0.0% | 16.0% | #6.8 | +0.49 |
| 4 | PagerDuty | 14.0% | 10.4% | 0.0% | 0.7% | 12.7% | #7.5 | +0.40 |
| 5 | ilert | 8.0% | 3.2% | 0.7% | 1.3% | 8.0% | #3.5 | +0.31 |
| 6 | FireHydrant | 7.3% | 4.3% | 4.0% | 0.7% | 6.7% | #10.8 | +0.65 |
| 7 | OneUptime | 6.0% | 2.3% | 0.0% | 3.3% | 5.3% | #8.5 | +0.37 |
| 8 | Better Stack | 4.0% | 2.9% | 0.0% | 0.0% | 3.3% | #10.0 | +0.38 |
| 9 | Grafana | 3.3% | 1.8% | 2.0% | 0.0% | 2.7% | #5.5 | +0.28 |
| 10 | Squadcast | 2.0% | 1.6% | 0.0% | 0.7% | 1.3% | #4.7 | +0.27 |
| 11 | Spike.sh | 1.3% | 0.5% | 0.7% | 0.7% | 1.3% | #11.0 | +0.35 |
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.
Free trial. Setup comes pre-filled from this report.