We did a write-up on the tech stack and some of the approaches we considered for sharing code between our Platform and the Self-Hosted versions here: <a href="https://supabase.com/blog/2021/11/30/supabase-studio" rel="nofollow">https://supabase.com/blog/2021/11/30/supabase-studio</a><p>We aim to get these to parity with each other, excepting some billing/server management features.<p>A big shout out to Sentry who do served as a good model for us (<a href="https://develop.sentry.dev/sentry-vs-getsentry/" rel="nofollow">https://develop.sentry.dev/sentry-vs-getsentry/</a>)
Been using Supabase for a while and love it. It’s got that feel of a really well thought out service where things just work how you’d want it to and new features arrive that you actually want and make life easier. It’s one of a handful of companies I saw and immediately wished I could invest in.<p>This announcement doesn’t really matter to me since I really like having a hosted service. But it’s good to know it’s future proof - ie if Supabase go out of business or a project takes off and I want to self host with all the good stuff then I can.
Been using SupaBase for a couple of months now on a side project and it’s very nice. I’ve used Firebase extensively and it’s so nice to have a similar offering using SQL for the DB layer. Good to see them sticking to the open source ethos.
For those who need a clickable link to the project: <a href="https://supabase.com/" rel="nofollow">https://supabase.com/</a>
I wanted to use supabase for one of my pet projects, but, unfortunately, the egress fee is just way to high, $0.09 per GB. I am not sure if it is viable for any serious project.
Just installed via the developer quickstart <a href="https://github.com/supabase/supabase/tree/master/studio#developer-quickstart" rel="nofollow">https://github.com/supabase/supabase/tree/master/studio#deve...</a>
but getting a connection refused error.<p>I'm assuming it's because of the db. Any advice / guide on setting that up?
I would really like to use supabase as an alternative for Firestore. Sadly, row level security on realtime, which is the killer feature of Firestore, does not exist.