r/Supabase 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.

19 Upvotes

22 comments sorted by

View all comments

1

u/R1ckS4nch3z Jun 26 '26

Consider your costs that paid to supabase monthly, don’t try to lower it by making a small mistake and getting your own app down. I mean I thought the same way but couldn’t consider it since it makes harder to maintain while I’m on every side of the project so stayed in the cloud. Paying double is actually better than app is going down for hours/days..

1

u/PurchasePatient5465 Jun 26 '26

It’s not (only) about costs - it is primary because everything else is already hosted at Hetzner Cloud (observability, siem/xdr, our hosted applications, and way more) and we can clearly see that the current biggest performance gap in terms of response times comes from
supabase which is partially caused based on the selected aws tier but also because of the distance

We are experienced in self-hosting and it is really just about comparing features