The latest news from incident.io HQ

We’re building the best way for your whole organization to respond, review and learn from incidents. This is where we talk about how and why.

Engineering

How we page ourselves if incident.io goes down

Learn how we tackle the ultimate paradox: ensuring our alerting system pages us, even when it’s the one failing. It's a common question - let's dive into detail on our "dead man's switch", how we stress-test our systems, and why we care so much about our setup allowing us to dogfood our own product.

Lawrence JonesPicture of Lawrence Jones

Lawrence Jones

8 min read
Article

We’re opening a San Francisco office

We’re expanding our global presence by opening our first office in San Francisco. 🔥

Stephen WhitworthPicture of Stephen Whitworth

Stephen Whitworth

4 min read
Engineering

Organizing ownership: How we assign errors in our monolith

At incident.io, we streamline our monolith by assigning clear ownership to chunks of code and enforcing it with CI checks. Tagged errors are automatically routed to the right team, reducing on-call stress and keeping our system efficient as we scale. Here's how we do it.

Martha LambertPicture of Martha Lambert

Martha Lambert

7 min read
Data

How we handle sensitive data in BigQuery

We take handling sensitive customer data seriously. This blog explains how we manage PII and confidential data in BigQuery through default masking, automated tagging, and strict access controls.

Lambert Le ManhPicture of Lambert Le Manh

Lambert Le Manh

8 min read
Data

How we model our data warehouse

Curious about the inner workings of our data warehouse? We’ve shared a lot about our data stack, but this time we’re diving into the design principles behind our warehouse. This blog breaks down how we structure our data, from staging to marts layers, and how we use it all in our BI tool. It’s a quick look into how we keep things flexible, efficient, and built to scale.

Jack ColseyPicture of Jack Colsey

Jack Colsey

13 min read
Engineering

Lessons from 4 years of weekly changelogs

Writing a meaningful update for customers every week has been held sacred at incident.io since we started the company. We've written over 200 of them in the past 4 years, and we recently celebrated going 2 years straight without missing a single a single week 🚀. Learn how we do it!

Pete HamiltonPicture of Pete Hamilton

Pete Hamilton

13 min read
Engineering

Observability as a superpower

At incident.io, tracing is our secret weapon for catching bugs before customers do. This blog unpacks how traces and spans are built, showcasing their role in debugging and performance tuning. From span creation to integrating traces with logs and error reports, it's a practical guide for adding tracing to your observability toolkit—whether you're in development or production.

Sam StarlingPicture of Sam Starling

Sam Starling

9 min read
Engineering

Choosing the right Postgres indexes

Indexes can dramatically boost your database performance, but knowing when to use them isn’t always obvious. This blog covers what indexes are, when to use them, how to choose the right type, and tips for spotting missing ones. Whether you're optimizing queries, enforcing uniqueness, or improving sorting, you'll learn how to fine-tune your indexing strategy without overcomplicating it.

Milly LeadleyPicture of Milly Leadley

Milly Leadley

10 min read
Article

Mastering regulatory compliance with incident.io

Learn how incident.io streamlines regulatory compliance by automating incident management, enhancing collaboration, and simplifying audits for frameworks like GDPR, SOC2, and DORA.

Chris EvansPicture of Chris Evans

Chris Evans

11 min read

Stay in the loop: subscribe to our RSS feed.

Move fast when you break things