[halotrope]

Congratulations, it is well deserved! I have been using SB for the past couple months and its great! In my experience what they excel at is picking really good components (Postgres, PostgREST, Elixir, Kong, Gotrue, Logflare etc) and packaging them with little overhead into something that is much greater than the sum of its parts.

There are issues of course (slow dashboard, some inconsistencies in auth, shaky self-hosting story, a little bloated JS client libs) but in general they have a solid offering that is only getting better.

I can't stress enough how there is really nothing quite like it out there at the moment. I get that HN crowd is always very skeptical esp with the somewhat airy opensource/self-hosting story that seems a little deprioritized to handle the (probably insane) growth. The escape hatches might be a bit rusty a bit at the moment but compare that with Firebase and its a little inconvenient in SB vs a prison in FB.

I am quite optimistic about Supabase and I wish the team the best of success.

[ratg13]

>I can't stress enough how there is really nothing quite like it out there at the moment

For self-hosting, AppWrite serves essentially the same purpose except for that it doesn't force you to use postgres.

The only major advantage of supbase at the moment is that they have a functional graphql offering and paid cloud hosting.

Whoever finishes OIDC integration first will have my interest.

[kiwicopple]

> doesn't force you to use postgres

at supabase we consider this a feature, not a bug. We don't want to provide huge abstractions over a database, because any product that does will inevitably be slower than the database in it's raw state. This is the major difference between supabase and appwrite - and an important one at enterprise-scale.

Other than that, I see a lot of developer love for Appwrite and it seems like an amazing product. If it comes down to features, I'm sure we will be in roughly the same place in a couple of years - they will add cloud hosting, and we will improve our rough edges.

[halotrope]

This mirrors my experience. By making the opinionated choice for Postgres it is possible to use e.g functions and triggers to replace a lot of code that would normally live in the backend. It is quite common to come from ORM-land and treat the database as just a dumb tablestore with some keys. Which does not do justice to the incredible featureset of Postgres. All of that makes it possible to avoid writing a lot of boilerplate and was a huge productivity boost for me. YMMV ofc.

[alberth]

> shaky self-hosting story

What makes it shaky?

That's interesting to hear because it seem like the goodwill sentiment regarding Supabase is because you can self-host it.

[halotrope]

Last time I checked it there was a docker-compose file for local deployment but you had to translate that to a working production env on your own. Which would include setting up the database, setting up Kong on edge-gateway, figuring out secrets management, filehosting and updates. One could argue that this is normal hoops to jump through when deploying open source ofc. It just felt way more laborious than the communication suggested. One of the main features the "dashboard" was completely unavailable for self-hosted at the time. So you would not get quite the same experience compared to commercial (again this might be expected for OSS but is a little different from what might have been expected initially ). I just checked and it seems now there is e.g. a (unofficial) k8s deployment plan so it so things might have improved. In general it just felt like it was not the highest priority to get the self-hosted plan up to parity compared to the managed version.

I have no reason to believe that was anything other than the product not being quite ready for the aspirations of the team. There where some comments on on HN that called the Open-Source claims a marketing ploy. I strongly disagree with that notion and believe that the SB team is acting in good faith and that they will deploy some of that fresh capital to further strengthen the OSS story.

Time will tell :)

[pzduniak]

I've recently done the conversion, used Teleport to get access to the dashboard. It works pretty well and I like the fact that I can fork GoTrue / point routes at my own server-side components, rather than just Supabase.

I agree that a proper Helm chart (or a Kubernetes operator) would be ideal. Too bad it would probably also hurt their Cloud offerings.

[SOLAR_FIELDS]

I’ve used the community Helm chart and it’s nowhere near production ready. I had to spend several days configuring it to be usable in production. Which isn’t that big of a deal, but it doesn’t look actively maintained at the moment and could probably use a fork.