
Like many SaaS businesses, we use our own on-call software to provide 24x7 cover if there are problems with incident.io. We have a 'pager' which will alert the relevant person if something unexpected happens in our app, so that they can investigate and fix it if needed.
Note: This was adapted from an internal document we wrote about how we think about on-call at incident.io.
We're building a product that people depend on 24x7, all year around. It's important it always works, that means we need to support it around the clock. During office hours this is a shared responsibility across the whole team, but to limit the impact out of hours, we have a dedicated person 'holding the pager'.
Being on-call doesn't come without its benefits. Designing our on-call schedules around this principle tightens the feedback loops between shipping and running. This helps us to make pragmatic engineering decisions and provide a healthy tension between shipping new code, and supporting and improving what we have.
Additionally, our product is designed, partly, to support folks who are on-call. There's no better way for us to empathise with our customers than to do the job ourselves — as detailed in being on-call at incident.io.
As an incentive, and to compensate for the inconvenience of having to remain close to your laptop, we'll pay a fixed amount per week to anyone who's on-call.
We'll calculate on-call compensation automatically from our schedules, and take overrides into account too — down to the minute, so if you cover someone for an hour while they go to the shops, you'll be paid for that time.
By compensating on-call we also aim to make overrides feel more fair, and avoid the need for more complex swaps of time. If someone offers to cover a day of your shift, they'll be paid for it so there's no need to feel indebted.
On-call payment is not expected to cover any time you spend working outside of hours. If you're paged and end up working in your evening, you should take time off in lieu. We trust you to manage this time yourself.
Being on-call unavoidably has an impact on your home life, but we want to provide the best possible experience. Here's a few ways we'll collectively help each other:

I'm one of the co-founders, and the Chief Product Officer here at incident.io.

Instead of thinking about reliability as an exercise in figuring out what we can control, and ignoring anything beyond that, we think about what we'll be really proud to offer to customers.
Mike Fisher
A forward look at where engineering teams are heading with AI, based on conversations with design partners who are visibly six-to-twelve months ahead of the average. Tailored code agents, MCP gateways, agentic products that talk to each other — most of the picture is already there in pockets, and the rest of the industry is closing the gap fast.
Lawrence Jones
incident.io just launched the PagerDuty Rescue Program, making it easier than ever for engineering teams to ditch their decade-old on-call tooling. The program includes a contract buyout (up to a year free), AI-powered white glove migration, a 99.99% uptime SLA, and AI-first on-call that investigates alerts autonomously the moment they fire.
Tom WentworthReady for modern incident management? Book a call with one of our experts today.
