Monitoring software could detect a fault and send an email, but someone still had to route the alert to the person on call and find a backup when that person did not respond. The founder’s account identifies tools such as Nagios and SolarWinds already in use at entry. The gap was the human response after detection. PD2
PagerDuty
PagerDuty solved the handoff from a monitoring alert to a person who would act
What shaped PagerDuty
- 1 · 2009 to 2010Attach to monitoring that already worksPagerDuty accepted alerts through an API or email, so teams could keep Nagios, SolarWinds and other monitoring tools. PD2Drop-In Adoption
- 2 · 2010 to 2019Coordinate the wider incident, beyond the pageThe company broadened the product into incident coordination and response. PD4 PD5
- 3 · 2019 to 2026A useful installed position reached a growth limitFor fiscal 2026 PagerDuty reported $492.5 million of revenue, up 5.4%, and $5.8 million of GAAP operating income. PD6
Arena: Market Conditions Before PagerDuty
How each step happened
Step 1 of 3 · 2009 to 2010
Attach to monitoring that already works
PagerDuty accepted alerts through an API or email, so teams could keep Nagios, SolarWinds and other monitoring tools. It converted an alert into an incident, contacted the on-call person and escalated to backups when needed. Co-founder Alex Solomon’s account identifies AdMob and Rutgers among early customers. The paid service launched in December 2009; he recalls adoption increasing after charging began. PD2
The offer removed a specific coordination task without requiring replacement of the system that detected the problem. That narrowed the initial adoption decision. Solomon attributed the response to charging partly to customers’ confidence that a critical service had a sustainable business behind it.
Rivals A team could maintain scripts, schedules and escalation procedures itself. PagerDuty made the handoff a maintained service while preserving the monitoring investment. PD2
Step 2 of 3 · 2010 to 2019
Coordinate the wider incident, beyond the page
The company broadened the product into incident coordination and response. Its IPO filing described hundreds of integrations and customers using the service across operational workflows. The filing reported 11,212 customers and 140% dollar-based net retention at January 2019; fiscal 2019 revenue was $117.8 million. Alex Clayton’s IPO analysis emphasized the contribution of expansion within existing customers. PD4 PD5
Once a team relied on the service to summon a responder, the next job was bringing in additional people and coordinating what happened next. Broader incident response extended an existing buying relationship. The IPO-era retention figures show how strongly spending within that base was expanding.
Rivals Another incident tool or a monitoring suite could supply overlapping functions. Coordination across tools gave buyers a reason to consider a separate subscription. PD4
Step 3 of 3 · 2019 to 2026
A useful installed position reached a growth limit
For fiscal 2026 PagerDuty reported $492.5 million of revenue, up 5.4%, and $5.8 million of GAAP operating income. January 2026 ARR grew about 1%, to roughly $499 million. Dollar-based net retention was 98%, down from 106% a year earlier. PD6
The later retention figure changes the expansion story. Existing customers in the measured cohort collectively ended with slightly less recurring revenue after expansion, contraction and churn. PagerDuty still had a substantial paying base, but that base no longer supplied net growth on this measure. The operational role had endured longer than the earlier pace of account expansion.
Rivals The paying base remained substantial as spending within the existing-account cohort contracted. Early expansion rates had ceased to describe the current business. PD6
Key dates
Sources
Oldest first.
- PD5 PagerDuty IPO S-1 breakdown. Participant or analytical account
- PD4 IPO registration statement, amendment. Filing
- PD6 Fourth-quarter and full-year fiscal 2026 financial results. Participant or analytical account
- PD90 PagerDuty Share statistics. Market data
- PD91 PagerDuty Daily price history. Market data
- PD2 EnterpriseReady 30: On-call management with Alex Solomon. Participant or analytical account