Infrastructure & Ops
NoOps — Fully Managed Platform
Your developers push code. Everything after that is ours.
- 24x7 monitoring with 15-minute P1 response
- Patching, scaling and DR handled
- One monthly report, no surprises
- 15 min
- P1 response, 24x7
- 99.95%
- Platform availability target
- 0
- On-call rotations for your team
SLA-backed, measured and reported monthly
Standard NoOps SLA; higher available by design
The point of the engagement
Who this is for
Teams of roughly ten to a hundred engineers who need production reliability but cannot justify — or cannot hire — a platform and SRE function. Hiring two good platform engineers in Bengaluru costs meaningfully more than this and gives you no coverage at 3am on a Sunday.
It is also for AI systems we built. An automation running your invoice pipeline needs the same operational rigour as any other production service, and it is considerably better if the people who built it are the people carrying the pager.
What 24x7 actually requires
Alerts that mean something. Tied to user-visible symptoms, not raw metrics. "Checkout error rate above 2%" is actionable at 3am. "CPU above 80%" is not.
A runbook per alert. Written before it fires. An alert with no runbook is someone reading code at 3am, and that is how small incidents become long ones.
A real escalation path. Named engineers, defined response times, and a route to someone who can make a decision. Not a shared inbox.
Rehearsed recovery. Quarterly DR tests with a written result. Restore paths that have never been executed do not work; this is close to a law of nature.
The monthly report
One document: availability against target, every incident with cause and fix, patch status, spend versus forecast, and the three things we recommend doing next. It is written for someone who has fifteen minutes and needs to know whether to worry.
How it runs
What the engagement looks like
Phases, not a proposal. Each one has an output you can see.
- 1
Assess and stabilise
Weeks 1-3We take on the estate as it is, fix what would page us at 3am, and set honest baselines. Nobody signs an availability target on infrastructure they have not seen.
- 2
Instrument to on-call standard
Weeks 3-5Alerts tied to user-visible symptoms rather than raw CPU, with runbooks attached. An alert without a runbook is a notification, not an on-call system.
- 3
Take the pager
Week 6We assume 24x7 responsibility with an agreed severity matrix and escalation path. Your team stops carrying it that week.
- 4
Improve continuously
OngoingMonthly reliability review, quarterly DR test and security review, ongoing cost optimisation. Every incident produces a blameless post-mortem and a fix, not a slide.
Proof
Where we have done this
FAQ
Questions we get asked
Talk to someone who does noops (fully managed)
Thirty minutes with an engineer who has delivered this, not an account manager. You will get a straight answer on feasibility, rough cost and where it would fail.
Or email [email protected] · we reply within 1 business day