Live data from Hacker News

Supabase (YC S20) – An open source Firebase alternative

supabase.io

111–120 of 374 posts

Re: Supabase (YC S20) – An open source Firebase alternative

#111

I am ecstatic that someone is finally taking on Firebase. As a Firebase user, I find it invaluable. Their free plan and limits are very generous. The fact they offer not only a database, but authentication, hosting and perhaps one of their biggest features besides authentication: Firebase Functions. I have API's in deployment that are solely running using Firebase Functions and using Firestore as the database. The CL…

Firebase smell the Google Maps model with its “free” for a long time plan, before turning up the price when most of the market is used to the product and are to deeply locked to the API.

Re: Supabase (YC S20) – An open source Firebase alternative

#112

Earlier quoted context omitted.

Oh wow, Supabase is in Elixir! You guys hiring?

>You guys hiring? Soon! We are joining the next YC cohort and we will hire after that Only some parts are elixir. The full stack is here: https://supabase.io/humans.txt

Apologies for shameless plug and off-topic but I am very enthusiastic about companies using Elixir.

I am a senior dev (18.5y experience in total), currently focusing on Elixir and Rust (3.5y with Elixir so far, learning Rust fast and currently making an ElixirRust bridge for the sqlite database).

I'll be checking out your page every now and then. Do post in the "Who's hiring?" thread when you are ready to hire! I'll be looking for you there as well.

Re: Supabase (YC S20) – An open source Firebase alternative

#113

Earlier quoted context omitted.

Good question - one we get asked often. We don't use GraphQL (but you can do deep-queries: https://supabase.io/docs/library/get#query-foreign-tables ) Under the hood we use PostgREST. At the same time, we may (also) offer GraphQL using Postgraphile, so people can bring their own client-library. Differences from Hasura: - Auth: we will use Postgres RLS - Realtime: we don't use triggers, we use WAL (much more scalable)…

This might be pedantic of me, but conflating RLS and auth isn't a great look. RLS is a general purpose mechanism for constraining row operations, and auth has to do with usernames and passwords and session tokens.

Maybe they mean authorisation rather than authentication but like you, I am curious if they will elaborate further on how is Postgres RLS used.

Re: Supabase (YC S20) – An open source Firebase alternative

#114

Earlier quoted context omitted.

Good question - one we get asked often. We don't use GraphQL (but you can do deep-queries: https://supabase.io/docs/library/get#query-foreign-tables ) Under the hood we use PostgREST. At the same time, we may (also) offer GraphQL using Postgraphile, so people can bring their own client-library. Differences from Hasura: - Auth: we will use Postgres RLS - Realtime: we don't use triggers, we use WAL (much more scalable)…

This might be pedantic of me, but conflating RLS and auth isn't a great look. RLS is a general purpose mechanism for constraining row operations, and auth has to do with usernames and passwords and session tokens.

As far as pedantry goes, wouldn't conflating RLS and AuthN be wrong, but AuthZ sort-of correct? At least, that's my understanding.

Re: Supabase (YC S20) – An open source Firebase alternative

#115

I am ecstatic that someone is finally taking on Firebase. As a Firebase user, I find it invaluable. Their free plan and limits are very generous. The fact they offer not only a database, but authentication, hosting and perhaps one of their biggest features besides authentication: Firebase Functions. I have API's in deployment that are solely running using Firebase Functions and using Firestore as the database. The CL…

Firebase smell the Google Maps model with its “free” for a long time plan, before turning up the price when most of the market is used to the product and are to deeply locked to the API.

Why shouldn't they charge for a great product ? When Google charges it's a problem when they don't charge it's a problem.

Re: Supabase (YC S20) – An open source Firebase alternative

#117

Earlier quoted context omitted.

This might be pedantic of me, but conflating RLS and auth isn't a great look. RLS is a general purpose mechanism for constraining row operations, and auth has to do with usernames and passwords and session tokens.

Maybe they mean authorisation rather than authentication but like you, I am curious if they will elaborate further on how is Postgres RLS used.

Probably similar in an overall sense to Postgraphile et al[0], in case you haven't seen that - although I am also interested in the specifics relating to Supabase.

[0] https://www.graphile.org/postgraphile/security/

Re: Supabase (YC S20) – An open source Firebase alternative

#119

Besides the pricing, the other painful thing about Firebase are the storage rules. Given I understand you want to give maximum control to frontend developers without having a backend, the fact that I need to reimplement them if I switch serverless is an absolute pain. What are your plan regarding this aspect. Where are we going to implement the business logic?

Did you check FaunaDB by any chance? I'm wondering whether their ABAC systems + UDFs would satisfy your needs.

I will check it thanks! Although the authentication seems too manual. That part I prefer firebase.

Re: Supabase (YC S20) – An open source Firebase alternative

#120

Earlier quoted context omitted.

Firebase smell the Google Maps model with its “free” for a long time plan, before turning up the price when most of the market is used to the product and are to deeply locked to the API.

Why shouldn't they charge for a great product ? When Google charges it's a problem when they don't charge it's a problem.

> Why shouldn't they charge for a great product ?

They should charge from the beginning.

> When Google charges it's a problem

Where is that ? It's a problem when it's abrupt.

Post reply on HN