Enterprise & Operations
SRE & Managed Operations
Most outages are found by customers first, because the alerts were noisy and the runbook was out of date. We run production systems for you - monitoring, on-call, incident response, and the fixes that stop the same incident coming back - with response targets written down. This is the half of our work that starts after launch, and the engineers on call know the system because many of them built it.
What We Run
Production, looked after around the clock
Six services that make up the Managed SRE tier. Onboarding comes first, and on-call starts once the runbooks have been tested.
Monitoring & Alerting
Alerts on the symptoms users feel, tuned until every page means something. Dashboards your team actually opens.
24×7 On-Call
A staffed rota around the clock, every day of the year, with acknowledgement and engagement targets in writing.
Incident Response
A named incident lead, a status channel, and decisions logged as they happen.
Post-Incident Reviews
A written note for every P1: what happened, what we did, and what changes so it does not happen again.
Reliability Engineering
Service-level objectives, capacity planning, and automation of the repeat work, so on-call stays sustainable.
Runbooks & Operational Readiness
Runbooks proven in game days, and a readiness review before anything new reaches production.
HOW IT RUNS
Four phases, from noisy to dependable
Each phase ends with something you can hold: a baseline, alerts that mean something, tested runbooks, a monthly report.
Onboarding Review
We learn the system before we are paged for it: architecture, alerts, incident history, dependencies and access.
DELIVERABLES
- Service and dependency map
- Alert inventory and noise report
- Incident history review
- Access and escalation paths
- Gaps against the tier
- Onboarding plan
Read This First
Three cases where managed operations is the wrong buy
Sometimes the honest answer is a different service:
The System Changes Daily
If the architecture is still being decided, keep it under a build engagement for now. An on-call rota needs something stable to learn.
Nobody Will Fix Root Causes
If incident actions never reach your backlog, we will keep restoring the same failure. Managed operations needs a route to change the system.
Business Hours Are Enough
If an overnight outage costs you little, the Standard or Extended support tier costs less and does the job.
What You Can Hold Us To
Response targets, written down
These are the Managed SRE tier on our support page, stated rather than implied.
01
24×7×365 Coverage
A staffed on-call rota, every hour of every day.
02
15 Minutes to Acknowledge
A P1 is acknowledged within 15 minutes, and an engineer is engaged within an hour.
03
A Note for Every P1
Within five working days: what happened, what we did, and what changes.
04
A Named Person
A technical account manager who knows your system and joins your reviews.
FAQs
Managed operations, answered
Managed SRE is the top support tier. This page is what sits behind it: the monitoring, rota, runbooks and reliability work that make the response targets achievable.
No. We onboard systems built by others. The onboarding review exists so that our engineers know the system before they are paged for it.
In Pune, India (UTC+05:30). Standard hours overlap the European morning and the US overnight; the Extended tier covers the full European working day and runs into the US East Coast afternoon; the Managed SRE rota covers the rest.
Managed SRE is a monthly retainer with a 12-month minimum. Onboarding comes first, and on-call starts once the runbooks are tested.
Find out what your
alerts are telling you.
Tell us what you run, who gets paged today, and what the last bad incident looked like. The first step is an onboarding review, and a plain account of what it finds.
Have a project in mind?
Start with a review of what your alerts are telling you.