5 ms·

co-founder here, happy to answer any questions. We're currently in alpha - app.supabase.io We also have a lot more to build, so to reward you for your patience

co-founder here, happy to answer any questions. We're currently in alpha - app.supabase.io We also have a lot more to build, so to reward you for your patience we are completely free right now

tmikaeld 6y ago
How much cheaper than Firebase do you expect to be when you launch?
- kiwicopple 6y ago
  Good (leading) question :) It's hard to answer because we're so early, so the most honest answer I can give is: i don't know. Firebase just changed their pricing to "pay as you go". I need to dig into their pricing to give a good comparison but I think we will be much cheaper for the IAAS aspect - we will try offer more value via the dashboard (i.e. we want to build an Airtable-like interface for non-techies to use), and charge on that aspect. One more thing - we personally find predictable pricing to be an important feature of IAAS and therefore will probably price differently to firebase's usage model.
  - tmikaeld 6y ago
    Or you can do what many usage-models do, make a calculator and usage on common use-cases.
lukeramsden 6y ago
How does this compare to Postgraphile or Hasura? Or rather, how is it going to compare once you've had some time to get it out of alpha.
- kiwicopple 6y ago
  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 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) - Only Postgres: Hasura mentioned they will build for other RDBMS. We're all in on PG and some of the more advanced features (replication, High Availability) - UI/UX. We will build an interface like Airtable, so that even your non-techie friends can use it
  - pkghost 6y ago
    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.
    - pdimitar 6y ago
      Maybe they mean authorisation rather than authentication but like you, I am curious if they will elaborate further on how is Postgres RLS used.
      - lukeramsden 6y ago
        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/ https://www.graphile.org/postgraphile/security/
    - lukeramsden 6y ago
      As far as pedantry goes, wouldn't conflating RLS and AuthN be wrong, but AuthZ sort-of correct? At least, that's my understanding.
    - kiwicopple 6y ago
      This is what we are targeting: http://postgrest.org/en/v7.0.0/auth.html http://postgrest.org/en/v7.0.0/auth.html We are still doing a heavy assessment of whether this model can be generalised for everyone. It covers the details of both authentication and authorization - we are just building a nice/easy way to enable this for everyone (probably using the same model as Postgraphile: https://www.graphile.org/postgraphile/security/ https://www.graphile.org/postgraphile/security/)
      - mindhash 6y ago
        i have seen oracle heavily employing RLS for authorization in e-business suite. and it made things so much easier.
yannikyeo 6y ago
How does app handle authn?
- kiwicopple 6y ago
  see my other comment > We want to nail the auth and we're looking at leveraging Postgres' native Row Level Security. This is a tricky task to "generalize" for all businesses but we have some good ideas (we're discussing in our repo if you want to follow - https://github.com/supabase/supabase https://github.com/supabase/supabase)
imedadel 6y ago
About the choice of the database. Why did you decide to go with PSQL instead of a NoSQL database as Firebase does? Doesn't that affect your scalability? Otherwise, great project!
- kiwicopple 6y ago
  Actually we chose Postgres specifically because it is scalable. I had to switch from Firebase in my previous company because we hit some scaling limits. Postgres handles the scale no problem - it's crazy the performance improvement we saw (and it's ACID) The trickiest part was the realtime functionality - https://github.com/supabase/realtime https://github.com/supabase/realtime
dexterbt1 6y ago
Any link to deployable dockerized versions?
- kiwicopple 6y ago
  Theres a version here: https://hub.docker.com/r/supabase/supabase-dev https://hub.docker.com/r/supabase/supabase-dev But we will be releasing a much more robust version with docs soon!
warent 6y ago
Hey there, I like the product and think your business model is admirable. I would like to make a suggestion that you consider offering some support for your enterprise patrons. $1000+/mo is very steep for an ad even if it was a popular product. imo that should come with some amount of white glove treatment.
- kiwicopple 6y ago
  That's a good call - let me update! edit: OK added - https://github.com/sponsors/supabase https://github.com/sponsors/supabase

