Both are great products, here's my biased (obviously) way of choosing between them:

- Appwrite is really focused on a simplistic experience. If you check out our SDK documentation, we try to keep everything dead simple.

- Supabase allows more verbose control over their PostgreSQL instance, i.e. you're actually writing SQL and interacting through a SQL console. This might be your cup of tea. They also use Deno for their cloud function equivalent, which is cool if you love Deno.

I would say Supabase is more opinionated, we try to give more options. Neither is necessarily better, there are pros and cons that you can decide on.

Other than that, Appwrite does some things that I find special.

Appwrite is simple to self-host. Like really simple. Like a single line of Docker command simple:

docker run -it --rm \ --volume /var/run/docker.sock:/var/run/docker.sock \ --volume "$(pwd)"/appwrite:/usr/src/code/appwrite:rw \ --entrypoint="install" \ appwrite/appwrite:latest

This gives you the full Appwrite experience for local/dev environments and you only need a few more environment variables to be production-ready.

We try to make Appwrite agnostic to your tech stack. You can use or disable any of the services when self-hosting, saving resources on your precious servers. You can integrate with frontend, backend, or both, or just use a single service, like our function runtimes.

We support a ton of SDKs, and we're always adding more. Our vibrant community makes this possible.

We have a lot of languages supported for Appwrite Functions, not just Deno ;) We have lots of storage adaptors you can choose from, or local storage if you want to keep all your data. We will support MANY databases (you can contribute your own, too).

I hope that helps, it really is down to personal preference, developing on the platforms feels very different. Try both!