Announcing o11's backing from Y Combinator.

# AI for PagerDuty

## AI that drives the incident, not just the page.

- Page on-call with the right escalation policy.
- Build incident timelines and draft postmortems in place.

## PagerDuty

Search incidents, services, users…

### Trigger Incident

All open Mine 3Triggered 2Acknowledged 1Recently resolved Reports

Status: Open  
Priority: All  
Service: All  
Team: All  
Add filter

Group by: None

- **P1** Database failover triggered — replica lag > 5s  
  Service: Platform · Database  
  High urgency · 3m active  
  JL J. Lim  
  Triggered  
- **P1** EU API gateway 5xx spike (15% error rate)  
  Service: Web  
  High urgency · 8m active  
  MC M. Chen  
  Triggered  
- **P2** High latency on api-east (p95 > 800ms)  
  Service: Platform  
  High urgency · 24m active  
  MC M. Chen  
  Acknowledged  
- **P3** SSL cert expiring in 7 days — billing-prod  
  Service: Billing  
  Low urgency · 1h active  
  LP L. Park  
  Acknowledged  
- **P3** Pod restart loop on web-fe  
  Service: Web  
  High urgency · 12m  
  MC M. Chen  
  Resolved  
- **P3** Datadog monitor alert — disk usage  
  Service: Platform  
  Low urgency · 2h  
  JL J. Lim  
  Resolved

## Acknowledge the 'Database failover' incident

Acknowledge incident #1 and page J. Lim as escalation.

## o11 for PagerDuty: an AI agent layer for incident response

o11 is an AI execution layer that runs inside PagerDuty. The agent pages the right on-call rotation, builds the incident timeline as the response unfolds, and drafts the postmortem with the actions, comms, and contributing factors already in place — without an incident commander reconstructing what happened from Slack scrollback two days later.

If you have searched for **AI for PagerDuty**, a **PagerDuty AI agent**, or a **PagerDuty AIOps alternative** that drives the response itself, the difference is whether the AI groups alerts or runs the incident.

## What teams use o11 for in PagerDuty

- **On-call paging.** Choose the right escalation policy, page the correct service, and avoid waking the wrong rotation when an alert spans multiple services and dependencies.
- **Incident timeline.** Capture pages, status updates, customer comms, and remediation steps on the incident as they happen, so the timeline is real-time, not reconstructed.
- **Postmortem drafting.** Pull the timeline, contributing factors, follow-up actions, and customer-impact summary into a draft that needs editing instead of writing.
- **Cross-system handoffs.** File ServiceNow or JSM incidents, post status to Slack or Microsoft Teams, link the GitHub revert PR, and update the Statuspage entry without juggling tabs in the middle of a sev1.

## Why o11 differs from PagerDuty AIOps and incident-native AI

PagerDuty AIOps and most incident-native AI features stop at noise reduction and similar-incident matching. They reduce alert volume and surface context, but the response itself is still driven manually by the incident commander. o11 is built to drive the response. The chat is the control surface, PagerDuty is where the page, the incident updates, and the postmortem record actually land.

## Built for teams that live across systems

PagerDuty rarely operates in isolation during a real incident. SREs pair it with Datadog or Splunk for telemetry, Slack or Microsoft Teams for the war room, ServiceNow or JSM for the incident record, GitHub for reverts, and Statuspage for customer comms. o11 is positioned to act across all of them. A single page can become a PagerDuty incident, a Slack war room, a Datadog dashboard pin, a GitHub revert, and a customer-facing status update without the IC re-keying the same context five times.

## Where PagerDuty teams typically start with o11

- **Incident commanders** with timeline capture and comms.
- **SREs and on-call engineers** with paging accuracy and remediation steps.
- **Engineering managers** with postmortem drafts and follow-up tracking.
- **Platform leadership** with reliability metrics and recurring root cause patterns.

## How o11 respects PagerDuty permissions

The agent operates with the user’s own PagerDuty account. Team membership, role-based access, and service ownership apply exactly the way they do for that user in the UI. Nothing runs as a global admin token, nothing bypasses escalation policies. That is what makes o11 deployable in reliability orgs that cannot trust a tool that pages or resolves outside the platform’s permission model.

## FAQ

### How is this different from PagerDuty AIOps?

AIOps groups alerts. o11 runs the incident, drives comms, and ships the postmortem.

### Who is it for?

Incident commanders, SREs, and on-call engineers.

## Ready to see o11 inside PagerDuty?

[Book a demo](/content/demo/index.html)