All offers
Managed service
Cross-cutting
Platform Operations Partnership
Your engineers build on the platform; we keep it running. The infrastructure, code and control stay yours — the operations become ours.
Duration
12 months, rolling
The problem
Building a platform is a project. Running one is a permanent staffing commitment, and it is the commitment that gets underestimated.
A production Kubernetes platform with observability, security, policy, and self-service needs a team that can cover upgrades, incidents, CVEs, capacity, and the constant drift of a fast-moving ecosystem. In practice that means eight to fifteen specialists, in a hiring market where those specialists are expensive and hard to keep. Most organizations end up with three, who spend their time firefighting instead of improving developer experience, and the platform slowly stops being an asset.
What we do
Day-2 operations for your platform: monitoring, incident response, patching, upgrades, capacity management, and lifecycle management of every component
Security operations: CVE tracking and remediation for your platform stack, policy maintenance, and compliance evidence upkeep
Continuous improvement: your platform does not freeze. We keep it current with the ecosystem and improve it against the developer experience metrics we agree with you.
Platform engineering capacity: an agreed allocation for new capabilities, new golden paths, and new self-service abstractions, prioritized with you each quarter
Support for your platform team: escalation, pairing, and knowledge transfer, so your people get stronger rather than more dependent
How this is different from outsourcing
Everything stays yours. Your infrastructure, your accounts, your repositories, your code. We work in your systems with your tooling, and the runbooks stay in your documentation. There is a documented, tested exit: at any point you can take operations back in-house, and we will help you do it. Since we build on open source and standard tooling, there is nothing proprietary to unwind.
We say this plainly because the fear of a managed service is lock-in, and it is a reasonable fear.
Service levels
Availability targets, response times, and escalation paths agreed to your requirements, from business hours through to 24/7 follow-the-sun, with a European operations model where sovereignty requires it.
Who it is for
Organizations running a production platform who would rather spend their scarce platform engineering capacity on developer experience and product enablement than on upgrade cycles and CVE triage.
Frequently asked questions
How does onboarding work?
As a four-to-six-week transition: we shadow your current operations, take over run responsibility component by component, and close the gaps we find in monitoring and runbooks along the way. You see the takeover progress in the same dashboards we will later operate from.
Do you also operate platforms you did not build?
Yes. Most partnerships start on an existing platform. We begin with a technical due diligence, agree on a stabilisation backlog if one is needed, and take over operations in stages.
How do service levels and pricing work?
A fixed monthly fee tied to the agreed service level and platform scope, reviewed quarterly, plus the agreed engineering allocation. No per-ticket billing — misaligned incentives are how platforms rot.
Interested?
Give us a picture of where you stand and the decision you face. We will return with a scope, a price, and a candid view of whether this partnership makes sense for you.