incident.io
Incident response run from Slack or Microsoft Teams, with its own on-call paging, status pages and an AI agent that investigates, sold as one SaaS priced per user.
- What it is
- Incident management,On-call
- Type
- Commercial product
- Made by
- incident.io
- License
- Proprietary
- Facts checked
- 24 October 2026
What it is
In incident.io an incident starts with /inc in Slack, a message shortcut, a form at inc.new or an alert. Declaring one creates a dedicated Slack channel, a video call, a linked ticket in Jira or Linear and an announcement in #incidents; Microsoft Teams works the same way. Workflows then run your process: assign roles such as incident lead, post reminders for updates, page another team or create follow-ups. After resolution the tool drafts a post-mortem from the timeline and tracks the follow-up actions, and dashboards show where time and workload went. A catalog of your services, teams and customers sits underneath, so an alert or incident can be tied to an owner automatically.
On-call, added in 2024, replaces a separate paging tool. Over 40 built-in alert sources, including Datadog, CloudWatch, Grafana, Prometheus Alertmanager, Sentry and PagerDuty, plus HTTP and email sources, feed alert routes that decide whether to page someone, open an incident or attach to an existing one. Schedules support several rotas, follow-the-sun coverage and shadowing; escalation paths keep notifying people by app push, SMS, phone call, Slack or email until someone acknowledges. Status pages (public, per-customer with login, and internal) update as the incident progresses. The AI layer, sold on higher plans, transcribes calls, writes summaries and runs Investigations that look at recent code changes and telemetry and post likely causes in the incident channel.
Pricing is per user. The free Basic plan has single-team on-call, one status page, one workflow and two integrations. Team costs $15 per user a month billed yearly ($19 monthly), plus $10 per on-call user; Pro is $25 plus $20 for on-call and adds the AI features, private incidents and custom dashboards. On-call alone is $20 per user.
Why teams pick it
- Response, paging, status pages and post-mortems in one product, so an alert, the incident it becomes and the customer update share one record
- Lives where engineers already talk: the incident channel, roles, updates and follow-ups are handled from Slack or Teams without opening another app
- Over 40 built-in alert sources and importers for PagerDuty and Opsgenie schedules and escalation policies make a move from those tools mostly mechanical
- A free plan that covers a single team’s incidents, on-call schedule and public status page
Watch out for
- Proprietary SaaS with no self-hosted version, and running incidents from chat needs Slack or Microsoft Teams
- Costs add up per person: on-call is a separate per-user add-on, and the AI features need Pro, with root cause analysis and the autonomous agent sold as extra add-ons
- The free plan stops at one workflow, two integrations, one custom field and one schedule, and has no API or webhooks
- Status page configuration can’t be managed with Terraform or code; the API covers only status page incidents and maintenance windows
Alternatives
What all incident management have in common →Compare side by side →
How it fits with other technologies
Send an alert from any tool to an HTTP alert source · bash
# The alert source ID and token come from the source you create in the dashboard.
# Alert routes then decide whether this pages someone, opens an incident, or both.
curl -X POST "https://api.incident.io/v2/alert_events/http/$ALERT_SOURCE_ID" \
-H "Authorization: Bearer $ALERT_SOURCE_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"title": "Checkout API: p99 latency over 2 s",
"status": "firing",
"deduplication_key": "checkout-latency",
"description": "p99 has been above 2 s for 5 minutes",
"metadata": { "service": "checkout-api", "team": ["payments"] }
}'
# Send the same key with "status": "resolved" to close the alert.See it in a real stack
No architecture uses incident.io yet. Drop it into the playground and wire it up yourself.Open playground →Where it came from2020–2025
At the UK bank Monzo, Chris Evans, then head of platform and reliability, wrote an incident tool because paging products like PagerDuty woke people up but didn’t help them run the incident. The first version, built over two evenings, was a Slack slash command that posted an announcement; he later rewrote it in Python and Django with stored incident state and a timeline page, and released it as open source. Pete Hamilton found it while looking for a tool for GoCardless, and Stephen Whitworth, who had co-founded the fraud-prevention company Ravelin, saw it at Monzo.
In November 2020 the three began turning it into a product, working early mornings and evenings while still at Monzo. They saw that companies either ran incidents by hand or kept rebuilding the same internal tool. The first product ran incident management entirely in Slack: announce the incident, open a channel, assign roles, update status pages, pull in specialists through PagerDuty and export follow-ups to Jira. In July 2022 they announced a $28.7 million Series A led by Index Ventures, on top of a $5.5 million seed.
Status pages came next, then in March 2024 incident.io On-call, built because customers kept naming it as their most wanted feature. When Atlassian began winding down Opsgenie, many customers moved their paging over; by April 2025 nearly two-thirds of customers were on On-call, the platform had handled more than 250,000 incidents, and the company raised a $62 million Series B led by Insight Partners to build AI agents that investigate incidents.
Why it’s built this way
- Run the incident inside Slack instead of in a separate web app
- Responders were already coordinating in chat. A slash command that opens a channel, announces the incident and records the timeline fits that habit instead of asking people to switch tools mid-outage.
- Build its own on-call paging instead of relying on PagerDuty
- Customers kept asking for it, and owning the alert-to-incident path lets one tool route alerts, page people, open the incident and update the status page without glue between vendors.
- A catalog of services, teams and customers under everything
- Alerts arrive with only a name or a tag. Looking them up in a catalog lets routes, escalations and workflows find the owning team and the affected customers automatically.
Timeline
- 2020
Evans, Hamilton and Whitworth start turning Evans’s Monzo incident tool into a product in November
- 2022
$28.7M Series A led by Index Ventures, on top of a $5.5M seed
- 2024
incident.io On-call launches in March, after Response and Status Pages
- 2025
$62M Series B led by Insight Partners; more than 250,000 incidents handled
- incident.io blog: The founder’s story, a trip down memory lane (podcast transcript, Dec 2022)
- TechCrunch: Incident.io looks to beef up its Slack-based incident response platform with $28.7M (Jul 2022)
- incident.io blog: Announcing On-call (Mar 2024)
- Index Ventures: incident.io raises $62M to build AI agents that resolve incidents with you (Apr 2025)
Sources10 · facts checked 24 October 2026
- incident.io homepage (products: Investigations, On-call, Response, Status Pages)
- incident.io docs: What’s incident.io? (products and platform)
- incident.io docs: Declaring incidents (/inc, inc.new, what happens next)
- incident.io docs: What alert sources are supported?
- incident.io docs: Introduction to status pages (public, customer, internal)
- incident.io docs: Can I manage status pages using Terraform or automation?
- incident.io API reference: Create alert event (HTTP source)
- incident.io docs: index (PagerDuty and Opsgenie importers, escalation paths)
- incident.io blog: Announcing On-call (alert routes, schedules, escalation paths, notifications)
- incident.io pricing (checked 24 October 2026)