Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Storage is now available in Supabase (YC S20)

supabase.io

Post reply on HN
Print view View original

61–70 of 82 posts

Re: Storage is now available in Supabase (YC S20)

#61

Post by [deleted] »

frakkingcylons wrote: post #56
yclurker wrote: post #26

Supabase is NOT open source and it's Founders are highly unethical. Here’s why. We heavily rely both on postgres and Firebase. And when Supabase came as an “open source” Firebase alternative (also a YC company), naturally we were excited. However ever since the launch, time and again the community has kept asking for a self-hostable version to no avail. And community is requesting that since not all of Supabase is op…

All of their code is available with OSI approved licenses. It’s factually open source. You’re making huge mental leaps about their intentions. There’s no need for the vitriol by calling their team “highly unethical”.

[deleted]

Re: Storage is now available in Supabase (YC S20)

#62

Post by CobrastanJorji »

kiwicopple wrote: post #37
smalltalks wrote: post #35

Earlier quoted context omitted.

Everything said above is true. Supabase started Open Source , their GitHub repo had tutorials on how to host the platform yourself with a bit of documentation. Basically from what I understood they've been growing SO FAST ( they raise 10+$M IIRC ) they had to make a choice between "Growth" or "Integrity". Obviously it's a YC company , the market they're going after is massive , they chose growth over integrity and do…

Every component of Supabase is MIT, Apache 2, or Postgres licensed - apart from the dashboard The code to self host it is in our main repo: https://github.com/supabase/supabase/tree/master/docker I do think we could have better/cleared docs, which we can fix up tomorrow. Re investment: we raised 6M, and we are under no pressure to trade our integrity for growth. We have open-source-friendly and patient investors (Moz…

Is there a difference between Firebase's "open source" and Suprabase's "open source"? Is Suprabase more open than Firebase in some manner, or does "an open source Firebase alternative" just mean "a Firebase competitor that also open sources its client side tools?" Is some part of the Firebase code closed source or less "Open" where the Suprabase equivalent is not? I haven't used Firebase much, so maybe I'm missing a big distinction.

Re: Storage is now available in Supabase (YC S20)

#63

Post by ignoramous »

crubier wrote: post #60
zapita wrote: post #38

Earlier quoted context omitted.

Supabase is definitely open-source. To the founders of supabase: don’t let people like this deter you. Their misplaced anger and self-righteousness says more about them than it says about you. If your software is good, we will use it. If it’s not, we won’t. There’s no need for poisonous behavior either way.

Supabase dashboard (which is the core of the actual product, the rest being open source tools) isn't open source or self hostable.

I think most F/OSS YC companies are adopting the GitLab model. Which is why may be they have put their UI code behind closed doors, because the "buyer-based open core" business model is, in part, based on it: https://www.heavybit.com/library/video/commercial-open-sourc...

Re: Storage is now available in Supabase (YC S20)

#64

Post by monstermachine »

CobrastanJorji wrote: post #62
kiwicopple wrote: post #37

Earlier quoted context omitted.

Every component of Supabase is MIT, Apache 2, or Postgres licensed - apart from the dashboard The code to self host it is in our main repo: https://github.com/supabase/supabase/tree/master/docker I do think we could have better/cleared docs, which we can fix up tomorrow. Re investment: we raised 6M, and we are under no pressure to trade our integrity for growth. We have open-source-friendly and patient investors (Moz…

Is there a difference between Firebase's "open source" and Suprabase's "open source"? Is Suprabase more open than Firebase in some manner, or does "an open source Firebase alternative" just mean "a Firebase competitor that also open sources its client side tools?" Is some part of the Firebase code closed source or less "Open" where the Suprabase equivalent is not? I haven't used Firebase much, so maybe I'm missing a…

Firebase is completely closed source and make it extremely hard to migrate any moderate size project.

Supabase builds on open source parts that everyone is already familiar with. Postgres for data store instead of firestore (which is a proprietary nosql Google cloud database with many quirks to keep you in). GoTrue for Auth which is an open source project by netlify. Real-time to provide Postgres changes over sockets open sourced by them. There are many parts which make up "supabase".

Supabase hosting provide a unified experience through their dashboard and manage all these parts for you. That isn't open source.

The actual UI kit for that is open source, though.

Dashboard doesn't stop you from migrating your backend infrastructure somewhere else. It does result in degraded developer experience which can be the biggest distinction.

Re: Storage is now available in Supabase (YC S20)

#65

Post by kiwicopple »

CobrastanJorji wrote: post #62
kiwicopple wrote: post #37

Earlier quoted context omitted.

Every component of Supabase is MIT, Apache 2, or Postgres licensed - apart from the dashboard The code to self host it is in our main repo: https://github.com/supabase/supabase/tree/master/docker I do think we could have better/cleared docs, which we can fix up tomorrow. Re investment: we raised 6M, and we are under no pressure to trade our integrity for growth. We have open-source-friendly and patient investors (Moz…

Is there a difference between Firebase's "open source" and Suprabase's "open source"? Is Suprabase more open than Firebase in some manner, or does "an open source Firebase alternative" just mean "a Firebase competitor that also open sources its client side tools?" Is some part of the Firebase code closed source or less "Open" where the Suprabase equivalent is not? I haven't used Firebase much, so maybe I'm missing a…

> Is some part of the Firebase code closed source or less "Open" where the Supabase equivalent is not?

