|
By Article
Schedules are a core part of any on-call system. In ours, they define who to page and when. But people use them in lots of other ways too: checking their next shift, asking for cover while at the gym, keeping a Slack user group up to date, or updating a Linear triage responsibility. For many of our customers, they’re one of the main ways they interact with our product, and as they’re such a foundational part of On-call, it’s very important they work well.
|
By Article
Everyone is using AI to help with post-mortems now. The pitch is obvious: post-mortems are time-consuming, the blank page is brutal, and AI is very good at producing structured, confident-sounding documents quickly. We're not here to push back on that. We've built AI into our own post-mortem experience, pulling your Slack thread, timeline, PRs, and custom fields together and giving your team a meaningful starting point in seconds. We think that's genuinely valuable, and the teams using it agree.
|
By Article
We've been building the broader incident.io platform for several years now, and one thing we've learned is that UX matters more here than almost anywhere else. When an incident fires, there's no room for poorly designed interfaces or fumbling through features you haven't touched in a while. The product has to be ergonomic: easy to pick up, easy to navigate, with the right things at your fingertips at exactly the right moment. We've put a lot of effort into this over the last 5 years.
|
By Article
You can run the best debrief of your life. Honest timeline, blameless tone, real insights. People leave the room nodding. And then nothing happens. This is the last mile problem of post-mortems - and it's an easy trap to fall into. When you've just been through a stressful incident, getting it back up is the priority. Once it's over, the post-mortem itself can feel like the finish line. You've documented what happened, been honest about it, identified what went wrong. It feels like the work is done.
|
By Article
Most engineering teams don’t migrate their on-call and paging systems unless absolutely necessary. No matter how painful their current solution, it's one of those changes that people put off for as long as possible because the cost is real. The disruption, the retraining, the risk of missing a critical page during the transition. It's not something you do on a whim.
|
By Article
Every incident platform needs to know who owns what. Which team owns which service. Which backlog to send follow-ups to. Which escalation path to page when something breaks. The problem is that most platforms encode this ownership logic separately in every configuration: alert routing, workflows, ITSM ticket syncing, and more. Each one maintains its own copy of the same information, in its own format.
|
By Article
Post-mortems are one of the most consistently underperforming rituals in software engineering. Most teams do them. Most teams know theirs aren't working. And most teams reach for the same diagnosis: the templates are too long, nobody has time, and nobody reads them anyway. These aren't wrong observations. But they're symptoms, not causes. The actual problem is that somewhere along the way, the post-mortem stopped being a piece of communication and became a compliance artifact.
|
By Article
At incident.io we run a deliberately simple technology stack. Keeping things boring has allowed us to scale from a few hundred customers to several thousand, while having only two platform engineers. In this post I'll walk through the stack, explain some of the choices we've made, and touch on the challenges we're facing as we grow.
|
By Article
Picture this: it's 2am, your pager goes off, and you're staring at a production database that's on fire. You know exactly what's wrong. You know exactly how to fix it. But you can't touch anything because you're waiting on someone to approve your access request. Meanwhile, your customers are down, your SLAs are bleeding out, and you're refreshing Slack hoping someone in security is awake to click "approve." This is the incident response tax that too many teams pay.
|
By Article
ITIL 5 launched in January 2026, and for the first time in the framework's 40-year history, AI governance is front and center. If you're running incident management, on-call rotations, or building operational tooling, this matters: the gap between AI adoption and AI governance is about to become a compliance and operational risk issue. I’m not usually a big ITIL fan, but this guidance has some genuinely useful framing and questions.
|
By incident-io
We rebuilt our post-mortems from the ground up. In this video, Pete and the engineering team talk through how they built it: the decisions they made, the problems they were solving, and what it took to ship AI-native post-mortems.
|
By incident-io
OpsGenie is going away in 2027, forcing a migration decision for thousands of teams. But this isn't just a tooling swap — it's a rare chance to upgrade how you respond to incidents. Because the real pain in incident response isn’t paging. It’s everything that happens after the alert: coordination, clarity, communication, ownership, and follow-through. Most teams solve this through heroics and tool-juggling across chat, tickets, and docs. That approach doesn't scale.
|
By incident-io
A full walkthrough of our completely rebuilt post-mortems experience. We cover AI-generated first drafts from your incident data, accuracy review, inline rewriting, a collaborative editor with live incident context, meeting notes with Scribe, and management tooling including dashboards, exports, and analytics. Post-mortems are included in incident.io Response. AI features and Scribe are available on Pro and Enterprise plans.
|
By incident-io
Everyone your sales team is reaching out to is drowning in emails. The way to cut through isn't to send more of them. It's to get personal, get creative, and get bold. That's the philosophy baked into incident.io's sales culture: experiment constantly, celebrate the inputs as much as the wins, and never play it safe. This video gives you a real look at what it's like to be part of a sales team at one of the most exciting startups right now. There are many more wins to come, and we want the right people here for them.
|
By incident-io
When an incident hits, every second counts. The response team at incident.io builds the tools that make sure engineers aren't flying blind when it matters most. Sam, Tech Lead of the response team, takes us inside what it's really like to build the core of incident.io: the high technical bar, the art of prioritisation, and why there's no shortage of meaningful work to do. If you're an engineer who wants to work on something that genuinely makes other engineers' lives better, this one's for you.
|
By incident-io
Working on AI in incident management means there's no playbook. No million blogs. Just building at the forefront of what's possible with AI models.In this video, Martha, Product Engineer on our AI team, talks about what it's really like working with AI that helps engineers respond to incidents faster. This covers the shift from traditional engineering, learning the personalities of different AI models, and why you need to embrace constant change when new models drop all the time.
|
By incident-io
Post-mortems are required, time-consuming, and widely disliked — but they’re also one of the biggest opportunities to improve reliability. In this webinar, we talked about how to run post-mortems that actually lead to learning and improvement. This covered why most post-mortems fall flat, how to structure them effectively, and walk through a real example to show what good looks like in practice. The goal: fewer wasted hours, better outcomes, and post-mortems that actually matter.
|
By incident-io
Paige Cruz (Chronosphere) shares why postmortems are never truly objective and how to make them useful anyway.
|
By incident-io
Three founders, one kitchen table, and a very honest end of year conversation. In this episode we look back on 2025, from moving continents and growing the company at pace, to ski trips that probably should not have happened, live demos that absolutely could have gone wrong, and the small moments that made the year memorable.
|
By incident-io
Stephen Whitworth, incident.io CEO and Co-founder, kicks off SEV0 San Francisco 2025 with an opening keynote focusing on the future of incident management in an AI-first world.
- April 2026 (5)
- March 2026 (6)
- February 2026 (6)
- December 2025 (4)
- November 2025 (4)
- October 2025 (4)
- September 2025 (1)
- August 2025 (7)
- July 2025 (4)
- June 2025 (5)
- May 2025 (3)
- April 2025 (15)
- March 2025 (6)
- February 2025 (4)
- January 2025 (3)
- December 2024 (10)
- November 2024 (8)
- October 2024 (6)
- September 2024 (3)
- August 2024 (4)
- July 2024 (12)
- June 2024 (8)
- May 2024 (13)
- April 2024 (18)
- March 2024 (15)
- February 2024 (18)
- January 2024 (9)
- December 2023 (10)
- November 2023 (5)
- October 2023 (10)
- September 2023 (16)
- August 2023 (3)
- July 2023 (8)
- June 2023 (6)
- May 2023 (4)
- April 2023 (8)
- March 2023 (2)
- February 2023 (5)
- January 2023 (5)
- December 2022 (3)
- November 2022 (4)
- October 2022 (10)
- September 2022 (7)
- August 2022 (11)
- July 2022 (6)
- June 2022 (3)
- May 2022 (2)
- April 2022 (3)
- March 2022 (6)
- February 2022 (7)
- January 2022 (2)
- December 2021 (5)
- November 2021 (5)
- October 2021 (2)
Create, manage and resolve incidents directly in Slack. Leave the admin and reporting to us.
Improving your incident response, visibility, and ability to learn:
- Less faffing, more fixing: We take care of the admin during incidents, so you can save your brainpower for the decisions that matter.
- Divide and conquer: We make sure everyone’s role is clear, track who’s working on what, and help you escalate if you need extra help.
- Get up to speed, at speed: Get everyone on the same page from the moment they join the incident, and help stakeholders stay in the loop.
- Timelines, in no time: Constructing an incident timeline for review is important, but time consuming. We’ll build one for you in real-time, and keep it constantly up to date.
- Data and insights you can trust: You’ve already paid for your incidents. By surfacing the data you need to make decisions, we help you get your money’s worth.
Incident response for your whole organisation.