PagerDuty
AI-driven incident management and on-call scheduling
PagerDuty owns the on-call scheduling and incident response workflow with the deepest enterprise integrations, making it the default operational backbone for Fortune 500 engineering teams.
SWOT Analysis
- Market-leading on-call scheduling and escalation policy engine trusted by 15,000+ customers
- Ops Cloud platform extends from incident response to AIOps event intelligence
- Deep integration ecosystem with 700+ native integrations including every major monitoring tool
- Strong enterprise contracts and NRR above 110% in enterprise segment
- PagerDuty AI (AIOps) reduces noise and surfaces actionable signals from millions of events
- Expand automation pillar: autonomous incident resolution reduces MTTR with AI-driven playbooks
- Customer service operations: extend incident management to customer-facing SLAs
- Agentic Ops integration: pair PagerDuty signals with AI agents for auto-remediation workflows
- Federal and regulated-sector expansion leveraging FedRAMP authorization
- ARR flat at $496M in Q1 FY27; new CEO John DiLullo takes over as ServiceNow rivalry intensifies
- Per-user pricing adds up quickly for large on-call rotations
- Incident.io, FireHydrant targeting lower cost-point for startup and growth-stage teams
- AIOps features perceived as add-on rather than core capability by some buyers
- ServiceNow embedding incident management directly into ITSM workflows, reducing standalone need
- Datadog Incidents competing by bundling incident management into the observability stack
- Slack-native competitors (Incident.io, Rootly) winning teams who live in Slack
- Economic pressure driving customers to consolidate on platform vendors over point solutions
User Sentiment
Synthesized from G2, Gartner Peer Insights, and analyst review data.
- Best-in-class on-call scheduling flexibility with escalation policies and schedule overrides
- Mobile app reliability: alerts arrive consistently with high priority even in DND mode
- Automated runbooks reduce mean time to resolution for common incident types
- Status page integration keeps stakeholders informed without manual updates
- Per-seat pricing becomes expensive for organizations with large on-call pools
- AIOps event intelligence requires significant tuning time before delivering value
- UI can feel heavy for teams that only need simple alerting and paging
Pricing & TCO
Analyst-synthesized pricing signals — directional only, contact vendor for current terms.
Starting Price
$21/user/month (Professional)
Typical ACV (Mid-Enterprise)
$20K–$200K
Market Segments
Deployment
Key Cost Drivers
- Number of full users versus stakeholder (view-only) users
- Tier selection: Professional vs Business vs Enterprise Digital Operations
- Add-on: AIOps, Runbook Automation, Process Automation
Per-seat pricing is predictable; AIOps and automation add-ons are where enterprise budgets expand.
Full comparisonCustomer Profile
Typical segments
Typical buyer
VP Engineering, Director of SRE, or Head of IT Operations
- 1On-call scheduling and escalation for 24/7 production engineering teams
- 2Incident response orchestration from detection through postmortem
- 3AIOps noise reduction correlating alerts from multiple monitoring tools into single incidents
Future Focus Areas
PagerDuty Copilot: AI agent that drafts incident timelines, suggests responders, and runs remediation steps
Automation Actions library for self-healing infrastructure triggered by PagerDuty incidents
Customer service incident management bridging IT ops and CX team response workflows
Deep integration with AI agent platforms (ServiceNow AI, Moveworks) for autonomous resolution