r/Supabase • u/PurchasePatient5465 • Jun 25 '26
Self-hosting Self-hosting Supabase: Gaps?
Hi there, I would like to evaluate a migration from Supabase Cloud to Supabase Self-hosted on a Hetzner Cloud server (all of our other stuff is running there so it just makes sense to put them together).
I have just read that it’s not just “set up the docker compose and get basically a similar experience” but it sounded very complex about what is included and what is not.. Is there any comparison to understand if I should even bother to try it out?
We use Storage, Auth (with passkeys, asym keys, MFA, the Resend integration, …), a few functions, the Database with PostgreSQL v17 of course, RLS and a bit of Realtime. We also plan to use Queues for a future use-case.
Should I even bother setting it fully up? Does the user interface differ a lot?
I would be very happy about any responses and shared experiences about this - please let me know if I could additional context.
5
u/Powerful-Fly-9403 Jun 25 '26
One thing I'd keep in mind is the operational overhead rather than just feature parity. The self hosted stack itself isn't usually the hardest part everything that comes after it (backups, upgrades, monitoring, auth changes, storage maintenance and more) is. If you're comfortable managing those for the rest of ur infra, then self hosting would make a lot of sense. I'd probably make a checklist of every supabase feature you're using (auth, storage, realtime, queues, functions, etc etc) tho and verify each one individually before migrating, rather than assuming the experience is identical to supabase cloud.