Managed DevOps Plans
Managed DevOps means we operate your DevOps function for a monthly fee: monitoring, incident response, pipelines, cluster and infrastructure operations, security patching and reporting. Plans differ by coverage hours. Month-to-month after an initial three-month stabilisation period.
- Typical duration
- Onboarding takes about four weeks, then ongoing month-to-month after a 3-month stabilisation period
- Format
- Monthly plan, written SLA, monthly reporting, month-to-month after stabilisation
- Led by
- A named senior engineer
Who this is for
- Startups and scale-ups that need senior DevOps without a full in-house team
- Teams whose engineers are pulled into infrastructure firefighting
- Companies that need out-of-hours cover for production
- Organisations that want one accountable partner for platform operations
What is included
Monitoring and alerting
Infrastructure and service monitoring with alert routing, tuned against agreed service levels.
Incident response
Severity levels, response targets written into your agreement, communication during incidents and a review afterwards.
CI/CD ownership
We maintain and improve your pipelines and release process.
Cluster and infrastructure operations
Kubernetes operations, upgrades, node and capacity management, and infrastructure code maintenance.
Security patching and baseline
Regular patching, access reviews and baseline checks, with findings tracked to closure.
Cost reviews
Regular reviews of spend, right-sizing and waste, reported against the baseline.
Runbooks and documentation
Documented runbooks for every critical component, kept current.
Reporting and reviews
Weekly check-ins, monthly reporting and architecture reviews before major releases.
Choose your coverage
All plans share the same engineering standards and ownership terms. They differ by when we are on call.
Business hours
Cover during agreed working hours
- +Monitoring and alerting
- +Incident response during agreed hours
- +Pipeline and infrastructure maintenance
- +Monthly reporting
Response: Response targets set in your written SLA
Extended
Extended hours and weekend cover
- +Everything in Business hours
- +Extended-hours incident response
- +Priority change handling
- +Quarterly architecture review
Response: Response targets set in your written SLA
24/7 on-call
Round-the-clock cover with on-call engineers
- +Everything in Extended
- +24/7 on-call rota
- +Incident response for P1 at any hour
- +Documented escalation path
Response: P1 first response within 15 minutes
What you receive
- ✓An onboarding period that audits, documents and stabilises your platform
- ✓Written SLA and escalation path
- ✓Weekly check-ins and a monthly report
- ✓Runbooks and architecture documentation in your repositories
- ✓An exit plan agreed up front
What we need from you
- •Access to cloud accounts, repositories and CI systems
- •A named technical and a named business contact
- •A decision on paging tools and communication channels
- •Agreement on severity definitions for your services
Not included
- –Penetration testing or formal security audits
- –Compliance certification (we implement technical controls, we do not issue certificates)
- –Feature development in your application code
How it runs
- 01
Discovery call
We confirm scope, coverage hours and priorities, and agree the plan and SLA in writing.
- 02
Onboarding
Access review, audit, documentation of runbooks and alert thresholds, and pipeline and monitoring hardening.
- 03
Stabilisation
Three months to bring the platform to an agreed baseline and settle the operating rhythm.
- 04
Steady-state operations
Ongoing operations, monthly reporting and continuous cost and security improvement.
- 05
Review and adjust
We review the plan regularly and change coverage or scope as your needs change.
Every package starts with a short scoping call. We then confirm scope, deliverables and timeline in writing, and you decide whether to go ahead. Prices are quoted for that fixed scope, not as a rate card.
Who you will work with
Engagements are led by a named senior engineer, not passed to an anonymous team.
CEO, DevOps / SRE / Cloud Consultant Engineer
You keep everything
No lock-in, by design. If you stop working with us, nothing you rely on stops working.
Your accounts
Everything runs in cloud accounts and subscriptions you own and control.
Your code
Infrastructure code, pipelines and configuration live in your repositories.
Your documentation
Architecture notes and runbooks are written for your team and handed over.
A defined exit
We agree the handover steps in writing, and access is removed when the work ends.
Related services and technologies
Frequently asked questions
What does the SLA cover?
Is there a minimum contract?
How is this different from hiring a DevOps engineer?
Which platforms do you operate?
What happens if we leave?
Get a written scope for Managed DevOps Plans
Book a short scoping call. You receive scope, deliverables and timeline in writing, and you decide whether to go ahead.