Hosting Supabase, long-term costs
Hey everyone,
Due to compliance reasons, our startup has to (or would greatly benefit) from moving away from Supabase's cloud service. This is mostly due to AWS being a sub-vendor.
In general EU public sectors just want to avoid american cloud (unfortunately for us devs, since its so much better).
Does anyone have experience with this? Currently we are mostly using:
- Postgres
- Supabase auth
- Supabase storage (S3)
So now im basically exploring 2 options:
- Ditching supabase entirely
- "Self-host" supabase, on european cloud providers
I really like Supabase, so that's why im tempted towards the 2nd, I guess I want to know, how bad is it? I work within edtech, so the upfront implementation cost is not too big of a concern for me (we have the entire summer to work on things like this), its the recurring, long-term maintenance Im afraid of.
We really, **really** want to avoid sub-vendors on our own, so going with multiple eu-native cloud providers for the different services (auth, storage, postgres) would be really deferred.
Concrete questions:
- Has anyone here done something similar? Did you regret it? Or is it fine?
- How much ongoing maintenance does the self-hosted stack require?
- Does anyone know of good european alternatives, if *not* deciding to host the Supabase stack?
Apologize in advance if similar questions are asked here every day.
EDIT: To be clear, we are **not** doing this to cut costs. The operational cost of "self" hosting will likely far outweigh any reduction in direct cloud bill. Supabase's service is genuinly very good, and if they were EU-soveirgn, we wouldnt even consider switching away.