Cloud and DevOps Health Check
A Cloud and DevOps Health Check is a fixed-scope, read-only review of your cloud accounts, infrastructure code, pipelines and operations. You receive a written findings report ranked by risk and effort, plus a prioritised roadmap you can act on with us or without us.
- Typical duration
- Typically 1 to 2 weeks for one environment, confirmed in the written scope
- Format
- Fixed scope, read-only access, written report and readout call
- Led by
- A named senior engineer
Who this is for
- Teams that have grown fast and no longer trust their own cloud setup
- Companies preparing for a security review, funding round or enterprise customer audit
- Leaders who inherited infrastructure and need an honest picture of its state
- Teams considering a migration, platform rebuild or managed service and wanting a baseline first
What is included
Access and identity review
How people and services authenticate, who can change production, and where permissions are wider than needed.
Architecture and networking
Account or subscription structure, network layout, exposure to the internet, and single points of failure.
Infrastructure as code and drift
How much of the estate is in code, how changes are reviewed, and where console edits have created drift.
CI/CD and release process
Pipeline design, build speed, secrets handling, approvals, rollback and how risky a normal deployment is.
Security baseline
Encryption, logging, secrets, patching and common misconfigurations, aligned to recognised baselines such as the CIS benchmarks.
Reliability, backup and recovery
Backups that exist, backups that have been restored, and how long recovery would realistically take.
Observability and on-call
Whether you would notice a problem before customers do, and whether alerts reach someone who can act.
Cloud cost
Obvious waste, missing budgets and alerts, and the main drivers of spend, measured against a baseline.
What you receive
- ✓A written findings report with every issue ranked by risk and effort
- ✓A current-state architecture diagram
- ✓A prioritised 30, 60 and 90 day roadmap
- ✓A readout call with your engineering leads
- ✓Optionally, a scoped proposal for the work you want help with
What we need from you
- •Read-only access to cloud accounts, repositories and CI system
- •One technical contact who can answer questions quickly
- •A list of the environments in scope (production, staging, others)
- •Any existing architecture notes, even if they are out of date
Not included
- –Penetration testing or formal security audits
- –Compliance certification (we implement technical controls, we do not issue certificates)
- –Making changes to your environment (that is a separate, scoped piece of work)
How it runs
- 01
Scoping call
We agree the environments, goals and constraints and confirm them in a written scope before anything starts.
- 02
Read-only access
You grant read-only roles in your cloud accounts, repositories and CI system. We change nothing.
- 03
Review
We work through the areas above, interview the engineers who know the system, and verify findings against the real configuration.
- 04
Report and readout
You receive the report, then we walk through it together and answer questions.
- 05
Decide next steps
You can act on the roadmap yourselves, with us, or with someone else. The report is yours either way.
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
Do you change anything in our environment?
How long does a Health Check take?
Why do you not publish a price?
Who owns the report?
Can you review AWS and Azure together?
Get a written scope for Cloud and DevOps Health Check
Book a short scoping call. You receive scope, deliverables and timeline in writing, and you decide whether to go ahead.