Cloud Centre of Excellence.
Operating model plus managed substrate, in one engagement. RACI, governance, FinOps, AI enablement principles. Outcome: the team you wanted to hire, on the platform you wanted to build.
See the solution→ [05] / SERVICE — MANAGED CLOUD & PLATFORM
We operate the parts of the platform your team shouldn't be holding.
Defined scope. Named owners. Monthly written reports. We run the platform substrate so your engineers can ship product, and we measure ourselves on how fast you could fire us painlessly.
[01] / CAPABILITIES _
What we run.
- [01] / FOUNDATION
Landing zone operations
Identity, network, accounts, policy, baseline monitoring. Quarterly drift reviews, named owners.
- [02] / PLATFORM
Internal developer platform ops
Golden-path updates, runtime patching, catalogue maintenance, on-call rotation included.
- [03] / SECURITY
Security operations
Detection coverage, response runbooks, evidence pack for audits. SecOps as a service, not a checkbox.
- [04] / FINOPS
FinOps operations
Monthly cost report your CFO can read. Anomaly detection. Allocation, showback, savings recommendations.
- [05] / OBSERVE
Observability ops
SLO upkeep, alert tuning, dashboard hygiene. We delete more alerts than we add.
- [06] / AI OPS
AI service operations
Token, latency, quality and cost telemetry. Guardrail upkeep. Pilot-to-production progression.
[02] HOW WE RUN IT _
How we run a managed engagement.
From audit to handoff12 month minimum, monthly thereafter
This is what our on-call looks like in practice: concrete actions from alert to runbook update, with minutes as the unit of accountability.
[FIG.08 / MANAGED SERVICES · INCIDENT TIMELINE] FROM ALERT TO RUNBOOK · ONE EVENT
[01] / SCOPE
Scope, scope, scope.
Two-week scoping. RACI written, named owners on both sides, exit clauses included.
⏱ 2 wks [02] / ONBOARD
Onboarding, 4–6 weeks.
Runbooks documented, observability baselines, monthly report template agreed.
⏱ 4–6 wks [03] / OPERATE
Monthly written report.
What happened, what changed, what's next. Quarterly maturity review with your CTO.
⏱ monthly [04] / EXIT
Painless exit, by design.
Runbook hand-back, knowledge transfer, exit fee zero. We measure ourselves on how fast you could fire us.
⏱ 1 moQuestions about managed services.
[01] How is this different from an MSP? +
MSPs run tickets. We run a runbook. We name what we do, what we don't, and we publish the SLOs we hold ourselves to. The monthly report is plain English.
[02] Can you run only part of the platform? +
Yes. Most engagements are partial. Common splits: we run the foundation, your team runs application platforms. Or we run FinOps and SecOps, your team runs delivery.
[03] What if we want to leave? +
Then you leave. Runbooks hand back. Documentation is yours from day one. No exit fees, no contract trap, no acquisition risk on your side.
[04] How is staffing decided? +
Six engineers per engagement, named, with public engineering profiles. You see the proposed team before signing. We're transparent if a specialist needs to flex in for a specific phase, but the core six stay for the duration.
[NEXT STEP]