Packages with scope and timeline in writing
Start with a defined piece of work instead of an open-ended engagement. Every package lists what is included, what you receive, what we need from you and how long it typically takes. Anything else is scoped as a custom quote.
Cloud and DevOps Health Check
Teams that want an independent view before investing, scaling, or facing an audit.
Typical duration: Typically 1 to 2 weeks for one environment
Kubernetes and EKS Production Readiness Review
Teams running Kubernetes in production, or about to, who want to know what could fail.
Typical duration: Typically 1 to 2 weeks per cluster
Landing Zone Sprint
Teams starting on AWS or Azure, or replacing a console-built setup, who need a sound foundation.
Typical duration: Typically 2 to 4 weeks
CI/CD Rebuild
Teams with slow, fragile or hand-maintained pipelines, or moving off Jenkins.
Typical duration: Typically 3 to 6 weeks depending on the number of pipelines
Observability and On-call Setup
Teams that learn about incidents from customers, or whose alerts are mostly noise.
Typical duration: Typically 3 to 5 weeks
Managed DevOps Plans
Teams that want senior DevOps capability without building the whole function in-house.
Typical duration: Onboarding takes about four weeks
Compare packages
| Package | Best for | Typical duration | Format |
|---|---|---|---|
| Cloud and DevOps Health Check | Teams that want an independent view before investing, scaling, or facing an audit. | Typically 1 to 2 weeks for one environment | Fixed scope, read-only access, written report and readout call |
| Kubernetes and EKS Production Readiness Review | Teams running Kubernetes in production, or about to, who want to know what could fail. | Typically 1 to 2 weeks per cluster | Fixed scope, read-only cluster access, written report and readout call |
| Landing Zone Sprint | Teams starting on AWS or Azure, or replacing a console-built setup, who need a sound foundation. | Typically 2 to 4 weeks | Fixed scope, delivered as code in your repositories, documented handover |
| CI/CD Rebuild | Teams with slow, fragile or hand-maintained pipelines, or moving off Jenkins. | Typically 3 to 6 weeks depending on the number of pipelines | Fixed scope, pipelines delivered in your repositories, parallel run before cut-over |
| Observability and On-call Setup | Teams that learn about incidents from customers, or whose alerts are mostly noise. | Typically 3 to 5 weeks | Fixed scope, delivered in your tooling and repositories, with training |
| Managed DevOps Plans | Teams that want senior DevOps capability without building the whole function in-house. | Onboarding takes about four weeks | Monthly plan, written SLA, monthly reporting, month-to-month after stabilisation |
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.