Work
Problems, constraints, and what actually changed
Most of this work sits under NDA, so these describe the sector and the scale rather than the client. Each one leads with the constraint — that's the part that made it hard, and the part worth reading.
Infrastructure02
SaaS platform, EU · 2025
Replacing the network under a running production fleet
A staged migration to Cilium and eBPF across a live cluster fleet — kernel-level network policy, no customer-visible downtime, and traffic visibility the team had never had.
- Downtime
- None
- Node pools migrated
- TODO
- Unknown dependencies found
- TODO
- Cilium
- eBPF
- Hubble
- Kubernetes
- Terraform
- Gateway API
B2B SaaS platform · 2024–2025
From one cluster per customer to one platform
A SaaS product was scaling infrastructure cost linearly with customers. I designed the tenancy model that broke that curve — real isolation, per-tenant cost visibility, and an escape hatch for the customers who genuinely needed one.
- Clusters
- TODO
- Onboarding time
- TODO
- Infra cost per customer
- TODO
- Kubernetes
- Kyverno
- Cilium
- Argo CD
- Terraform
- OpenCost
Recognise your own problem in one of these?
Most engagements start with a short call and a written plan — what I'll do, what it costs, and what done looks like.
Stockholm, Sweden (CET) · Comfortable overlap with European hours and US East Coast mornings