# Rootly AI visibility in Incident Management & On-Call

Canonical: https://devtune.ai/verticals/incident-management-and-on-call/rootly

[Website](https://rootly.com/)

Updated: 2026-09-27T01:48:57.308123+00:00
Prompts: 25
Runs: 6


## Platforms

- chatgpt-search
- google-ai-mode
- bing-copilot-search
- google-ai
- perplexity
- xai-search

Rank: 1
Total brands: 11
Measured responses: 150
Presence percent: 39.33333333333333
Share of voice percent: 25.936599423631122
Average position: 3.611111111111111
Docs presence percent: 2.666666666666667
Blog presence percent: 10.666666666666668
Brand mention percent: 0


## Profile

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.
Product summary: 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 capabilities

- 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



### Target users

- Site Reliability Engineers (SREs) and platform engineering teams
- DevOps engineers managing on-call rotations and incident response
- Engineering managers and VPs seeking MTTR visibility and reliability metrics
- Mid-market and enterprise software companies with distributed engineering teams
- Companies migrating off PagerDuty, Opsgenie, or manual Slack-based incident workflows
- Startups scaling incident management processes for the first time



### Key use cases

- 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

Integrations ecosystem: Rootly offers 70+ named integrations organized across alerting, automation, catalog, communication, deployment, monitoring, retrospectives, and ticketing categories. Key integrations include: Monitoring/Observability—Datadog, Grafana, New Relic, Honeycomb, AWS CloudWatch, Prometheus Alertmanager, Sentry, Splunk, Rollbar, Nobl9; Communication—Slack (primary), Microsoft Teams, Zoom, Google Meet, Webex, Mattermost, X; Ticketing—Jira Cloud, Linear, Asana, ClickUp, Zendesk, Freshdesk, ServiceNow, Trello, Shortcut; Deployment—GitHub, GitLab, Kubernetes, Terraform, Pulumi, Heroku, AWS Elastic Beanstalk; Retrospectives/Docs—Confluence, Notion, Google Docs, Coda, SharePoint, Dropbox Paper, Quip, Airtable; Catalog—Backstage, Cortex, OpsLevel; AI/LLM—OpenAI, Anthropic (Claude), Google Gemini, Mistral AI (BYOK supported); Other—Zapier, Fivetran, Glean, Workday, BambooHR, HashiCorp Vault, AWS EventBridge, AWS SNS, Statuspage.io. Rootly also provides a Terraform provider, public REST API, CLI, webhooks, and an MCP server for IDE-native incident resolution. A Spotify Backstage plugin is available open-source.
Pricing summary: 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.
Review summary: 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.
Competitive positioning: 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.
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.


### Source urls

- https://rootly.com/
- https://rootly.com/pricing
- https://rootly.com/integrations
- https://rootly.com/customers/motive
- https://techcrunch.com/2023/08/10/incident-response-management-platform-rootly-secures-12m/
- https://www.thesaasnews.com/news/rootly-raises-12-million-in-series-a
- https://rootly.com/blog/rootly-raises-12-million-from-renegade-partners-google-gradient-ventures-xyz-ventures
- https://www.g2.com/sellers/rootly
- https://www.g2.com/products/rootly/reviews
- https://www.ycombinator.com/companies/rootly
- https://www.businesswire.com/news/home/20251023094479/en/Rootly-Announced-as-One-of-Deloittes-Technology-Fast-50-Program-Winners-for-2025
- https://checkthat.ai/brands/rootly
- https://www.globenewswire.com/news-release/2023/08/28/2732653/0/en/Rootly-Recognized-as-High-Performer-and-Enterprise-Leader-in-Incident-Management-for-Sixth-Consecutive-Quarter-in-G2-Summer-2023-Report.html
- https://aws.amazon.com/marketplace/pp/prodview-rghas6mvoo3re
- https://incident.io/blog/rootly-incident-management-review-2026

Reviewed at: 2026-04-28T23:32:01.734+00:00


### Customer outcomes

| Customer | Summary | Metric |
| --- | --- | --- |
| Tripadvisor | 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. | 50% reduction in resolution times |
| Motive | 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. | Incident setup reduced from 15–60+ minutes to seconds; 99.99% reliability achieved at scale |



### Reviews breakdown

| Platform | Score | Score max | Review count | Url |
| --- | --- | --- | --- | --- |
| G2 | 4.8 | 5 | 65 | https://www.g2.com/products/rootly/reviews |



### Review themes



#### 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




### Company facts

Founded year: 2020
Hq: San Francisco, CA, USA


#### Founders

- JJ Tang
- Quentin Rousseau

Employees range: 51-100
Total funding: $15.2M
Valuation: Not available
Arr: Not available
Customer count: hundreds (exact count undisclosed)
Status: Private


Readiness: Not available


## Ranking

| Display name | Pair count | Total pairs | Presence percent | Avg position |
| --- | --- | --- | --- | --- |
| Rootly | 59 | 150 | 39.33333333333333 | 3.611111111111111 |
| incident.io | 52 | 150 | 34.66666666666667 | 3.5730337078651684 |
| PagerDuty | 41 | 150 | 27.333333333333332 | 2.2 |
| Opsgenie | 31 | 150 | 20.666666666666668 | 4.258620689655173 |
| FireHydrant | 14 | 150 | 9.333333333333334 | 3.1578947368421053 |
| Grafana | 8 | 150 | 5.333333333333334 | 4.555555555555555 |
| ilert | 7 | 150 | 4.666666666666667 | 5.6 |
| OneUptime | 4 | 150 | 2.666666666666667 | 6.4 |
| Better Stack | 2 | 150 | 1.3333333333333335 | 4.5 |
| Spike.sh | 0 | 150 | 0 | Not available |
| Squadcast | 0 | 150 | 0 | Not available |



## Platform breakdown

| Platform | Prompt count | Presence rate |
| --- | --- | --- |
| chatgpt-search | 17 | 68 |
| google-ai-mode | 15 | 60 |
| bing-copilot-search | 9 | 36 |
| google-ai | 10 | 40 |
| perplexity | 8 | 32 |
| xai-search | 0 | 0 |



## Strengths

| Prompt text | Platform count | Avg position |
| --- | --- | --- |
| What on-call tools support noise reduction and alert grouping so engineers aren't paged for every individual monitoring alert during an outage? | 2 | 1 |
| What incident management platforms offer an API or IaC provider so on-call schedules and routing rules can be managed as code? | 2 | 1 |
| What on-call and incident platforms offer a public status page as part of the core product without requiring a separate subscription? | 1 | 1 |
| 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? | 3 | 1.3333333333333333 |
| 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? | 4 | 1.5 |



## Gaps

| Prompt text | Competitor presence count |
| --- | --- |
| Which on-call platforms have the most pre-built integrations with monitoring and observability tools for automatic alert ingestion? | 4 |
| Which on-call platforms have the fastest alert delivery times from inbound webhook to phone call — which ones reliably page within 30 seconds? | 3 |
| What incident platforms scale well for a 1000-person engineering org with hundreds of on-call rotations and thousands of alert rules? | 2 |



## Topic scores

| Topic name | Prompt count | Cited prompt count |
| --- | --- | --- |
| Capability | 5 | 5 |
| Developer Experience | 5 | 5 |
| Integrations & Ecosystem | 5 | 4 |
| Performance & Reliability | 5 | 3 |
| Setup & First Run | 5 | 5 |



## Prompt results

- Prompt text: Which on-call tools have a reliable global phone network that can reach engineers in multiple countries with consistent call quality?


#### Brand position by platform

Chatgpt-search: Not available
Google-ai-mode: 3
Bing-copilot-search: Not available
Google-ai: Not available
Perplexity: Not available
Xai-search: Not available



#### Platform rows



##### Chatgpt-search

| Display name | Position |
| --- | --- |
| PagerDuty | 2 |
| Opsgenie | 3 |



##### Google-ai-mode

| Display name | Position |
| --- | --- |
| Rootly | 3 |



##### Bing-copilot-search





##### Google-ai





##### Perplexity

| Display name | Position |
| --- | --- |
| ilert | 4 |
| Grafana | 6 |



##### Xai-search




- Prompt text: What on-call tools support noise reduction and alert grouping so engineers aren't paged for every individual monitoring alert during an outage?


#### Brand position by platform

Chatgpt-search: 1
Google-ai-mode: Not available
Bing-copilot-search: Not available
Google-ai: 1
Perplexity: Not available
Xai-search: Not available



#### Platform rows



##### Chatgpt-search

| Display name | Position |
| --- | --- |
| Rootly | 1 |
| PagerDuty | 2 |
| Grafana | 3 |



##### Google-ai-mode

| Display name | Position |
| --- | --- |
| incident.io | 1 |



##### Bing-copilot-search





##### Google-ai

| Display name | Position |
| --- | --- |
| Rootly | 1 |



##### Perplexity

| Display name | Position |
| --- | --- |
| PagerDuty | 1 |
| Opsgenie | 5 |
| incident.io | 8 |



##### Xai-search




- Prompt text: What incident platforms scale well for a 1000-person engineering org with hundreds of on-call rotations and thousands of alert rules?


#### Brand position by platform

Chatgpt-search: Not available
Google-ai-mode: Not available
Bing-copilot-search: Not available
Google-ai: Not available
Perplexity: Not available
Xai-search: Not available



#### Platform rows



##### Chatgpt-search





##### Google-ai-mode

| Display name | Position |
| --- | --- |
| PagerDuty | 1 |
| incident.io | 3 |



##### Bing-copilot-search





##### Google-ai





##### Perplexity

| Display name | Position |
| --- | --- |
| PagerDuty | 1 |
| incident.io | 6 |



##### Xai-search




- Prompt text: What on-call tools give engineers visibility into their own on-call burden so they can flag unsustainable alert volumes to their manager?


#### Brand position by platform

Chatgpt-search: 3
Google-ai-mode: Not available
Bing-copilot-search: Not available
Google-ai: Not available
Perplexity: 4
Xai-search: Not available



#### Platform rows



##### Chatgpt-search

| Display name | Position |
| --- | --- |
| PagerDuty | 1 |
| Opsgenie | 2 |
| Rootly | 3 |



##### Google-ai-mode





##### Bing-copilot-search





##### Google-ai





##### Perplexity

| Display name | Position |
| --- | --- |
| incident.io | 1 |
| Rootly | 4 |



##### Xai-search




- Prompt text: Which on-call platforms have the fastest alert delivery times from inbound webhook to phone call — which ones reliably page within 30 seconds?


#### Brand position by platform

Chatgpt-search: Not available
Google-ai-mode: Not available
Bing-copilot-search: Not available
Google-ai: Not available
Perplexity: Not available
Xai-search: Not available



#### Platform rows



##### Chatgpt-search

| Display name | Position |
| --- | --- |
| Opsgenie | 2 |
| incident.io | 3 |



##### Google-ai-mode

| Display name | Position |
| --- | --- |
| incident.io | 3 |



##### Bing-copilot-search





##### Google-ai





##### Perplexity

| Display name | Position |
| --- | --- |
| PagerDuty | 1 |
| Opsgenie | 3 |
| incident.io | 4 |



##### Xai-search




- Prompt text: Looking for an incident tool that auto-generates a timeline and draft post-mortem from chat history and alert events — which platforms do this?


#### Brand position by platform

Chatgpt-search: 2
Google-ai-mode: Not available
Bing-copilot-search: 1
Google-ai: 2
Perplexity: 5
Xai-search: Not available



#### Platform rows



##### Chatgpt-search

| Display name | Position |
| --- | --- |
| incident.io | 1 |
| Rootly | 2 |
| FireHydrant | 3 |
| Opsgenie | 4 |



##### Google-ai-mode





##### Bing-copilot-search

| Display name | Position |
| --- | --- |
| Rootly | 1 |
| incident.io | 4 |



##### Google-ai

| Display name | Position |
| --- | --- |
| Rootly | 2 |



##### Perplexity

| Display name | Position |
| --- | --- |
| incident.io | 1 |
| Rootly | 5 |



##### Xai-search




- Prompt text: What incident management tools maintain their own uptime independently so they still function when the service they monitor goes down?


#### Brand position by platform

Chatgpt-search: 2
Google-ai-mode: 2
Bing-copilot-search: Not available
Google-ai: Not available
Perplexity: Not available
Xai-search: Not available



#### Platform rows



##### Chatgpt-search

| Display name | Position |
| --- | --- |
| PagerDuty | 1 |
| Rootly | 2 |
| Opsgenie | 3 |



##### Google-ai-mode

| Display name | Position |
| --- | --- |
| Rootly | 2 |



##### Bing-copilot-search

| Display name | Position |
| --- | --- |
| OneUptime | 2 |



##### Google-ai





##### Perplexity

| Display name | Position |
| --- | --- |
| PagerDuty | 1 |



##### Xai-search




- Prompt text: Which on-call platforms have the most pre-built integrations with monitoring and observability tools for automatic alert ingestion?


#### Brand position by platform

Chatgpt-search: Not available
Google-ai-mode: Not available
Bing-copilot-search: Not available
Google-ai: Not available
Perplexity: Not available
Xai-search: Not available



#### Platform rows



##### Chatgpt-search

| Display name | Position |
| --- | --- |
| PagerDuty | 1 |
| Opsgenie | 2 |
| incident.io | 4 |



##### Google-ai-mode

| Display name | Position |
| --- | --- |
| PagerDuty | 1 |
| incident.io | 2 |



##### Bing-copilot-search

| Display name | Position |
| --- | --- |
| incident.io | 1 |



##### Google-ai





##### Perplexity

| Display name | Position |
| --- | --- |
| PagerDuty | 1 |
| Opsgenie | 2 |



##### Xai-search




- Prompt text: What incident management platforms offer an API or IaC provider so on-call schedules and routing rules can be managed as code?


#### Brand position by platform

Chatgpt-search: Not available
Google-ai-mode: 1
Bing-copilot-search: Not available
Google-ai: 1
Perplexity: Not available
Xai-search: Not available



#### Platform rows



##### Chatgpt-search

| Display name | Position |
| --- | --- |
| Grafana | 2 |



##### Google-ai-mode

| Display name | Position |
| --- | --- |
| Rootly | 1 |
| incident.io | 3 |



##### Bing-copilot-search

| Display name | Position |
| --- | --- |
| Grafana | 2 |



##### Google-ai

| Display name | Position |
| --- | --- |
| Rootly | 1 |
| PagerDuty | 2 |



##### Perplexity

| Display name | Position |
| --- | --- |
| PagerDuty | 1 |
| Opsgenie | 4 |



##### Xai-search




- Prompt text: What on-call and incident platforms offer a public status page as part of the core product without requiring a separate subscription?


#### Brand position by platform

Chatgpt-search: Not available
Google-ai-mode: 1
Bing-copilot-search: Not available
Google-ai: Not available
Perplexity: Not available
Xai-search: Not available



#### Platform rows



##### Chatgpt-search





##### Google-ai-mode

| Display name | Position |
| --- | --- |
| Rootly | 1 |



##### Bing-copilot-search





##### Google-ai





##### Perplexity

| Display name | Position |
| --- | --- |
| incident.io | 1 |
| ilert | 2 |
| Better Stack | 3 |
| PagerDuty | 5 |
| FireHydrant | 6 |
| OneUptime | 9 |
| Opsgenie | 11 |



##### Xai-search




- Prompt text: 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?


#### Brand position by platform

Chatgpt-search: 2
Google-ai-mode: 1
Bing-copilot-search: 1
Google-ai: Not available
Perplexity: Not available
Xai-search: Not available



#### Platform rows



##### Chatgpt-search

| Display name | Position |
| --- | --- |
| incident.io | 1 |
| Rootly | 2 |
| PagerDuty | 3 |
| Opsgenie | 4 |



##### Google-ai-mode

| Display name | Position |
| --- | --- |
| Rootly | 1 |
| incident.io | 2 |



##### Bing-copilot-search

| Display name | Position |
| --- | --- |
| Rootly | 1 |



##### Google-ai





##### Perplexity

| Display name | Position |
| --- | --- |
| PagerDuty | 1 |
| Opsgenie | 4 |
| incident.io | 6 |



##### Xai-search




- Prompt text: 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?


#### Brand position by platform

Chatgpt-search: 2
Google-ai-mode: Not available
Bing-copilot-search: 12
Google-ai: Not available
Perplexity: 6
Xai-search: Not available



#### Platform rows



##### Chatgpt-search

| Display name | Position |
| --- | --- |
| incident.io | 1 |
| Rootly | 2 |
| Opsgenie | 3 |



##### Google-ai-mode

| Display name | Position |
| --- | --- |
| PagerDuty | 1 |
| incident.io | 2 |
| Opsgenie | 3 |



##### Bing-copilot-search

| Display name | Position |
| --- | --- |
| incident.io | 2 |
| Rootly | 12 |



##### Google-ai





##### Perplexity

| Display name | Position |
| --- | --- |
| incident.io | 1 |
| Rootly | 6 |



##### Xai-search




- Prompt text: Which on-call management tools have the smoothest migration path from a legacy pager tool with existing rotation schedules and escalation policies?


#### Brand position by platform

Chatgpt-search: 3
Google-ai-mode: 1
Bing-copilot-search: Not available
Google-ai: Not available
Perplexity: Not available
Xai-search: Not available



#### Platform rows



##### Chatgpt-search

| Display name | Position |
| --- | --- |
| incident.io | 1 |
| FireHydrant | 2 |
| Rootly | 3 |
| Opsgenie | 4 |



##### Google-ai-mode

| Display name | Position |
| --- | --- |
| Rootly | 1 |
| FireHydrant | 2 |



##### Bing-copilot-search

| Display name | Position |
| --- | --- |
| incident.io | 2 |



##### Google-ai





##### Perplexity

| Display name | Position |
| --- | --- |
| incident.io | 1 |
| FireHydrant | 5 |
| Grafana | 6 |



##### Xai-search




- Prompt text: 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?


#### Brand position by platform

Chatgpt-search: 1
Google-ai-mode: 2
Bing-copilot-search: Not available
Google-ai: 1
Perplexity: 2
Xai-search: Not available



#### Platform rows



##### Chatgpt-search

| Display name | Position |
| --- | --- |
| Rootly | 1 |
| Opsgenie | 2 |
| incident.io | 3 |
| FireHydrant | 4 |
| PagerDuty | 5 |



##### Google-ai-mode

| Display name | Position |
| --- | --- |
| incident.io | 1 |
| Rootly | 2 |



##### Bing-copilot-search

| Display name | Position |
| --- | --- |
| incident.io | 1 |



##### Google-ai

| Display name | Position |
| --- | --- |
| Rootly | 1 |



##### Perplexity

| Display name | Position |
| --- | --- |
| Opsgenie | 1 |
| Rootly | 2 |
| PagerDuty | 3 |
| incident.io | 6 |



##### Xai-search




- Prompt text: Which incident response tools come with built-in runbook templates so teams don't have to build their incident playbooks from scratch?


#### Brand position by platform

Chatgpt-search: 3
Google-ai-mode: Not available
Bing-copilot-search: Not available
Google-ai: 5
Perplexity: 4
Xai-search: Not available



#### Platform rows



##### Chatgpt-search

| Display name | Position |
| --- | --- |
| PagerDuty | 1 |
| FireHydrant | 2 |
| Rootly | 3 |



##### Google-ai-mode





##### Bing-copilot-search





##### Google-ai

| Display name | Position |
| --- | --- |
| FireHydrant | 1 |
| PagerDuty | 4 |
| Rootly | 5 |
| OneUptime | 7 |



##### Perplexity

| Display name | Position |
| --- | --- |
| Opsgenie | 2 |
| Rootly | 4 |



##### Xai-search




- Prompt text: What on-call platforms have the best mobile app for engineers who need to respond to alerts at 3am with minimum friction?


#### Brand position by platform

Chatgpt-search: 2
Google-ai-mode: 1
Bing-copilot-search: Not available
Google-ai: Not available
Perplexity: 6
Xai-search: Not available



#### Platform rows



##### Chatgpt-search

| Display name | Position |
| --- | --- |
| PagerDuty | 1 |
| Rootly | 2 |
| Grafana | 4 |
| Opsgenie | 5 |



##### Google-ai-mode

| Display name | Position |
| --- | --- |
| Rootly | 1 |



##### Bing-copilot-search

| Display name | Position |
| --- | --- |
| incident.io | 4 |



##### Google-ai

| Display name | Position |
| --- | --- |
| incident.io | 5 |



##### Perplexity

| Display name | Position |
| --- | --- |
| PagerDuty | 1 |
| Rootly | 6 |



##### Xai-search




- Prompt text: Which incident management tools let on-call engineers acknowledge, escalate, and update incidents directly from workplace chat without using a web dashboard?


#### Brand position by platform

Chatgpt-search: 2
Google-ai-mode: 1
Bing-copilot-search: 3
Google-ai: 2
Perplexity: Not available
Xai-search: Not available



#### Platform rows



##### Chatgpt-search

| Display name | Position |
| --- | --- |
| Opsgenie | 1 |
| Rootly | 2 |
| ilert | 3 |



##### Google-ai-mode

| Display name | Position |
| --- | --- |
| Rootly | 1 |



##### Bing-copilot-search

| Display name | Position |
| --- | --- |
| incident.io | 1 |
| Rootly | 3 |



##### Google-ai

| Display name | Position |
| --- | --- |
| Rootly | 2 |



##### Perplexity

| Display name | Position |
| --- | --- |
| PagerDuty | 1 |
| incident.io | 3 |
| Grafana | 5 |
| Better Stack | 6 |



##### Xai-search




- Prompt text: What incident management tools integrate deeply with workplace chat platforms so the entire incident workflow happens inside the chat app?


#### Brand position by platform

Chatgpt-search: 2
Google-ai-mode: 1
Bing-copilot-search: 4
Google-ai: Not available
Perplexity: 3
Xai-search: Not available



#### Platform rows



##### Chatgpt-search

| Display name | Position |
| --- | --- |
| incident.io | 1 |
| Rootly | 2 |
| Opsgenie | 3 |



##### Google-ai-mode

| Display name | Position |
| --- | --- |
| Rootly | 1 |



##### Bing-copilot-search

| Display name | Position |
| --- | --- |
| incident.io | 1 |
| Rootly | 4 |



##### Google-ai

| Display name | Position |
| --- | --- |
| incident.io | 1 |
| ilert | 8 |



##### Perplexity

| Display name | Position |
| --- | --- |
| Rootly | 3 |
| ilert | 4 |



##### Xai-search




- Prompt text: What incident management tools support AI-assisted triage that suggests likely root cause and relevant runbooks when an alert fires?


#### Brand position by platform

Chatgpt-search: 2
Google-ai-mode: 3
Bing-copilot-search: Not available
Google-ai: Not available
Perplexity: Not available
Xai-search: Not available



#### Platform rows



##### Chatgpt-search

| Display name | Position |
| --- | --- |
| incident.io | 1 |
| Rootly | 2 |
| PagerDuty | 4 |



##### Google-ai-mode

| Display name | Position |
| --- | --- |
| Rootly | 3 |



##### Bing-copilot-search





##### Google-ai





##### Perplexity

| Display name | Position |
| --- | --- |
| PagerDuty | 1 |
| FireHydrant | 3 |
| incident.io | 5 |



##### Xai-search




- Prompt text: Which incident management platforms support multi-service incident coordination where separate on-call teams are engaged simultaneously?


#### Brand position by platform

Chatgpt-search: Not available
Google-ai-mode: 2
Bing-copilot-search: 1
Google-ai: Not available
Perplexity: Not available
Xai-search: Not available



#### Platform rows



##### Chatgpt-search

| Display name | Position |
| --- | --- |
| PagerDuty | 1 |
| Opsgenie | 2 |
| FireHydrant | 3 |



##### Google-ai-mode

| Display name | Position |
| --- | --- |
| incident.io | 1 |
| Rootly | 2 |
| FireHydrant | 3 |



##### Bing-copilot-search

| Display name | Position |
| --- | --- |
| Rootly | 1 |



##### Google-ai

| Display name | Position |
| --- | --- |
| PagerDuty | 1 |



##### Perplexity

| Display name | Position |
| --- | --- |
| PagerDuty | 1 |
| incident.io | 3 |



##### Xai-search




- Prompt text: Which on-call tools support bidirectional integration with a status page so incidents automatically update public status without manual intervention?


#### Brand position by platform

Chatgpt-search: 2
Google-ai-mode: 2
Bing-copilot-search: Not available
Google-ai: 4
Perplexity: Not available
Xai-search: Not available



#### Platform rows



##### Chatgpt-search

| Display name | Position |
| --- | --- |
| PagerDuty | 1 |
| Rootly | 2 |
| incident.io | 3 |
| Opsgenie | 4 |



##### Google-ai-mode

| Display name | Position |
| --- | --- |
| Rootly | 2 |
| PagerDuty | 3 |



##### Bing-copilot-search





##### Google-ai

| Display name | Position |
| --- | --- |
| Opsgenie | 1 |
| Rootly | 4 |
| ilert | 6 |



##### Perplexity

| Display name | Position |
| --- | --- |
| Opsgenie | 1 |
| PagerDuty | 2 |



##### Xai-search




- Prompt text: 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?


#### Brand position by platform

Chatgpt-search: 4
Google-ai-mode: Not available
Bing-copilot-search: 3
Google-ai: 4
Perplexity: Not available
Xai-search: Not available



#### Platform rows



##### Chatgpt-search

| Display name | Position |
| --- | --- |
| incident.io | 1 |
| PagerDuty | 2 |
| Opsgenie | 3 |
| Rootly | 4 |
| Grafana | 5 |



##### Google-ai-mode

| Display name | Position |
| --- | --- |
| PagerDuty | 1 |



##### Bing-copilot-search

| Display name | Position |
| --- | --- |
| incident.io | 1 |
| Rootly | 3 |



##### Google-ai

| Display name | Position |
| --- | --- |
| Rootly | 4 |



##### Perplexity

| Display name | Position |
| --- | --- |
| PagerDuty | 1 |
| Opsgenie | 4 |



##### Xai-search




- Prompt text: 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?


#### Brand position by platform

Chatgpt-search: Not available
Google-ai-mode: 1
Bing-copilot-search: 7
Google-ai: Not available
Perplexity: Not available
Xai-search: Not available



#### Platform rows



##### Chatgpt-search

| Display name | Position |
| --- | --- |
| PagerDuty | 1 |
| Opsgenie | 3 |
| incident.io | 4 |



##### Google-ai-mode

| Display name | Position |
| --- | --- |
| Rootly | 1 |
| PagerDuty | 2 |



##### Bing-copilot-search

| Display name | Position |
| --- | --- |
| Rootly | 7 |



##### Google-ai

| Display name | Position |
| --- | --- |
| ilert | 8 |



##### Perplexity

| Display name | Position |
| --- | --- |
| PagerDuty | 1 |
| Opsgenie | 4 |



##### Xai-search




- Prompt text: Which incident management platforms let engineering teams build and maintain runbooks collaboratively with a good editor experience?


#### Brand position by platform

Chatgpt-search: 2
Google-ai-mode: Not available
Bing-copilot-search: Not available
Google-ai: 1
Perplexity: Not available
Xai-search: Not available



#### Platform rows



##### Chatgpt-search

| Display name | Position |
| --- | --- |
| incident.io | 1 |
| Rootly | 2 |
| FireHydrant | 3 |
| PagerDuty | 4 |



##### Google-ai-mode

| Display name | Position |
| --- | --- |
| incident.io | 1 |



##### Bing-copilot-search





##### Google-ai

| Display name | Position |
| --- | --- |
| Rootly | 1 |



##### Perplexity

| Display name | Position |
| --- | --- |
| FireHydrant | 4 |
| OneUptime | 6 |



##### Xai-search




- Prompt text: Which incident platforms have strong post-mortem and retrospective features that go beyond a blank document — structured templates, follow-up tracking, and metrics?


#### Brand position by platform

Chatgpt-search: 1
Google-ai-mode: 1
Bing-copilot-search: 1
Google-ai: 1
Perplexity: 7
Xai-search: Not available



#### Platform rows



##### Chatgpt-search

| Display name | Position |
| --- | --- |
| Rootly | 1 |
| FireHydrant | 2 |
| incident.io | 4 |
| PagerDuty | 5 |



##### Google-ai-mode

| Display name | Position |
| --- | --- |
| Rootly | 1 |
| incident.io | 2 |



##### Bing-copilot-search

| Display name | Position |
| --- | --- |
| Rootly | 1 |
| incident.io | 3 |



##### Google-ai

| Display name | Position |
| --- | --- |
| Rootly | 1 |
| incident.io | 2 |



##### Perplexity

| Display name | Position |
| --- | --- |
| incident.io | 1 |
| Opsgenie | 3 |
| Rootly | 7 |



##### Xai-search







## Top sources

| Url | Title | Domain | Logo url | Source vertical | Content type | Citation count | Last30d count |
| --- | --- | --- | --- | --- | --- | --- | --- |
| https://rootly.com/blog/best-incident-postmortem-software-2026 | Best incident postmortem software for 2026: Complete Guide \| Rootly | rootly.com | https://izgwnlozsmjmqjsnddmg.supabase.co/storage/v1/object/public/domain-logos/9dbab6f8-54b2-49a0-8181-89a0ed130318/53005bca-a629-4268-994a-ae58475befb6/4fe81fc829aff06e05badd7c993fda9b4a503393.png | commercial | comparison | 26 | 26 |
| https://rootly.com/blog/15-best-incident-response-software-platforms-for-modern-engineering-teams-2026 | Best Incident Management & Response Software: 15 Top Platforms (2026) \| Rootly | rootly.com | https://izgwnlozsmjmqjsnddmg.supabase.co/storage/v1/object/public/domain-logos/9dbab6f8-54b2-49a0-8181-89a0ed130318/53005bca-a629-4268-994a-ae58475befb6/4fe81fc829aff06e05badd7c993fda9b4a503393.png | commercial | comparison | 25 | 25 |
| https://docs.rootly.com/integrations/terraform | Terraform - Rootly documentation | docs.rootly.com | Not available | commercial | documentation | 13 | 13 |
| https://rootly.com/sre/ultimate-2026-guide-incident-postmortem-tools-teams | Ultimate 2026 Guide to Incident Postmortem Tools for Teams \| Rootly | rootly.com | https://izgwnlozsmjmqjsnddmg.supabase.co/storage/v1/object/public/domain-logos/9dbab6f8-54b2-49a0-8181-89a0ed130318/53005bca-a629-4268-994a-ae58475befb6/4fe81fc829aff06e05badd7c993fda9b4a503393.png | commercial | comparison | 12 | 12 |
| https://rootly.com/incident-response/runbooks | Incident Response Runbooks: Templates, Examples & Guide \| Rootly | rootly.com | https://izgwnlozsmjmqjsnddmg.supabase.co/storage/v1/object/public/domain-logos/9dbab6f8-54b2-49a0-8181-89a0ed130318/53005bca-a629-4268-994a-ae58475befb6/4fe81fc829aff06e05badd7c993fda9b4a503393.png | commercial | comparison | 10 | 10 |
| https://rootly.com/sre/best-incident-management-software-microsoft-teams-2026 | Best Incident Management Software for Microsoft Teams (2026) \| Rootly | rootly.com | https://izgwnlozsmjmqjsnddmg.supabase.co/storage/v1/object/public/domain-logos/9dbab6f8-54b2-49a0-8181-89a0ed130318/53005bca-a629-4268-994a-ae58475befb6/4fe81fc829aff06e05badd7c993fda9b4a503393.png | commercial | comparison | 10 | 10 |
| https://rootly.com/sre/incident-management-software-jira-integration-2026 | Incident Management Software with Jira Integration (2026) \| Rootly | rootly.com | https://izgwnlozsmjmqjsnddmg.supabase.co/storage/v1/object/public/domain-logos/9dbab6f8-54b2-49a0-8181-89a0ed130318/53005bca-a629-4268-994a-ae58475befb6/4fe81fc829aff06e05badd7c993fda9b4a503393.png | commercial | comparison | 10 | 10 |
| https://rootly.com/sre/top-incident-response-platforms-for-slack-first-teams | Rootly \| Top Incident Response Platforms for Slack-First Teams | rootly.com | https://izgwnlozsmjmqjsnddmg.supabase.co/storage/v1/object/public/domain-logos/9dbab6f8-54b2-49a0-8181-89a0ed130318/53005bca-a629-4268-994a-ae58475befb6/4fe81fc829aff06e05badd7c993fda9b4a503393.png | commercial | comparison | 9 | 9 |



## Response excerpts

| Prompt text | Platform | Excerpt |
| --- | --- | --- |
| What incident management platforms offer an API or IaC provider so on-call schedules and routing rules can be managed as code? | chatgpt-search | \[1\] \| \| Rootly \| ✅ Terraform \| ✅ Escalation policies/paths/levels \| Terraform + API \| Particularly strong “on-call as code” story; supports schedules, rotations, escalation policies and paths in Terraform. |
| What on-call tools give engineers visibility into their own on-call burden so they can flag unsustainable alert volumes to their manager? | chatgpt-search | ...Strong \| Alerts received/acknowledged/closed per user, priority, escalations, daily distribution, on-call hours \| \| Rootly \| Strong \| Explicit on-call load by engineer, alert volume, incident metrics \| \| incident.io \| Moderate... |
| What on-call tools support noise reduction and alert grouping so engineers aren't paged for every individual monitoring alert during an outage? | chatgpt-search | ...and cross-service alert grouping; deduplication; suppression and auto-pause \| Large/mixed monitoring environments \| \| Rootly \| Alert deduplication plus alert grouping/correlation across monitoring sources \| Teams wanting incident management tight... |



## Competitor excerpts

| Platform | Competitor name | Excerpt |
| --- | --- | --- |
| chatgpt-search | PagerDuty | ...ughly: \| Platform \| Integration breadth \| Particularly strong for \| Notes \| \| --- \| --- \| --- \| --- \| \| PagerDuty \| 750+ integrations \| Broadest monitoring/observability ecosystem \| Strong coverage across APM, infrastructure, log... |
| chatgpt-search | Opsgenie | \[1\] \| \| Opsgenie \| 200+ integrations \| Monitoring-heavy environments \| Extensive native integrations for Datadog, Dynatrace, New Relic, Prometheus, Nagios, Sentry, LogicMonitor, CloudWatch, etc. \[2\] \| \| Splunk On-Call \| 300+ in... |
| google-ai-mode | PagerDuty | You can trigger complex workflows using conditional logic, assign roles, query integrated tools like Jira or PagerDuty, and leverage "Ask Rootly AI" to summarize timelines or draft executive updates entirely in plain English within the channel. |
| google-ai-mode | incident.io | Incident.io +1 The leading platforms providing this deep, end-to-end chat integration include: * incident.io : Widely regarded as a leader in Slack-first architecture. |
| bing-copilot-search | incident.io | ...tforms with the broadest pre-built integrations for monitoring and observability tools are PagerDuty (700+ integrations), incident.io (50+ integrations across monitoring, ticketing, and cloud), FireHydrant (Slack-native with strong observability tie-ins)... |
| perplexity | PagerDuty | Among the major on-call platforms, PagerDuty appears to have the broadest pre-built integration ecosystem, followed by Opsgenie and Splunk On-Call. |
| perplexity | Opsgenie | Among the major on-call platforms, PagerDuty appears to have the broadest pre-built integration ecosystem, followed by Opsgenie and Splunk On-Call. |
| chatgpt-search | Opsgenie | \[1\] \| \| Opsgenie \| High \| Supports webhook/API ingestion and voice notifications. |
| chatgpt-search | incident.io | \| \| incident.io \| Medium–High \| Strong incident workflow platform; typically paired with other alerting sources. |
| google-ai-mode | incident.io | Incident.io +1 * Better Stack is widely praised by engineers for having one of the cleanest, most modern UIs in the observability space. |
| perplexity | PagerDuty | ...sed on the published evidence available here. The strongest candidates for a sub-30-second *best-case* path are likely PagerDuty and possibly incident.io with a voice provider, but their public documentation does not establish a 30-second webho... |
| perplexity | Opsgenie | \| \| Opsgenie \| Phone notifications may be aggregated and sent at intervals of up to four minutes.[3] \| No. Its documented aggregation behavior is incompatible with a dependable 30-second guarantee unless specifically configured and tested otherwise. |



## Trend

Visibility delta: 7.999999999999993
Avg position delta: -0.16937669376693743
Citation count delta: 8