- Challenge
- The same two people get paged every time. That was how the client put it on the first call.
- Approach
- We set service level objectives with the product owners, restructured the on-call rota, and introduced a simple incident process with written reviews.
- Stack
- SLOs · error budgets · runbooks · post-incident reviews
- Result
- On-call is shared fairly, incidents follow a known routine, and each one leaves a written lesson.
SRE & incident response
On-call that works, incidents handled calmly, and lessons that stick.
Talk to an engineerWhat we do
SRE & incident response consultancy
An assessment of your SRE & incident response setup, with findings ranked by risk and effort.
SRE & incident response delivery
We design and build it with your team, in your accounts, documented as we go.
SRE & incident response support
Monitoring, patching and upgrades, with incident response agreed per contract.
SRE & incident response training
Workshops and pairing on SRE & incident response, built around your own systems.
Tools we work with
Incident response
- PagerDuty
- Opsgenie
- incident.io
- Rootly
SLOs
- Sloth
- Pyrra
- Nobl9
- Grafana SLOs
Status & comms
- Statuspage
- Better Stack
- Slack
Resilience testing
- k6
- Chaos Mesh
- Litmus
- AWS Fault Injection Service
Practice
- Runbooks
- error budgets
- post-incident reviews
- game days
How an engagement runs
- 1 A call. 30 minutes with an engineer to understand the problem.
- 2 A look. Read-only access or a walkthrough, so we scope from facts.
- 3 A proposal. Scope, deliverables and a price model: fixed scope, day rate or retainer.
- 4 The work. In your accounts and repositories, alongside your team.
- 5 A handover. Documentation and a session with your team, so you’re not dependent on us.
Proof
A recent SRE & incident response engagement. We keep client names private, but the problem, the work and the outcome are exactly as they happened.
See our workQuestions
Do you work in our accounts or yours?
Yours. Everything we build lives in your cloud accounts and repositories from day one, so there is nothing to migrate when we finish.
Can you work alongside our own team?
Yes, and we prefer it. We can run a project ourselves, embed engineers in your team, or pair with your people so they pick it up as we go.
How is this priced?
Depending on the work: a fixed-scope price, a day rate or a monthly retainer. We agree it in a written proposal before anything starts.