How PagerDuty Quietly Built a Moat Wall Street Missed

In the world of tech, a 'moat' is a firm's defense against competitors. While some are obvious, others are practically invisible. PagerDuty, a name synonymous with waking up engineers at 2 a.m., has built one of the latter kind.

More Than Just a Digital Beeper

First, let's clear up a common misconception. PagerDuty isn't just a glorified pager system. It's a comprehensive platform for digital operations management. When a company's website goes down, a critical feature breaks, or a server crashes, PagerDuty is the

central nervous system that detects the signal, filters out the noise, and routes the alert to the exact person or team needed to fix it. It manages on-call schedules, automates escalations, and provides a centralized place for teams to coordinate during a crisis. In an economy where downtime can cost millions per minute, its role is not just to alert, but to orchestrate a rapid response and minimize business impact.

The Moat's First Layer: Extreme Stickiness

The first, and perhaps strongest, part of PagerDuty's moat is its high switching cost. Once a company embeds PagerDuty into its operational DNA, ripping it out is a nightmare. It's not like swapping one email provider for another. Engineers build their entire incident response workflows around it. Teams configure complex on-call schedules, escalation policies, and automated runbooks. Changing platforms means retraining the entire technical organization and rebuilding years of institutional knowledge codified in the system. The potential for a botched migration, which could lead to missed critical alerts, makes most companies think twice. Evaluating the cost of an incident versus the cost of switching often leads to sticking with the incumbent.

The Moat's Second Layer: The Integration Ecosystem

The second component of the moat is a powerful network effect built on integrations. PagerDuty connects with over 750 other software tools, from monitoring platforms like Datadog and Splunk to communication hubs like Slack and Microsoft Teams. This massive ecosystem makes PagerDuty the central hub for operational data. It doesn't need to be the best at everything, it just needs to connect to everything. This creates a classic 'platform' advantage; the more tools that integrate with PagerDuty, the more valuable it becomes to users, which in turn encourages even more toolmakers to build integrations. This interoperability makes it the de facto standard for incident response orchestration.

So Why Has Wall Street Missed It?

If the moat is so strong, why the disconnect with market perception? A few factors are at play. First, PagerDuty's growth has slowed, which spooks investors focused on hyper-growth SaaS companies. With net revenue retention hovering around 100%, it signals that existing customers aren't dramatically expanding their spending. Second, the market is crowded, with giant platforms like ServiceNow and observability specialists like Datadog bundling their own competing on-call tools, creating the perception that PagerDuty is being squeezed. Finally, its value is in prevention and mitigation—a quieter, less glamorous story than explosive user growth. It's a profitable, cash-generating business, but in a market obsessed with speed, its steady, defensive nature is often miscategorized as stagnation.