Supabase vs Appwrite

Supabase and Appwrite are the two names that come up first when you want a self-hosted "backend in a box" — auth, a database, storage, functions, realtime — without writing that plumbing yourself. Both bill themselves as open-source Firebase alternatives, both ship official Docker setups, and both cover the same core feature list. The split between them is not features so much as philosophy: how much SQL you want to write, and how much infrastructure you are willing to run to get there.

Postgres-native vs batteries-included

Supabase starts from PostgreSQL and builds outward. The database is not hidden behind an abstraction — it is the product. Auth, storage metadata, and realtime subscriptions all live in the same Postgres instance you can psql into, query directly, extend with extensions, and protect with row-level security policies. The backend is Apache-2.0 licensed and built on TypeScript services in front of that Postgres core.

Appwrite starts from the API and builds down to whatever storage engine is convenient — currently MariaDB, wrapped in a document-style abstraction. You create collections, define attributes, and query through Appwrite's SDKs rather than writing SQL. The project is BSD-3-Clause licensed and its services are written in PHP. The pitch is a single, consistent surface across every service, with less need to understand the database underneath it.

Both catalog entries land at the same 4 GB RAM floor and ship as Docker stacks, but the shape of what you're running is genuinely different, which shows up most in the next section.

Database model & data access

This is the decision that should drive the pick. Supabase gives you direct Postgres access: real SQL, joins, foreign keys, views, and the extension ecosystem (pgvector for embeddings, PostGIS for geospatial data, and so on). If your team already thinks in SQL, or you know you'll eventually need a complex join or a custom extension, Supabase gets out of your way faster.

Appwrite's database is document-oriented at the API layer — collections and documents, filtered queries, permission rules per document — even though MariaDB sits underneath. That abstraction is easier to pick up if you've never written SQL, and it keeps the mental model consistent with Appwrite's other services. The trade-off is that anything relational — multi-table joins, ad hoc reporting, analytical queries — is harder to express than it would be in raw Postgres.

Features & services

The feature lists are close to a match on paper: both offer authentication, a database, file storage, serverless functions, and realtime subscriptions. Appwrite rounds its suite out with messaging and a "Sites" feature for hosting full-stack frontends, aiming to be the one console you open for everything. Supabase leans on its Postgres foundation instead — auto-generated REST and GraphQL APIs over your schema, Edge Functions, and the same row-level-security model securing every table by default.

Neither is missing a core primitive the other has; the difference is where each project chose to go deep. Supabase goes deep on the database. Appwrite goes deep on presenting a uniform API across every service.

DX & ecosystem

Supabase's Postgres foundation gives it an edge in ecosystem reach: any tool, ORM, or extension built for Postgres works against a Supabase database with little friction. It's also the more widely adopted of the two as a Firebase alternative, which means more community answers and third-party integrations when something goes sideways.

Appwrite's SDK coverage is broad across web, mobile, and server platforms, and its console is approachable without a database background — useful for a team that doesn't want to reason about SQL. The trade-off is a smaller surrounding ecosystem and less flexibility once a project outgrows the document abstraction.

Self-host footprint

Both report the same 4 GB RAM floor in this catalog, but the shape of the deployment differs. Appwrite runs as a single Docker Compose stack that brings up the full platform — database, auth, storage, functions, and admin console — in one command, which is reflected in its friendlier 3 out of 5 difficulty rating. Supabase's official self-host setup is a multi-container stack — Postgres, PostgREST, an auth service, Realtime, Storage, and Kong as the API gateway among them — each with its own container to configure and keep healthy, which lands it at 4 out of 5. Neither is a bad afternoon, but Appwrite's single-stack story is the simpler one to stand up and operate day to day.

Licensing

Both are permissively licensed and safe to self-host without copyleft concerns: Supabase is Apache-2.0, Appwrite is BSD-3-Clause. Neither license carries the network-use disclosure obligations of an AGPL project, so this dimension is close to a wash — pick on architecture and features, not license risk.

Which should you self-host?

Pick Supabase if…

• You want direct Postgres access — real SQL, joins, extensions like pgvector — rather than an API abstraction over the database.
• You value the larger ecosystem: more integrations, more community prior art, and tooling that already speaks Postgres.
• You don't mind running a multi-container stack and a slightly steeper setup in exchange for that flexibility.

Pick Appwrite if…

• You want a single, all-in-one stack that's easier to stand up and operate, with one console covering every service.
• You'd rather work through a document-style API than write SQL directly, especially with a team that isn't SQL-fluent.
• You want messaging and site-hosting bundled in alongside the core auth/database/storage/functions set.

Running either on a VPS

Both land at the same 4 GB RAM floor, so sizing isn't the deciding factor — architecture is. Supabase's multi-container stack rewards comfort with Docker Compose and Postgres administration; Appwrite's single-stack installer gets you to a running console faster with less to reason about underneath. Whichever you choose, back up the database regularly — it holds your schema, your users, and your files' metadata — and the step-by-step guides linked below cover the official Docker setup for each.