#
How it's built
How this homelab is built — IaC in five minutes
Everything in this homelab is Infrastructure as Code (IaC): virtual machines are provisioned declaratively, configured by automation, and the configuration itself lives in version control — never…
Why I rebuilt a Red Hat-style identity system at home
This homelab had no internal name resolution for a long time — every machine's name-to-address mapping lived in a manually edited local file, copied by hand to every machine that needed it. That…
Security and compliance, sandbox edition
Part of my day job sits in a regulated industry, where hardening standards, compliance checks, and audit trails aren't optional — they're how a system earns the right to run in production at all.…
#
Security & network architecture
Three zones behind a firewall — why I split WAN, DMZ, and LAN
Until recently, every machine in this homelab — from the public-facing portal to internal admin tools I'd never want exposed — sat on the same flat network. That's fine for a lab nobody else touches,…
Letting strangers in, safely — self-service onboarding for outside visitors
The portal already had a login system, but every account on it had been created by hand, by me. That's fine for a lab only I use — it stops working the moment I actually want outside visitors to be…
Two automations, one shared setting — a lesson in ownership
Two separate, independent pieces of automation each manage their own identity system in this homelab — one for accounts I use myself, one dedicated to outside visitors. Both, it turned out, were…
Elsewhere in this homelab
What is deliberately left out →