My Homeserver Is Overkill. That's the Point.
I run Kubernetes at home. I have DNS automation, persistent volumes, and enough moving parts to make a normal person ask, "Why not just one docker-compose file?"
Fair question. The honest answer: because I enjoy this. The practical answer: because this setup gives me control, repeatability, and a place to test ideas before I trust them elsewhere.
Yes, it is overkill
Most personal websites do not need a cluster. Mine doesn't either. But "need" is not the only metric. I use this environment to practice operations the same way I'd run production services: clear deploy flow, persistent storage rules, and fewer hidden surprises.
Overkill becomes useful when it is intentional. I'm not adding complexity just to look clever. I'm building a system I can understand end to end and maintain without guesswork.
What I actually get from it
First: confidence. When something breaks, I know where to look. Second: speed. Once the base is solid, shipping a new service is mostly routine. Third: ownership. My data, my stack, my failure modes.
Also, it's fun. There's no substitute for seeing a service go from idea to domain name on your own infrastructure. It's nerdy, sure. It's also satisfying in a very concrete way.
The part nobody advertises
Self-hosting has tax: maintenance, updates, backups, and the occasional weird outage at inconvenient hours. If you hate that, keep it simple and outsource more. If you like learning systems deeply, this is a great trade.
How I think about it now
I don't optimize for "minimal setup." I optimize for "I can run this calmly six months from now." That usually means boring defaults, explicit conventions, and documenting decisions when they matter.
So yes - my homeserver is overkill. It's also one of the most useful things I maintain.