The Door Was Open
You didn't find this by accident. You found it the way you find everything worth finding — sideways. A link in a comment. A handle you didn't recognize. A bio that said something about an RV and a security operations center and you thought that can't be real.
You found it the way you find everything worth finding — sideways. A link in a comment. A handle you didn't recognize. A bio that said something about an RV and a security operations center and you thought that can't be real.
It's real.
28 Docker containers. Local LLMs behind a governance protocol I wrote because nobody else was writing them. Suricata. Zeek. Wazuh. CrowdSec. Grafana. Node-RED. InfluxDB. A full network security stack running from a 40-foot fifth wheel parked somewhere you won't find on a map. Zero cloud subscriptions. Zero venture capital. Zero employees. One builder. Cold beer.
And I document every single piece of it.
I'm not a security engineer by degree. I'm not a developer by trade. I'm not an AI researcher by any credential that matters on a résumé.
I'm the kid who took apart the family VCR in 1984 and did not fix it.
I spent the next four decades learning the hard way — the only way that sticks. Wiring closets at 2am. Home labs built from machines that fell off the corporate refresh truck. The kind of troubleshooting where the answer is always in the last place you look because you stop looking when you find it.
And then AI happened.
The kind where the machine does 70% of the work and you make the 30% of decisions that actually matter.
I looked at that and thought: this changes everything.
Not because the technology is new. Because the access is new. The things that took a team of twelve and a six-figure budget now take one person, a workstation, and the stubbornness to read the documentation.
So I built it. From an RV. Because that's where I live.
If you're still reading, I already know some things about you.
You looked at the cloud and thought: that's just somebody else's computer I'm renting at a markup. You've been running something self-hosted — a Plex server, a Pi-hole, a NAS that started as "just for backups" and now runs fourteen services. You already suspected this was the right path. You just hadn't found anyone doing it at this scale and writing about it honestly.
Or maybe you're not technical at all. Maybe you're just curious about what happens when one person decides to build the thing the hard way and tells the truth about it. That works too.
Either way — you're here now.
Every article on this site is the mess and the fix.
What broke. Why it broke. What I learned. The exact commands that put it back together. The governance frameworks I built from scratch because nobody was writing them for solo operators. The AI delegation model that lets one person run infrastructure that used to require a team of twelve. The moment the local LLM absorbed the full system state and started giving answers that actually understood the stack it was running on.
The site is the experience. The newsletter is the signal. The articles are the proof.
This isn't a company. It's a passion project that pays for itself. Inbound only. The work speaks. The honesty attracts. The reputation compounds.
If you self-host, build from scratch, or just want to watch someone construct a rolling security operations center in real time and document every mistake along the way — subscribe. Stick around. Tell the three people you've known since the Bawls era.
The building never stops.
Welcome aboard.
mpdc.dev