MK
All services
06

DevOps & Cloud Infrastructure

I build infrastructure that survives the cloud decision being wrong. Terraform-first, environment parity from local to production, and pipelines that don't care whether the underlying provider is AWS, Azure, or GCP.

A data centre server aisle lit by status LEDs
What this looks like
Infrastructure-as-code
  • Terraform modules with sane defaults and tagging
  • Environment parity: local, ephemeral preview, staging, production
  • State management, remote backends, and policy-as-code (OPA / Sentinel)
Cloud-agnostic pipelines
  • GitHub Actions / GitLab CI / Azure DevOps — same shape across providers
  • Container build, scan, push, deploy as one repeatable contract
  • Ephemeral preview environments per PR for review and design partners
Operations & cost
  • Secrets management (Vault, AWS/Azure secret stores, sealed-secrets)
  • Cost guardrails: budgets, anomaly alerts, idle-resource reaping
  • Disaster recovery and backup posture review
What you walk away with
  • Terraform repo with reusable modules
  • CI/CD baseline with preview environments
  • Cost + DR posture review with action plan
Tools & tech
Terraform
AWS
Azure
GCP
Kubernetes
Docker
GitHub Actions
Vault

Ready to scale your engineering?

Book a 30-minute discovery call. If we're not a fit, I'll tell you on the call — and point you toward someone who is.

WhatsApp me