co-founder here, happy to answer any questions. We're currently in alpha - app.supabase.io We also have a lot more to build, so to reward you for your patience we are completely free right now

tmikaeld 6y ago

How much cheaper than Firebase do you expect to be when you launch?

kiwicopple 6y ago
Good (leading) question :) It's hard to answer because we're so early, so the most honest answer I can give is: i don't know. Firebase just changed their pricing to "pay as you go". I need to dig into their pricing to give a good comparison but I think we will be much cheaper for the IAAS aspect - we will try offer more value via the dashboard (i.e. we want to build an Airtable-like interface for non-techies to use), and charge on that aspect. One more thing - we personally find predictable pricing to be an important feature of IAAS and therefore will probably price differently to firebase's usage model.
- tmikaeld 6y ago
  Or you can do what many usage-models do, make a calculator and usage on common use-cases.

lukeramsden 6y ago

How does this compare to Postgraphile or Hasura? Or rather, how is it going to compare once you've had some time to get it out of alpha.

kiwicopple 6y ago
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 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) - Only Postgres: Hasura mentioned they will build for other RDBMS. We're all in on PG and some of the more advanced features (replication, High Availability) - UI/UX. We will build an interface like Airtable, so that even your non-techie friends can use it
- pkghost 6y ago
  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.
  - pdimitar 6y ago
    Maybe they mean authorisation rather than authentication but like you, I am curious if they will elaborate further on how is Postgres RLS used.
    - lukeramsden 6y ago
      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/ https://www.graphile.org/postgraphile/security/
  - lukeramsden 6y ago
    As far as pedantry goes, wouldn't conflating RLS and AuthN be wrong, but AuthZ sort-of correct? At least, that's my understanding.
  - kiwicopple 6y ago
    This is what we are targeting: http://postgrest.org/en/v7.0.0/auth.html http://postgrest.org/en/v7.0.0/auth.html We are still doing a heavy assessment of whether this model can be generalised for everyone. It covers the details of both authentication and authorization - we are just building a nice/easy way to enable this for everyone (probably using the same model as Postgraphile: https://www.graphile.org/postgraphile/security/ https://www.graphile.org/postgraphile/security/)
    - mindhash 6y ago
      i have seen oracle heavily employing RLS for authorization in e-business suite. and it made things so much easier.

yannikyeo 6y ago

How does app handle authn?

kiwicopple 6y ago
see my other comment > We want to nail the auth and we're looking at leveraging Postgres' native Row Level Security. This is a tricky task to "generalize" for all businesses but we have some good ideas (we're discussing in our repo if you want to follow - https://github.com/supabase/supabase https://github.com/supabase/supabase)

imedadel 6y ago

About the choice of the database. Why did you decide to go with PSQL instead of a NoSQL database as Firebase does? Doesn't that affect your scalability? Otherwise, great project!

kiwicopple 6y ago
Actually we chose Postgres specifically because it is scalable. I had to switch from Firebase in my previous company because we hit some scaling limits. Postgres handles the scale no problem - it's crazy the performance improvement we saw (and it's ACID) The trickiest part was the realtime functionality - https://github.com/supabase/realtime https://github.com/supabase/realtime

dexterbt1 6y ago

Any link to deployable dockerized versions?

kiwicopple 6y ago
Theres a version here: https://hub.docker.com/r/supabase/supabase-dev https://hub.docker.com/r/supabase/supabase-dev But we will be releasing a much more robust version with docs soon!

warent 6y ago

Hey there, I like the product and think your business model is admirable. I would like to make a suggestion that you consider offering some support for your enterprise patrons. $1000+/mo is very steep for an ad even if it was a popular product. imo that should come with some amount of white glove treatment.

kiwicopple 6y ago
That's a good call - let me update! edit: OK added - https://github.com/sponsors/supabase https://github.com/sponsors/supabase