[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.