Key Intelligence Insight
incident.io is not a better PagerDuty. It is building the category that makes PagerDuty irrelevant.
Four and a half years in, the company has outgrown the "incident management startup" frame. It has processed over half a million real incidents, closed a $62 million Series B at a $400 million valuation, and added OpenAI, Netflix, Etsy, and Airbnb to a customer roster that now exceeds 600 organizations. By the founders' own analysis of public revenue figures, it is growing faster than both PagerDuty and Opsgenie -- legacy juggernauts worth billions with sales forces and procurement relationships incident.io does not yet have.
The strategic move for 2026 is bigger than the funding round: incident.io is exiting "pure play incident management" entirely and defining a new category it calls holistic reliability -- one that catches failures upstream in the development process, filters alert noise with AI before it reaches engineers, and resolves what slips through faster than any human team could. The AI SRE product demonstrated this live, unscripted, on stage: it investigated a deliberately broken production environment, drafted the fix, and wrote the post-mortem.
Founding Story
incident.io was founded in 2021 by three co-founders -- Stephen Whitworth (CEO), Pete Hamilton, and Chris Evans -- who built the company out of direct experience with the dysfunction of legacy incident tooling. The founding logic was straightforward: engineers were forced to context-switch between fragmented paging systems, web consoles, and communication tools at the worst possible moment, when production was on fire.
The early insight was architectural. Rather than build another standalone tool that required engineers to leave their workflow, incident.io built natively inside Slack and Microsoft Teams -- where engineering teams already lived. This was not a UX preference. The mechanism: by embedding incident response inside the communication layer, the product eliminated the coordination overhead that added minutes to every incident and hours to every post-mortem.
The founders relocated between London, New York, and San Francisco over the company's first four years, moving physical operations to stay close to the enterprise market. Even as headcount more than doubled -- from 68 to roughly 165 employees in a single year -- the founders personally dedicated 30% to 40% of their time to interviewing candidates, deliberately protecting culture and hiring quality over speed.
The company is incorporated as Pineapple Technology Ltd. and operates globally out of London and San Francisco.
Product
incident.io is an all-in-one platform for on-call scheduling, incident response, AI-driven resolution, and customer-facing status pages. The product surface area has expanded aggressively since 2024, driven by a team that more than doubled in size and a Series B that explicitly funded multi-product expansion.
On-call launched in March 2024 as a direct displacement product targeting PagerDuty and Opsgenie. It was built by an internal team of at most ten people and grew to compete with billion-dollar incumbents on features -- flexible scheduling, shadow rotations, holiday calendars, alert routing and grouping, a mobile app, and cover requests. By April 2025, nearly two-thirds of the customer base had migrated onto it.
Response is the original core product: a chat-native incident coordination layer running end-to-end response workflows inside Slack and Microsoft Teams. Role assignment, automated escalation, custom incident types, and real-time communication all run without requiring engineers to leave the tool they are already in.
AI SRE is the company's sharpest forward-looking bet. It is an autonomous agent that investigates alerts, correlates telemetry and code changes, identifies root causes, drafts pull requests to fix broken production environments, and generates post-mortems. The founders proved it was not vaporware by running a 45-minute live, unscripted demo at a major conference -- deliberately breaking their production environment and letting the AI resolve it on stage. It did.
Status Pages are automated customer-facing communication hubs that reduce inbound support tickets during active outages. OpenAI -- serving an estimated 700 million active users -- runs on incident.io's status page product.
Post-mortems, Insights, Catalog, and Workflows complete the platform. AI-native post-mortems launched in early 2026. Catalog maps service ownership and infrastructure dependencies to power precise incident routing. Insights surfaces MTTR trends, workload metrics, and reliability patterns across the organization.
The 2026 product roadmap extends the platform upstream: AI applied to pull requests before deployment, to catch incidents before they happen, and AI applied to alert streams to reduce noise before it reaches engineers. The product is moving from reactive to preventive.
Market, Competition & Business Performance
Market
The incident management and IT operations market sits inside the broader DevOps and site reliability engineering tooling category -- a space defined by the structural reality that software systems fail, and the cost of downtime is measurable and high. The core buyer is the engineering organization, specifically SRE, DevOps, and platform engineering teams inside companies that run software in production at scale.
The incumbents -- PagerDuty ($400M+ ARR, publicly traded) and Opsgenie (acquired by Atlassian) -- built their market positions on a pre-Slack, web-console-centric model. That model has a ceiling. The mechanism: as engineering teams moved to chat-native workflows, the friction of toggling to a separate incident console became a compounding drag on adoption and satisfaction. Incident.io was built to fit inside the workflow, not alongside it.
The company's stated 2026 positioning -- holistic reliability, not incident management -- represents a market expansion move. Upstream code review, alert noise reduction, and accelerated resolution are three distinct workflows that engineering teams currently manage with separate tools or do not manage at all. Collapsing them into a single platform increases total addressable surface area and creates switching costs that a point solution cannot replicate.
Competition
In paging and on-call, incident.io's founders identify only two players currently larger: PagerDuty and Opsgenie. They are growing faster than both, by their own analysis of public revenue data. The competitive dynamics favor the challenger: PagerDuty and Atlassian carry the organizational weight of public companies defending existing revenue, while incident.io is building new product surface area with a team less than a tenth the size.
Direct competitors in the incident management layer include Rootly, FireHydrant, and Better Stack -- all building chat-native alternatives to legacy paging. Squadcast competes specifically on on-call. None has matched incident.io's breadth: the combination of on-call, response, AI SRE, status pages, and post-mortems in a single integrated platform is, as of early 2026, incident.io's structural advantage.
The AI SRE product creates a category gap that is harder to close. Building an agent that reliably investigates production failures, identifies root causes, and drafts code fixes requires deep incident data -- the kind that accumulates from processing half a million real incidents. Competitors without that data foundation cannot replicate the training surface.
The Pragmatic Engineer -- one of the most influential publications among senior software engineers -- listed incident.io alongside PagerDuty and Opsgenie as a leading incident management choice in a poll of its readership. That is a distribution advantage that compounds: the buyer population is engineers, and engineers read the Pragmatic Engineer.
Business Model
incident.io operates a tiered SaaS model with a free Basic tier and paid Team ($19/user/month), Pro ($25/user/month), and Enterprise (custom) plans. On-call is available as a standalone product at $20/user/month, or bundled with the core plans at $10-20/user/month depending on tier. The model is designed to land at the team level and expand across the organization.
The go-to-market motion is high-touch enterprise, not pure product-led growth. The mechanism: customers in this category want active guidance on deployment and workflow design, not just a self-serve onboarding flow. The sales motion matches the buying process, and the buying process involves SRE leads and engineering directors with defined budgets.
Out-of-home marketing in London -- 400 bus stops and a digital roundabout takeover in the Old Street startup hub -- drove measurable recruiting ROI. Engineers cycling past the same ad seven times built brand recognition in the talent pool the company was hiring from simultaneously. The brand philosophy is deliberate: generate an emotion, make people smile. The billboards read "resolve incidents while you sleep" and "Ship page wake repeat."
Traction
The capital position is defined. incident.io closed a $62 million Series B in April 2025 at a $400 million valuation, led by Insight Partners with participation from Index Ventures and Point Nine Capital, bringing total funding above $96 million. The round was not a lifeline -- it was an accelerant. The company had already reached the scale necessary to justify it.
The customer roster now exceeds 600 organizations, spanning Netflix, OpenAI, Etsy, Airbnb, Intercom, Skyscanner, Square, Vanta, Linear, and Zendesk. OpenAI's status page runs on the platform, serving an estimated 700 million active users -- a signal of both technical trust and brand credibility at the highest possible tier of the market.
Operationally, the platform has processed over half a million real incidents. Volume in 2025 alone exceeded every prior year combined. Two-thirds of the customer base had migrated onto the On-call product within roughly a year of its launch -- a product adoption rate that implies pull, not push. The team behind that growth went from 68 to 165 employees in a single year, with the product development organization more than doubling in size since January 2025.
By the founders' own analysis of public filings, revenue growth is outpacing both PagerDuty and Opsgenie. That is the structural signal: a challenger with a fraction of the headcount, no legacy sales motion to protect, and a product that fits where engineers actually work is compounding faster than incumbents worth multiples of its valuation.
The company describes itself as "predictable and unkillable" at four and a half years -- sustained by customer revenue, not burn. That financial foundation gives the team the room to take the product risks the holistic reliability bet requires.