# Rootly > Rootly is the AI incident management platform that unifies on-call, incident response, retrospectives, and status pages - built for fast-moving engineering teams to resolve incidents faster with Slack/Teams-native workflows, automation, and AI assistance. Rootly is an AI-native incident management platform for fast-moving engineering teams. It brings on-call alerting/paging, incident response workflows in Slack or Microsoft Teams, post-incident learning (retrospectives), and status pages into one place. Teams use Rootly's automations and AI to coordinate responders, keep stakeholders updated, and capture timelines and follow-ups - so incidents resolve faster and learning compounds over time. Category: Incident Management (AI-native on-call + incident response + retrospectives + status pages + AI SRE) Trusted by: DoorDash, NVIDIA, Figma, Dropbox, SoFi, Replit, Stack Overflow, Superhuman, Clay, Wealthsimple, Glean, Canva, TripAdvisor, Trivago, WIX, Brex, Sailpoint ## Products - [Rootly On-Call](https://rootly.com/on-call): Alerts, paging, schedules, escalations, coverage workflows, live call routing, heartbeats, and mobile apps - [Incident Response for Slack](https://rootly.com/incident-response-slack): Slack-native incident workflows with automations and AI assistance - [Incident Response for Microsoft Teams](https://rootly.com/incident-response-microsoft-teams): Teams-native incident workflows with automations and AI assistance - [Incident Response for Google Chat](https://rootly.com/incident-response-with-google-chat): Googel Chat-native incident workflows with automations and AI assistance - [Retrospectives](https://rootly.com/retrospectives): Post-incident learning with automated timelines, templates, action items, and reliability metrics - [Rootly AI SRE](https://rootly.com/ai-sre): AI investigation across the incident lifecycle - root cause analysis with confidence scores, summaries, drafting, and suggested fixes - [Status Pages](https://rootly.com/status-pages): Public, private, and internal status pages with workflow-driven updates - [Mobile App](https://rootly.com/mobile): On-call paging, alerts, and AI-assisted incident response on iOS and Android # AI Capabilities Rootly AI works across the entire incident lifecycle - in Slack, Microsoft Teams, mobile, and your IDE. Every AI action runs as your user within your permissions, and any change requires explicit human sign-off before execution (human in the loop). - AI SRE root cause analysis: Investigates the moment an alert fires, runs parallel hypothesis checks across alerts, telemetry, recent deployments, and past incidents, and surfaces ranked, evidence-backed root cause with confidence scores and suggested fixes. - Transparent reasoning: Shows its reasoning chain at every step (no black box); AI blocks let you view and edit the prompts that generate results. - Conversational AI assistant (@Rootly): Ask questions in natural language and take action in-channel - page someone, change severity or status, manage action items, draft comms - in Slack or Microsoft Teams. - Catch-up and incident summaries: Personalized summaries that get late joiners and stakeholders up to speed in seconds. - Meeting scribe and live call transcription: The Rootly AI Meeting Bot joins incident bridge calls to transcribe in real time and capture context so nothing is missed. - Automated stakeholder communications: Drafts audience-specific updates for responders, leadership, and customers, and keeps the status page current as the incident changes state. - Similar and related incident matching: Surfaces relevant past incidents and proven solutions, and can bring in previous responders. - Proactive nudges and suggestions: Suggested troubleshooting steps, next actions, and who to page. - Auto-generated retrospectives: Builds the incident timeline live and drafts summary, impact, root cause, mitigation, and action items - all editable, with tasks tracked to completion. - Natural-language insights and reports: Ask for instant reports on reliability and retrospective metrics (such as time spent or outstanding action items) in plain language. - On-call coverage AI: Finds and schedules a substitute for coverage and PTO requests from plain-language input. - Mobile AI: Ask questions and direct actions (acknowledge, escalate, hand off) from the iOS and Android apps, from anywhere. - MCP server: Connects Rootly to AI agents and IDEs (Cursor, Windsurf, Claude) so agents can query incidents and configure on-call and response directly. - Bring your own LLM keys: Use your own model provider keys for single-turn AI features. - AI data protection: Zero third-party model training; incident data is used only for your organization and never pooled across customers; sensitive data (links, emails, passwords) is redacted before being sent to AI providers; AI access respects incident privacy settings. ## Guides & Pillars - [The Complete Guide to AI SRE](https://rootly.com/ai-sre-guide): Architecture, concepts, lifecycle, maturity model, metrics/ROI, and implementation of AI for site reliability - [Incident Response: A Complete Guide](https://rootly.com/incident-response): Lifecycle, roles, best practices, metrics, playbooks, and runbooks - [On-Call Management Guide](https://rootly.com/on-call-software): Schedules, rotations, escalation policies, alert fatigue, and on-call best practices - [Incident Postmortems Guide](https://rootly.com/incident-postmortems): Blameless postmortems, templates, timelines, and meeting guides - [Incident Communications Guide](https://rootly.com/incident-communications): Building a robust incident response communication plan ## Comparisons - [Rootly vs PagerDuty](https://rootly.com/alternatives/rootly-vs-pagerduty): All-in-one incident management vs paging-only, at roughly half the cost - [Rootly vs Opsgenie](https://rootly.com/alternatives/rootly-vs-opsgenie): Migrating off Opsgenie before its April 2027 end-of-life - [Rootly vs Jira Service Management](https://rootly.com/alternatives/rootly-vs-jira-service-management): Running incidents vs tracking them as tickets ## Documentation - [Documentation Hub](https://docs.rootly.com/): Main documentation portal - [API Reference](https://docs.rootly.com/api-reference/overview): REST API documentation - [Official SDKs](https://docs.rootly.com/api-reference/sdks): Python, Go, Ruby, and JavaScript SDKs - [API Keys](https://docs.rootly.com/integrations/api): Authentication and API key management - [Terraform Provider](https://registry.terraform.io/providers/rootlyhq/rootly/latest/docs): Infrastructure as code for Rootly configuration - [MCP Server](https://docs.rootly.com/integrations/mcp-server): IDE agent integration for Cursor, Windsurf, and Claude - [Slack Integration](https://docs.rootly.com/integrating-with-slack): Slack setup and configuration - [Microsoft Teams Integration](https://docs.rootly.com/integrations/microsoft-teams): Teams setup and configuration - [Status Pages Configuration](https://docs.rootly.com/configuration/status-pages): Setting up and configuring status pages ## Integrations - [Integrations Hub](https://rootly.com/integrations): Browse all available integrations Key integrations include: Slack, Microsoft Teams, Jira, Linear, Confluence, Datadog, Sentry, Grafana, Prometheus, Honeycomb, ServiceNow, GitHub, Backstage, and Cortex. ## Security & Trust - [Security Overview](https://rootly.com/security): Security program, certifications, and data protection - [Trust Portal](https://security.rootly.com/): Security certifications, compliance, and policies - [System Status](https://status.rootly.com/): Real-time platform status ## Customer Stories - [Customers Directory](https://rootly.com/customers): All customer stories - [Achievers](https://rootly.com/customers/achievers) - [Capa](https://rootly.com/customers/capa) - [Clay](https://rootly.com/customers/clay) - [Cora](https://rootly.com/customers/cora) - [CTSO Central](https://rootly.com/customers/ctso-central) - [Grail](https://rootly.com/customers/grail) - [KnowBe4](https://rootly.com/customers/knowbe4) - [Lucidworks](https://rootly.com/customers/lucidworks) - [Momentum](https://rootly.com/customers/momentum) - [Motive](https://rootly.com/customers/motive) - [Poll Everywhere](https://rootly.com/customers/poll-everywhere) - [Reactiv](https://rootly.com/customers/reactiv) - [Replit](https://rootly.com/customers/replit) - [Roller](https://rootly.com/customers/roller) - [SpotDraft](https://rootly.com/customers/spotdraft) - [Upstart](https://rootly.com/customers/upstart) - [Wealthsimple](https://rootly.com/customers/wealthsimple) - [Webflow](https://rootly.com/customers/webflow) ## Optional - [Pricing](https://rootly.com/pricing): Pricing plans and options - [Enterprise](https://rootly.com/enterprise): Rootly for large engineering organizations - [Startups](https://rootly.com/startups): Rootly for startups - [Home](https://rootly.com): Main website ## FAQ ### Platform What does Rootly include? One platform covering the full incident lifecycle: on-call/paging, incident response in Slack, Google Chat or Microsoft Teams, AI SRE investigation, retrospectives, and status pages - with a service catalog, workflows, and automations. Every major feature is included on every plan, with no separate add-ons. Is Rootly just for Slack? No. The full incident lifecycle runs natively in both Slack and Microsoft Teams - declaration, coordination, comms, AI assistance, and retrospectives - without switching to a separate interface. Is Rootly a monitoring tool? No. Rootly integrates with monitoring tools (Datadog, Sentry, Grafana, Prometheus, Honeycomb, and others) and focuses on incident management: on-call, response, learning, and status pages. ### On-Call How does Rootly decide who gets paged? Rootly reads the alert's routing target - service, team, or escalation policy - then uses live schedules and escalation rules to select the responder, escalating to the next level until someone acknowledges. It can page teams, users, schedules, and Slack channels directly, with no workaround "services" required. What channels can Rootly page through? Voice calls, SMS, push notifications, Slack, and email - chosen by urgency and user preference, with automatic retries, fallbacks, and Do Not Disturb override for critical alerts. Can Rootly handle complex schedules? Yes - multi-person rotations, layered primary/secondary coverage, business-hours-only and time-zone-aware schedules, overrides, shadow rotations, and one-click coverage requests. Slack user groups update automatically. What is live call routing, and what are heartbeats? Live call routing turns a phone call into a page (live connection, voicemail-to-page, IVR trees, failover). Heartbeats detect silent failures: if a system stops checking in within its expected interval, Rootly alerts the right team and auto-resolves on a recovery ping. How reliable is Rootly's paging? Rootly runs on a multi-region redundant architecture with a 99.99% uptime SLA and multi-channel fallbacks, so a critical alert lands even if one channel or provider is degraded. ### Incident Response What is Rootly Incident Response? Teams run the entire incident inside Slack or Microsoft Teams - declaring, assigning roles, coordinating the fix, updating stakeholders, and capturing the timeline. Each incident inherits context from on-call, the service catalog, and past incidents. What can Rootly's in-channel AI do? Mention @Rootly to ask questions in plain language and take action as your user, within your permissions - paging, changing severity/status, managing action items, and drafting comms. It also provides catch-up summaries, incident summaries, and a meeting scribe for bridge calls, and confirms destructive actions before running them. How does Rootly keep stakeholders updated? Rootly automates stakeholder, leadership, and customer communication and keeps the status page current as the incident changes state, so responders stay focused on the fix. Can I manage incident response programmatically? Yes. Rootly offers a full REST API, official SDKs (Python, Go, Ruby, JavaScript), a Terraform provider for config-as-code, and an MCP server for IDE agents like Cursor, Windsurf, and Claude. ### AI SRE What is an AI SRE? An AI system that performs the investigation, triage, and coordination tasks traditionally handled by a site reliability engineer during an incident - monitoring alerts, running root cause analysis, and assisting resolution alongside human engineers, not replacing them. What is Rootly AI SRE and how does its root cause analysis work? Rootly AI SRE activates the moment an alert fires and runs parallel hypothesis checks across alerts, telemetry, recent deployments, and past incidents, producing a ranked, evidence-backed theory of what went wrong. Each finding includes a confidence score and a visible reasoning chain. What does "human in the loop" mean in practice? Rootly AI investigates, surfaces findings, suggests fixes, and drafts updates - but every change requires explicit human sign-off before execution. It never auto-remediates on its own. How quickly does Rootly AI SRE deliver value? Teams typically see it surface its first root cause finding within the first incident after setup, with no separate onboarding because it's built into the existing platform. ### Retrospectives What's the difference between a postmortem and a retrospective? They're often used interchangeably, but "postmortem" emphasizes documenting what happened, while "retrospective" emphasizes learning and improving the system and process through tracked follow-up actions. Rootly uses blameless retrospectives. What parts of a retro can AI safely automate? Assembling the timeline (from alerts, chat, commits/deploys, and status updates), summarizing long threads, drafting sections, and generating initial action items - all editable so humans validate the facts and final commitments. How do you run blameless retros without losing accountability? Focus on what in the system made the outcome likely - gaps in alerts, runbooks, ownership, or change practices - then assign clear owners and due dates. Accountability is about follow-through, not blame. Do Rootly retrospectives work with our existing tools? Yes. Action items push to Jira or Linear as synced subtasks, and retro docs export to Confluence, Notion, Google Docs, and SharePoint, so the retro lives where your org documents knowledge. ### Status Pages Why use a status page, and how does Rootly's reduce support tickets? A status page is a single source of truth during downtime - what's impacted, what you're doing, and when the next update lands. When customers can self-serve accurate updates, they stop opening duplicate "is it down?" tickets, and Rootly keeps status updates aligned with the incident workflow rather than a separate tool. Can we control who sees what, and can customers subscribe? Yes. Rootly supports public, private, and internal pages (with authenticated/SSO access for private pages) and subscriptions so customers and stakeholders opt in to incident and maintenance updates. Pages are fully branded on your own domain. ### Security & Data Does Rootly train on my incident data? No. Rootly enforces zero third-party model training. Your incident data is used exclusively for your organization - never pooled with other customers, never used to train general models. Sensitive data (links, emails, passwords) is redacted before being sent to AI providers, and teams can bring their own LLM keys. Where is incident data stored, and who can access it? Access mirrors your org's permissions (SSO/RBAC) and is auditable - only the right people can view or edit sensitive incident artifacts, and AI access respects incident privacy settings. ### Comparisons & Migration Does Rootly replace PagerDuty, and is it more affordable? Yes. PagerDuty notifies a person when something breaks; Rootly handles the page and everything after - coordination, resolution, communication, and learning - in one platform. PagerDuty gates core capabilities behind add-ons (AIOps, Advance, Status Pages); Rootly includes them on every plan, typically at about half the total cost, with a free tier for non-pageable stakeholders. How is Rootly different from incident.io or Resolve AI? Rootly's AI SRE is built into a complete incident management platform rather than layered on top of one, so it has full context across services, ownership, on-call schedules, and incident history before investigating. It shows its reasoning at every step, enforces zero third-party training, and never auto-remediates without human sign-off. When is Opsgenie shutting down, and what are the options? Atlassian closed new Opsgenie sales in June 2025 and set end-of-life for April 2027, after which the platform becomes inaccessible and unexported data is deleted. Rootly's on-call concepts closely mirror Opsgenie, schedules and escalation policies import directly, and you can keep using Jira, Confluence, and other Atlassian tools. Can Jira Service Management do incident management? JSM logs incidents as tickets and, since absorbing Opsgenie, includes basic on-call. But ownership-based paging, live response coordination, automated comms, root-cause investigation, and retrospectives are manual in JSM. Rootly runs each natively; most teams keep JSM for ITSM/service-desk and use Rootly to run incidents. Does Rootly help with migration, and how long does it take? Yes. Rootly runs a read-only audit of your current setup, delivers a findings report, and executes the migration with a tailored plan. Most teams are live within a week (large enterprise tenants 6 weeks to 3 months), and Rootly will buy out your remaining PagerDuty contract - you don't start paying until it ends.