We’re building the best way for your whole organisation to respond, review and learn from incidents. This is where we talk about how and why.
New Joiner: Isaac Seymour
We're growing the team! Welcome our latest hire - Isaac Seymour
Using context.Context to mock API clients
We've found a pattern to mock external client libraries while keeping code simple, reducing the number of injection spots and ensuring all the code down a callstack uses the same mock client.
We've successfully completed our SOC 2 audit
We're very pleased to announce that incident.io is now SOC 2 compliant, having successfully completed our Type I audit.
On-call by default
Like many SaaS businesses, we have an on-call rota to enable us 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.
Breaking down complex projects into smaller, shippable increments
Mitigate the risks of delivering a complex project by shipping small pieces along the way.
Lisa Karlin Curtis
Workflows: your process, automated
We're delighted to announce the latest feature of the incident.io platform: Workflows. Configure your processes once, and we'll make sure you follow them, every time.
New Joiner: Yann Sarfati
Welcoming Yann Sarfati to the team!
Building safe-by-default tools in our Go web application
Moving fast and breaking things is all well and good, but keeping our customer data safe isn't something we can compromise on. Find out how we do it!
Lisa Karlin Curtis
Deploying to production in <5m with our hosted container builder
Fast build times have a number of benefits, from reliability to developer happiness. We reduces our time to deploy to <5, and it's glorious.
Stay in the loop: subscribe to our RSS feed.
Big or small, there’s huge value in improving your incident response, visibility, and ability to learn.