scribase
Comparison

Supabase vs Appwrite: Postgres by default, or open source by default

Supabase is Postgres underneath, with SQL and row level security as the access model. Appwrite is open source and self-hostable, with its own default database (TablesDB) reached through the Appwrite SDK; a dedicated Postgres or MySQL database is a separate, additionally-priced item on Appwrite Cloud. The honest framing is "SQL-first vs open-source-first," not a like-for-like swap.

Last checked November 18, 2026.

What each product actually is

SupabaseAppwrite
DatabasePostgres by default, in every projectTablesDB by default, through the Appwrite SDK; dedicated Postgres/MySQL from $10/month per database on Appwrite Cloud
Query languageSQL, with joins and aggregatesAppwrite SDK queries on the default database
Access rulesRow level security policies in SQLAppwrite permissions on rows and tables
Open source / self-hostingCore is not open source; self-hosted by written agreementFully open source, free to self-host
Auth, Storage, Realtime, FunctionsBuilt inBuilt in
ComplianceNone yetSOC 2 Type II; a BAA can be signed

Sources: Supabase: Pricing, Appwrite: Pricing

Free tier and entry pricing

Checked 2026-11-18 on each vendor's pricing page
SupabaseAppwrite
Free plan500 MB database, 1 GB storage; paused after 1 week of inactivity; limit of 2 active projects1 organization and 2 projects on the default (non-Postgres) database
Entry paid planPro, from $25/month per organization, plus per-project computePro per project; a dedicated Postgres database is a further +$10/month add-on

Sources: Supabase: Pricing, Appwrite: Pricing

When each one is the right call

  • Pick Supabase (or a Postgres-first backend like it) when SQL, joins and row level security are the point, not an add-on.
  • Pick Appwrite when open source and self-hosting matter on their own terms, or when you need a signed BAA or SOC 2 report today.
  • Pick neither, and look at a combined platform, when the want is "Postgres on the free plan too, with the API already generated from it."

Where Scribase fits

Scribase runs the same supabase-js API (Auth, Storage, Realtime, REST, Functions) that Supabase does, over Postgres 17 in every project including the free one — so Appwrite's "dedicated Postgres is a $10/month add-on" gap does not exist here: Postgres is not an add-on, it is the database. It does not match Appwrite's open-source self-hosting or its signed-BAA/SOC 2 compliance posture (see /security).

Sources: Scribase pricing

FAQ

Questions people ask

Does Appwrite use Postgres?

Not by default. Appwrite's own database, TablesDB, is reached through the Appwrite SDK. A dedicated PostgreSQL or MySQL database on Appwrite Cloud is a separate item starting at $10/month per database.

Is Appwrite open source and Supabase is not?

Appwrite's core is fully open source and free to self-host. Supabase's hosted platform runs on an open-source foundation (Postgres, PostgREST, GoTrue and others), but Supabase's own managed-platform code is not open source the way Appwrite's full stack is.

Which has better compliance certifications?

As of this check, Appwrite states SOC 2 Type II and that a BAA can be signed. Supabase and Scribase (which runs the same API) do not have these yet — see each one's own security page for the current state.

Can I migrate from Appwrite to a Postgres-based backend?

There is no automated Appwrite importer on scribase-migrate or Supabase's own tooling. Moving means recreating the schema as SQL tables, exporting rows through Appwrite's API or CLI, and reloading them through a migration.