All of the Firebase backend is proprietary, and their client code is open source.

The Supabase backend is here: https://github.com/supabase/supabase/tree/master/docker

This is the set up we use for every project on our hosted platform. These backend tools are either built by Supabase, supported by Supabase (we employ maintainers), or licensed with OSI-compliant licenses.

Our client libraries are all open source, Apache 2.0 licensed.

Supabase is open source in every definition of the word. I think the problem is our self-hosting docs, so we'll spend the day improving this.

Re: Storage is now available in Supabase (YC S20)

#66

Post by turtlebits »

yclurker wrote: post #26

Supabase is NOT open source and it's Founders are highly unethical. Here’s why. We heavily rely both on postgres and Firebase. And when Supabase came as an “open source” Firebase alternative (also a YC company), naturally we were excited. However ever since the launch, time and again the community has kept asking for a self-hostable version to no avail. And community is requesting that since not all of Supabase is op…

Realtime seems to be the "magic" part of Supabase, and the code is there as well as a docker image.

The rest are other open source projects. Are you really expecting them to provide their full stack including user management and billing?

Re: Storage is now available in Supabase (YC S20)

#67

Post by CobrastanJorji »

kiwicopple wrote: post #65
CobrastanJorji wrote: post #62

Earlier quoted context omitted.

Is there a difference between Firebase's "open source" and Suprabase's "open source"? Is Suprabase more open than Firebase in some manner, or does "an open source Firebase alternative" just mean "a Firebase competitor that also open sources its client side tools?" Is some part of the Firebase code closed source or less "Open" where the Suprabase equivalent is not? I haven't used Firebase much, so maybe I'm missing a…

> Is some part of the Firebase code closed source or less "Open" where the Supabase equivalent is not? All of the Firebase backend is proprietary, and their client code is open source. The Supabase backend is here: https://github.com/supabase/supabase/tree/master/docker This is the set up we use for every project on our hosted platform. These backend tools are either built by Supabase, supported by Supabase (we emplo…

Ah, gotcha. So Supabase has backend that is also open source which could theoretically be used for self hosting? Yes, that is a difference. It wasn't clear to me from the docs. Thanks!

Re: Storage is now available in Supabase (YC S20)

#68

Post by turtlebits »

smalltalks wrote: post #35
yclurker wrote: post #26

Supabase is NOT open source and it's Founders are highly unethical. Here’s why. We heavily rely both on postgres and Firebase. And when Supabase came as an “open source” Firebase alternative (also a YC company), naturally we were excited. However ever since the launch, time and again the community has kept asking for a self-hostable version to no avail. And community is requesting that since not all of Supabase is op…

Everything said above is true. Supabase started Open Source , their GitHub repo had tutorials on how to host the platform yourself with a bit of documentation. Basically from what I understood they've been growing SO FAST ( they raise 10+$M IIRC ) they had to make a choice between "Growth" or "Integrity". Obviously it's a YC company , the market they're going after is massive , they chose growth over integrity and do…

They provide a Docker image, Dockerfile and a docker-compose to run the whole stack.

I'm assuming it should be relatively easy to point their client at your own instance and they should work.

What more do you want?

Re: Storage is now available in Supabase (YC S20)

#69

Post by kiwicopple »

nicoburns wrote: post #45
smalltalks wrote: post #35

Earlier quoted context omitted.

Everything said above is true. Supabase started Open Source , their GitHub repo had tutorials on how to host the platform yourself with a bit of documentation. Basically from what I understood they've been growing SO FAST ( they raise 10+$M IIRC ) they had to make a choice between "Growth" or "Integrity". Obviously it's a YC company , the market they're going after is massive , they chose growth over integrity and do…

Why do you need a firebase clone? Can't you just use postgres the traditional way?

Supabase started because we open sourced a "change data capture" server on top of Postgres[0]. We then chatted developers to see if they wanted to use it. In our conversations, many of the developers were using Firebase because it was "just easier" to get started.

We really like Postgres, so we decided to make it as easy to get started as Firebase. We aren't modifying Postgres, or trying to turn it into something proprietary. We want migration to/from to a simple pgdump wherever possible. We provide some tooling around it to make it a better experience (for example, auto-generated APIs using PostgREST).

[0] https://github.com/supabase/realtime

Re: Storage is now available in Supabase (YC S20)

#70

Post by kiwicopple »

eloff wrote: post #54
kiwicopple wrote: post #15

Earlier quoted context omitted.

wow, that's a glowing recommendation. Thanks for the kind words. We have a long way to go to catch up with Firebase on most features, but of course we are benefiting from all the hard work that other OSS tools have already delivered. Postgres does most of the heavy-lifting, PostgREST is amazing, and Netlify's GoTrue server is a key piece of our architecture.

I'm curious about GoTrue, isn't that MySQL only? So do you guys run MySQL for the users database, or?

We run a fork of GoTrue, using the migrations in this PR:

https://github.com/netlify/gotrue/pull/254

tbh, our fork[1] has deviated a bit from Netlify's so we need to spend some time with them upstream'ing any changes that they would want to merge (perhaps magic links, Azure logins, OAuth scopes).

Long term, I think we will need to run 2 different forks because we have different requirements for multi-tenant. So the benefit here would be sharing "OAuth providers" (eg, if we add Okta, we upstream it, if they add Twitter logins, we pull it)

[1] https://github.com/supabase/gotrue

Post reply on HN