[avolcano]

I think this is a bit disingenuous to post. Your own website[1] says:

> Supabase is an amalgamation of 5 open source tools (and growing). We don't have a simple way to install everything on a single server, but we will work on this as soon as we have a stable set of features.

Now, it's fair to say "we don't have a simple way" is different from "we don't have a way at all," but you clearly discourage users from trying to self-host right now for any reason beyond developing Supabase itself (which appears to be the use of the Docker Compose setup you have linked).

Personally: I'd love for Supabase to have a clear guide for self-hosting, including system requirements for single-box hosting, advice (even without code or tooling!) for scaling your setup, etc. Until then, it's just another hosted service with vendor lock-in, no different from Firebase to me.

[1] https://supabase.io/docs/faq#how-do-i-host-supabase

[kiwicopple]

That's fair, to be honest those docs were written a long time ago and haven't been updated. We're releasing our CLI tomorrow, which is part of the "self hosting" story, so I'll update these docs with some detailed instructions.

Thanks for the candid feedback.

[yclurker]

>> It's just another hosted service with vendor lock-in, no different from Firebase to me

Couldn't agree more. They are real shady every time self hosting comes up.

See here ==> https://news.ycombinator.com/item?id=26637360