Platform health check
Your Kubernetes, CI/CD pipelines, infrastructure as code, monitoring and backups reviewed against good practice, with a ranked list of what to fix first.
The parts that keep production running
Kubernetes and containers
Cluster set-up, resource limits, upgrades and who can change what. VMs and serverless are covered the same way.
CI/CD
How code is built, tested and deployed, how secrets are handled, and how a bad release is rolled back.
Infrastructure as code
Terraform or equivalent: coverage, drift, state handling and review of changes.
Monitoring and alerting
Logs, metrics and alerts, and whether an alert reaches someone who can act on it.
Backups and recovery
What is backed up, whether a restore has been tested, and how long recovery would take.
Access and secrets
Who can change production, how access is removed, and where secrets live.
Scope, review, report, walkthrough
Scope
We agree the environments in scope and get read-only access.
Review
We review configuration and pipelines and talk to the people who run them.
Report
Findings ranked by what would hurt most, each with the effort to fix.
Walkthrough
We go through the report with your team and agree the order of fixes.
What you get
- A ranked list of fixes, each with its risk and the effort involved
- Recovery gaps called out: what you could not restore today, and how long it would take
- A short summary for non-technical readers
- A walkthrough with your team
Not included
- Making the fixes, unless agreed as a separate engagement
- Application security testing (see the application security assessment)
- Cloud cost analysis (see the cloud cost review)
Duration
Agreed at scoping, based on the number of environments and services in scope.
Price
On request. Fixed and agreed in writing before work starts.
Is this the right fit?
Teams that run their own platform without a dedicated platform or SRE engineer, teams that inherited infrastructure nobody fully understands, and anyone preparing for a customer due-diligence review. For ongoing work, see Cloud & DevOps.
Common questions about the platform health check
Do we need to run Kubernetes?
No. The health check covers whatever you run: virtual machines, containers, Kubernetes or serverless.
What access do you need?
Read-only access to your cloud accounts, CI/CD system and infrastructure code, plus an hour or two with the people who run them.
Will you change anything?
No. The health check is read-only. Fixes are made afterwards, by your team or by us as a separate engagement.
How is it different from the cloud cost review?
The health check is about reliability and safety: deployments, recovery, monitoring and access. The cost review is about what you pay. Many teams do both.
Can you make the fixes?
Yes, as a separate engagement scoped after the health check, or your team can work from the report.
Find out what would break first
Tell us what you run and how it gets to production. We’ll suggest what to check first, and if your platform is in good shape, we’ll say that.