01The path to production
- Manual steps and who can bypass them
- Rollback: tested, or hoped for
- Drift between environments
- Secrets in pipelines
Infrastructure analysis: an X-ray of how you ship and run
Delivery, Kubernetes, cloud cost and observability: read end to end in 1–2 weeks, ranked by what actually matters.
Delivery path manual prod deploys
Kubernetes requests ≫ usage
Cloud cost untagged spend
Observability alerts tuned
Ranked by urgency · each option costed over 3 years
What you can expect
- Read-only access. Nothing changes while I look.
- Findings ranked by urgency, not by what I could sell you next.
- Scope agreed before I start, so there are no surprises.
- The report is yours, whether or not you hire me afterwards.
02Kubernetes and the data on it
- Version and upgrade path
- Requests vs real usage, autoscaling
- RBAC and network policies
- Postgres: HA, backups, point-in-time recovery
03Where the money goes
- Spend by team and service
- Idle and oversized resources
- Commitments and spot
- Lock-in premiums
04What you can see when it breaks
- Coverage vs what actually breaks
- Alert noise and SLOs
- Logs and traces joined up
- On-call and runbooks
A fixed-scope review of how your software is built, shipped and run: the delivery pipeline, the Kubernetes clusters, the cloud bill and the monitoring. It takes 1–2 weeks and needs read-only access, so nothing changes while I look.
You get a written report with every finding ranked by urgency, each fix costed over three years (including leaving it as it is), and a roadmap that puts the quick wins first. I walk your team through it and answer every question.
It suits a team whose cloud bill keeps growing, whose releases feel risky, or who hears about outages from customers first. The report is yours to keep: follow it with your own team, with me, or both.
What you get
- Written report
- Costed options
- Roadmap
- Walkthrough
- GitOps with ArgoCD ArgoCD · Helm Optional
- Release automation GitHub Actions · Azure DevOps Optional
- Infrastructure as code Terraform · Terragrunt Optional
- Postgres on Kubernetes CloudNativePG Optional
- Observability stack Prometheus · Loki · Tempo · Grafana Optional
How it goes
- 01 Kickoff and access
- 02 Analysis
- 03 Report and walkthrough
- 04 Build (optional)
Common questions
How long does an infrastructure analysis take?
Usually 1–2 weeks, depending on the size of the setup, from the kickoff call to the report walkthrough.
What access do you need?
Read-only access to your repositories, clusters, cloud bill and dashboards. Nothing changes while I look.
What do I get at the end?
A written report with every finding ranked by urgency, each fix costed over three years, a roadmap, and a walkthrough session with your team.
How much does it cost?
It depends on the size of the setup. Scope and price are agreed after a first 30-minute call, before any work starts.
Do I have to hire you afterwards?
No. The report is yours to keep. Your team can follow the roadmap alone, with me, or both.
Which platforms do you cover?
Kubernetes on AKS, EKS or GKE, Azure and AWS, and bare metal, with CI/CD in ArgoCD, GitHub Actions or Azure DevOps.