21–30 of 82 posts
Congrats to the launch! Very impressed with the progress :) Do you have plans to add passwordless auth (either magic link or OTP - preferably OTP)?
> magic link
We have this one available here:
https://supabase.io/docs/reference/javascript/auth-signin#si...
We don't have OTP, but that's a great idea - something we can add to GoTrue (https://github.com/supabase/gotrue)
Congrats on the launch! I like how you approached adding Storage to the product/platform?, keeping the initial version minimal, yet polished. I've been following you since the public launch and I'm really impressed by your work and progress. Definitely keeping an eye as you go, Supbase is a tool that could fit really nicely in the projects I'm usually working on (fullstack web, mobile apps). I wonder what's your pers…
> what's your perspective on the GraphQL (and Prisma)?
Every Supabase project is a full Postgres instance, so you can connect Prisma to it (we provide the Postgres connection string in the Project Settings). There is a potential issue if you are using serverless functions with Postgres (because connections are expensive in Postgres), but look out for an announcement soon which will solve this ...
> I'm not really satisfied with Auth0 and would love to use something else
You can also choose to use a single part of Supabase (just the Auth). I'm biased, but I think we are a lot simpler to use. We have a long way to go to catch up to their enterprise offerings though (compliance, SOC2, etc).
Congrats on the launch! I like how you approached adding Storage to the product/platform?, keeping the initial version minimal, yet polished. I've been following you since the public launch and I'm really impressed by your work and progress. Definitely keeping an eye as you go, Supbase is a tool that could fit really nicely in the projects I'm usually working on (fullstack web, mobile apps). I wonder what's your pers…
We're quite close to the Redwood team - the community there are awesome. > what's your perspective on the GraphQL (and Prisma)? Every Supabase project is a full Postgres instance, so you can connect Prisma to it (we provide the Postgres connection string in the Project Settings). There is a potential issue if you are using serverless functions with Postgres (because connections are expensive in Postgres), but look ou…
This is the first approach that I could think of, so it's good that you also mention that -- I was slightly worried that I might be missing something. Definitely looking for the mystery announcement :)
> You can also choose to use a single part of Supabase (just the Auth). I'm biased, but I think we are a lot simpler to use. We have a long way to go to catch up to their enterprise offerings though (compliance, SOC2, etc).
Regarding simplicity, it's something that occurred to me as well and one of the selling points. The happy path for Auth0 is simple enough, but when one has slightly different use-case, it's a tad too complicated for my taste. Fortunately, I don't need enterprise features so I'll experiment with integrating my project with Supabase.
Supabase has been better in every way than Firebase. Even if it wasn’t open source it would still be a better alternative. No-sql’s main (only?) appeal is approachability; Supabase makes relational data just as approachable while avoiding the ceiling that every Firebase project seems to hit. Plus its database UI is actually usable.
Earlier quoted context omitted.
> Even if it wasn’t open source it would still be a better alternative. Well, it's not hard to imagine that, since they don't provide a way to self-host it.
Hope this helps: https://github.com/supabase/supabase/tree/master/docker
> Supabase is an amalgamation of 5 open source tools (and growing). We don't have a simple way to install everything on a single server, but we will work on this as soon as we have a stable set of features.
Now, it's fair to say "we don't have a simple way" is different from "we don't have a way at all," but you clearly discourage users from trying to self-host right now for any reason beyond developing Supabase itself (which appears to be the use of the Docker Compose setup you have linked).
Personally: I'd love for Supabase to have a clear guide for self-hosting, including system requirements for single-box hosting, advice (even without code or tooling!) for scaling your setup, etc. Until then, it's just another hosted service with vendor lock-in, no different from Firebase to me.
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 open source. If it were, community themselves would have built it. But Founders have been “milking” the words “Open Source” and ignoring the community altogether.
Here is the full story : Few weeks ago, I checked supabase self hosting documentation again ==> they were callous enough to even mention how to move away from Supabase and had no instructions to self host! Completely put off by this unethical means of taking community and words open source for granted, I prompted them about it. And their response has been to remove “How to Self host” section altogether from the website, documentation and Github. And then provided a fully watered down version of docker-compose which “is barely functional or useful” to community as it has no dashboard within it.
Whenever self hostable questions comes up, Supabase Founders cover up by providing vague answers like ==> “We are building with existing & proven OSS tools. We stitch them all together seamlessly”. When decrypted, that translates to ==> “We use open source to build our software (hey nothing special here : bazillion companies do that). There will never be a usable self-hostable solution in near future”. F** you Supabase.
Every single open source company that I can think of can be self-hosted. World class open source companies go to great lengths to ensure its always self hostable even by compiling source.
Supabase founders : You should be so ashamed of yourself for setting such low standards on what could be termed as open source.
Earlier quoted context omitted.
Hope this helps: https://github.com/supabase/supabase/tree/master/docker
I think this is a bit disingenuous to post. Your own website[1] says: > Supabase is an amalgamation of 5 open source tools (and growing). We don't have a simple way to install everything on a single server, but we will work on this as soon as we have a stable set of features. Now, it's fair to say "we don't have a simple way" is different from "we don't have a way at all," but you clearly discourage users from trying…
Couldn't agree more. They are real shady every time self hosting comes up.
See here ==> https://news.ycombinator.com/item?id=26637360
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…
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…
I can think of some open source projects are prohibitively difficult to host yourself.
I can also think of closed source projects that are easy to self host.
In any case I feel that your fervor is unjustified.
Supabase has been better in every way than Firebase. Even if it wasn’t open source it would still be a better alternative. No-sql’s main (only?) appeal is approachability; Supabase makes relational data just as approachable while avoiding the ceiling that every Firebase project seems to hit. Plus its database UI is actually usable.
When you say firebase, are you also referring to Firestore? Because Firestore is way more powerful.