Most "self-hosting" articles are basically a list of Docker Compose files. They tell you what to run. They don't tell you why the smart money is moving away from managed cloud services — or what a real production stack looks like when you do it right. The shift isn't about being cheap. It's about control. Your data. Your pipeline. Your infra. No vendor lock-in, no surprise pricing changes, no terms-of-service update that kills your product overnight. Here's the stack I'd build today if I were starting from scratch — tools that are production-grade, actively maintained, and built by teams who eat their own cooking. How I picked these I'm not ranking by GitHub stars or Hacker News upvotes. I'm ranking by: Production-readiness — does it hold up under real load, or is it a weekend project with a pretty README? Migration story — can you replace an existing paid service without a 3-month rewrite? Maintenance burden — how much ops work does it create vs. eliminate? Privacy posture — does it send anything home?…