cloud/recipesStart a project

Available for freelance engagements

Infrastructure,
written like a recipe.

I'm a freelance DevOps engineer who ships repeatable, well-documented systems. Every pipeline, cluster, and platform I build comes with the method to reproduce it.

Book a projectView the recipes
~/cloud-recipes — zsh
$terraform apply

Apply complete. 42 added, 0 changed, 0 destroyed.

$kubectl rollout status deploy/api

deployment "api" successfully rolled out

$gh workflow run deploy.yml

✓ pipeline green — shipped in 4m 12s

$

// services

Three recipes I cook to production

Each engagement follows the same discipline: known ingredients, a documented method, and a result your team can reproduce without me in the room.

DevOps

CI/CD, observability, and reliable releases.

Ingredients

  • GitHub Actions
  • Docker
  • Prometheus
  • Grafana

Method

  1. Design pipelines that build, test, and ship on every commit.
  2. Wire up metrics, logs, and alerts so failures surface early.
  3. Codify rollbacks and release gates for safe, boring deploys.

Cloud Automation

Infrastructure as code, from zero to reproducible.

Ingredients

  • Terraform
  • Pulumi
  • AWS
  • Ansible

Method

  1. Model your cloud footprint as version-controlled code.
  2. Automate provisioning, secrets, and environment parity.
  3. Cut cloud spend with right-sizing and lifecycle policies.

Platform Engineering

Golden paths that let your team ship themselves.

Ingredients

  • Kubernetes
  • Backstage
  • Helm
  • ArgoCD

Method

  1. Build internal platforms with self-service templates.
  2. Standardize environments so onboarding takes minutes.
  3. Document the golden path so the team scales without you.

// method

A kitchen discipline for infrastructure

Good infrastructure is repeatable. I treat every engagement like a recipe you can follow again — with clear ingredients, ordered steps, and nothing hidden.

years in infrastructure
8+

years in infrastructure

pipelines shipped
40+

pipelines shipped

uptime maintained
99.9%

uptime maintained

documented handoffs
100%

documented handoffs

  1. mise en place

    Audit & prep

    I map your current stack, bottlenecks, and risks before touching anything — no surprises later.

  2. cook

    Build in the open

    Everything lands as reviewed, version-controlled code. You watch it come together in small, safe increments.

  3. plate

    Ship & document

    The system goes live with runbooks, dashboards, and a handoff so your team owns it fully.

// contact

Have infrastructure that needs a recipe?

Tell me about your stack and where it hurts. I'll reply with an honest take and a plan — whether that's a pipeline, a cloud migration, or a full platform.

hello@cloudrecipes.devGitHubLinkedIn