Moved from hosted Supabase to self-hosted on a single VPS — here's what I learned after weeks in production

Most self-hosting guides show you how to get Supabase running. Not many tell you what happens after you've been running it for months with real users and real data. Here's what I've learned. The project I built MadeOnSol , a Solana ecosystem directory that tracks 950+ tools across 26 categories. The stack includes 74 Postgres tables, 100k+ real-time trade records, Google OAuth, file storage for 900+ tool logos, and Row Level Security on every table. It started on Supabase's free hosted tier. Four months ago I moved everything to a self-hosted Docker setup on a Hetzner CPX32 (8GB RAM, 4 vCPU, €15/month). Here's what I'd want to know if I were doing it again. How much resources does it actually use? This is the question nobody answers well. The default self-hosted Supabase ships with ~15 containers. I stripped it down to 8 by removing Studio, Edge Functions, Analytics, Vector, Meta, and the Deno cache. None of them were doing anything useful in production. Here's what the remaining servi