|
|
|
|
|
by CobrastanJorji
1905 days ago
|
|
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. |
|
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.