An Appwrite alternative where every project is plain Postgres
Appwrite gives you auth, databases, storage, functions and hosting in one open-source platform. Its default database, TablesDB, is reached through the Appwrite API; a dedicated PostgreSQL database is a separate paid item. Scribase starts from the other end: every project is Postgres 17, on the free plan too, and auth, storage, realtime and functions sit on top of it. Pick Scribase when you want SQL and row level security. Stay on Appwrite when you want open source and self-hosting.
Last checked November 17, 2026.
The short answer
- Pick Scribase when you want to write SQL, use joins and Postgres extensions, and protect rows with row level security policies.
- Pick Scribase when your code already uses supabase-js: it works with the URL and key swapped.
- Stay on Appwrite when open source and self-hosting matter, when you need a signed BAA or SOC 2, or when you use Appwrite Sites hosting and Messaging.
Appwrite and Scribase, side by side
| Appwrite Cloud | Scribase | |
|---|---|---|
| Database | TablesDB by default, through the Appwrite API. Dedicated PostgreSQL or MySQL from $10 a month per database. | Postgres 17 in every project, including the free one |
| Query language | Appwrite SDK queries on the default database | SQL, plus a REST API that supabase-js calls |
| Access rules | Appwrite permissions on rows and tables | Postgres row level security policies that read auth.uid() |
| Free plan | 1 organization and 2 projects. A project freezes and the console becomes read-only when it reaches a limit. | 1 project free with no time limit (0.5 GB database, 1 GB files, no card) |
| Billing unit | Plans apply to the organization; resources are allocated per project | Per project: Hobby $5 a month, Pro $25 a month |
| Point-in-time recovery | On dedicated databases, +20% of the base price | Included |
| Open source and self-hosting | Yes, open source and free to self-host | Core is not open source. Licensed self-hosted deployment only. |
| Compliance | SOC 2 Type II; a BAA can be signed | None yet |
Sources: Appwrite: Pricing, Appwrite docs: Free plan, Appwrite docs: Pro plan, Scribase: Pricing
What plain Postgres changes
- One query can join tables, aggregate and filter. You are not limited to the query operators of an SDK.
- Access rules live in the database as policies, so they hold for every client and every query.
- Extensions are available: pgvector for embeddings, pg_cron for schedules, pgmq for queues, full text search.
- Your data leaves as a standard Postgres dump that any Postgres host can load.
- Every database can branch: a copy-on-write branch carries the parent rows and gets its own URL and keys.
alter table notes enable row level security;
create policy "owner reads own notes"
on notes for select
using (user_id = auth.uid());Moving from Appwrite
There is no Appwrite importer. Scribase imports from Supabase, Firebase and any Postgres connection string; Appwrite is not on that list. A move is manual, and it is real work:
Step 1
Create the project
One command creates Postgres and Auth and writes the URL and anon key into your .env file.
Creates the backend and writes the URL and anon key into your .env filesh npx scribase initStep 2
Recreate the schema as SQL tables
Each Appwrite table becomes a Postgres table. Relationships become foreign keys.
Step 3
Export your rows and load them
Export from Appwrite with its API or CLI, then insert through a migration or the REST API.
Step 4
Rewrite permissions as policies
Appwrite permissions become row level security policies. Nothing is readable until you write them.
Step 5
Move users
Users get new ids, so match old rows to new users by email. Password users reset their password on first sign-in.
What Scribase does not do
- One region today (Frankfurt). If your users or your compliance rules need another region, this is not the right host yet.
- Direct Postgres connections from the internet (ports 5432 and 6543, for psql or pg_restore) are not open yet. Migrations, the console SQL editor and the HTTP serverless driver work today.
- No compliance certifications yet (no SOC 2, no HIPAA BAA).
- The core is not open source. You can export everything, and a licensed self-hosted deployment exists, but you cannot clone the server from a public repository.
- No static site hosting and no SMS or push messaging product like Appwrite Sites and Appwrite Messaging. Transactional email is a separate Resend-compatible API in the same account.
Questions people ask
What is a good Appwrite alternative with Postgres?
Scribase and Supabase both give every project a Postgres database with auth, storage, realtime and functions on top. Scribase is priced per project and keeps one project free with no time limit; a quiet project scales to zero and wakes on the next request.
Does Appwrite use Postgres?
As of 2026-11-17, Appwrite's pricing page lists TablesDB as the default database type and PostgreSQL as a dedicated database option, from $10 a month per database. On Scribase every project is Postgres 17, including the free one.
How many projects does the Appwrite free plan allow?
Appwrite's docs state that each Appwrite Cloud account can have one organization and 2 projects on the Free plan. When a free project reaches a resource limit it freezes and the console runs in read-only mode until the next billing cycle or an upgrade.
Can I migrate from Appwrite to Scribase automatically?
No. Scribase has importers for Supabase, Firebase and plain Postgres, not for Appwrite. You recreate the schema as SQL tables, export and load the rows, rewrite permissions as row level security policies, and users reset their passwords.
Is Scribase open source like Appwrite?
No. Appwrite is open source and can be self-hosted for free. The Scribase core is not open source; the CLI and client tooling are public, your data exports as standard Postgres, and a licensed self-hosted deployment exists.