Ongoing support
For infrastructure we didn't build: inherited, outgrown, or simply short of the people it needs. We learn it properly, then take on as much of the running as you want to hand over.
Which page you want
If we build the cluster, keeping it current is already part of that engagement. See on-prem Kubernetes. This page is the other case: something already running, that needs covering. Inheriting somebody else's cluster is a job most consultancies decline, and it's the one we're most often asked for.
Two shapes
We take the cluster on.
We learn the estate first, then own break-fix, security patching, version currency and planned upgrades against agreed response targets. You keep running it day to day; we own the work with a deadline attached.
We work alongside your team.
On-call participation, capacity planning and incident review from someone who already knows the estate when it breaks, rather than a stranger reading your runbook during an outage.
Before anything is promised
We won't commit to response targets against an estate nobody on our side has examined. It isn't caution, it's that the number would be meaningless. So adoption starts with an architecture and capacity review: same work, different purpose.
It also tends to surface what the real problem is. Sometimes the answer isn't a support contract at all, and we'd rather find that out before you're paying for one.
Typical response targets
| Severity | Response | Cover |
|---|---|---|
| Production cluster down | 1 hour | 24×7 cover |
| Production degraded | 4 hours | 24×7 cover |
| Non-production or planned work | 1 business day | Business days |
| Advisory questions | 2 business days | Business days |
Typical, not committed. Coverage level is the main variable and the specifics are agreed in your contract. They're looser than our platform SLA because this covers infrastructure we don't operate, where diagnosis depends on access and information we don't hold.
What it runs, what breaks, and how much of it you want to stop thinking about. Quoted per engagement after a scoping call.