Appwrite now speaks Postgres_
Run a managed PostgreSQL instance inside your Appwrite project and connect to it with psql, your ORM, and the entire PostgreSQL ecosystem.
Some workloads outgrow the abstraction over them. You want psql, your own migrations, the ORM you already picked, and the extensions your queries depend on, without taking on provisioning, backups, failover, and patching.
Today we are announcing native PostgreSQL databases in Appwrite. You pick a compute specification, Appwrite provisions the engine in your project's region, and you connect to it like any PostgreSQL server, because it is one.
Create your first database
Provisioning happens in the Console:
- In your project, go to Databases and click Create database.
- Under Choose database type, select PostgreSQL from the Native databases group.
- Under Specifications, pick the tier that fits your workload, and optionally configure read replicas and point-in-time recovery.
- Review the summary and click Create database.
The database provisions in minutes and reports ready when you can connect.
Direct access to the PostgreSQL engine
A native database gets its own hostname, credentials, and TLS out of the box:
psql "postgresql://admin:<password>@db-<hash>.<region>.appwrite.center:5432/<database>"Prisma, Drizzle, Django, Rails, Spring Boot, EF Core, and GORM run against it with no Appwrite-specific configuration, and we ship integration guides for each. Extensions like PostGIS, pgvector, and pg_trgm install per database.
This is a different product from Appwrite Databases. TablesDB, DocumentsDB, and VectorsDB are reached through Appwrite SDKs with platform permissions built in. A native PostgreSQL database has no Appwrite layer between your code and the engine, and the Appwrite SDKs do not manage its data. Your drivers do.
Managed infrastructure features
Appwrite runs the operational work that self-hosting PostgreSQL would put on your team:
- Backups and point-in-time recovery. Scheduled and manual backups, plus continuous archiving that can restore to any moment inside the retention window.
- Branches. Ephemeral copies of your database created from a storage snapshot, ideal for previews and testing against production-shaped data.
- High availability. Up to five replicas with asynchronous, synchronous, or quorum replication and automatic failover behind a stable hostname.
- Scaling. Resize compute online between eight specifications, and let storage autoscaling grow the disk before it fills.
- Connection pooling. A per-database pooler multiplexes serverless traffic, with read/write splitting when replicas are enabled.
- Network security. TLS by default, IP allowlists, and a dedicated hostname per database.
SQL tooling in the Console
You do not have to leave the Console to work with the database. The SQL editor runs queries with formatting and explain plans, the Monitor tab charts compute, connections, storage, and workload, and the Connections tab lists what pg_stat_activity reports, with actions to cancel a running query or terminate a session.
Specifications and pricing
Specifications run from $10 per month (1 vCPU, 1 GB memory, 10 GB storage) to $699 per month (8 vCPU, 64 GB memory, 3 TB storage), each with included storage and bandwidth. High availability replicas and point-in-time recovery are add-ons, priced as a percentage of the tier. The full table lives in the documentation.
Every Pro plan also comes with $10 in database credits each month. That covers the entry specification in full, so a Pro organization can run a PostgreSQL database on Appwrite without paying anything beyond the plan.
Get started
Native PostgreSQL databases are available on Appwrite Cloud today on dedicated infrastructure.
We are rolling native databases out region by region, starting with Frankfurt (fra) and New York (nyc). More regions are on the way. A database takes the region of the project that owns it, so create your project in one of these regions to try them.
