Hi, I'm
Engineering Leader · Builder · Bitcoiner
17+ years building production systems at scale. I lead engineering teams, architect distributed platforms, and obsess over infrastructure that runs well and costs less. Currently a Technical Manager at Head Digital Works.
I write about AWS, self-hosting, Bitcoin sovereignty, and the thinking behind hard decisions.
Replaced $40K/month Datadog + $40K/month CloudWatch with a self-built Grafana LGTM stack. ~$120K/month prospective savings across 15 departments at 6 TB/day.
Architected a targeting engine with Java 21 virtual threads processing millions of events at <500ms p99.
Right-sizing, Karpenter, Graviton, and lifecycle policies across production infrastructure. Zero performance loss.
Run my own Kubernetes clusters, observability stack, and services on bare metal. No cloud lock-in.
Technical deep dives, building in public, Bitcoin, and first-principles thinking.
Six dedicated servers in a German data centre, and a multi-tenant Kubernetes platform on top of them. Most of what I run my life on now lives there. This is an honest account of why I built it, what it actually costs, and the situations in which you absolutely should not do the same.
I have two children. They will grow up in a world where Bitcoin is part of how families save, spend, and pass on wealth. Software good enough for non-technical families to do this safely does not yet exist. So I am building it — in public, decision by decision, with the next generation as the only deadline that matters.
Python on Knative was costing me 5–7 seconds every cold start. On a small Kubernetes cluster, that latency was the difference between a usable AI agent and a broken one. So I rewrote four services in Go on three weekends. Here are the measured numbers, the unexpected wins, the unexpected pains, and when you absolutely should not do the same.
