Appwrite released version 2.0 of its open-source backend platform on August 31, a rebuild that replaces the engine underneath, adds five database types, and exposes storage and authentication through the S3 and OAuth standards rather than Appwrite's own interfaces. The company says existing projects keep running and nothing in the release requires a migration.
Appwrite founder and chief executive Eldad Fux set out the reasoning behind the version bump: the traditional backend-as-a-service bargain traded portability for convenience, because a project written against a proprietary SDK had to be rewritten once it outgrew the platform. Appwrite 2.0 leans on protocols developers already use, with the aim of lowering the cost of leaving.
Three changes carry that argument. Storage now answers to the S3 API and authenticates with AWS Signature Version 4, so the AWS CLI, the AWS SDKs, and S3-aware tools such as rclone work against Appwrite buckets while the same files stay reachable over the native storage API. Authentication now implements OAuth 2.1 and OpenID Connect, letting integrators point a standard client library at a discovery URL. And the platform can provision dedicated PostgreSQL and MySQL engines that speak their own wire protocols, reachable from psql or the mysql client with no Appwrite API in the path.
The database options now span five types. Alongside a schemaless store called DocumentsDB and a vector store, VectorsDB, that builds HNSW indexes for similarity search, Appwrite's release provisions PostgreSQL (version 18 by default, 17 optional) and MySQL (8.4 by default, 8.0 supported) instances, each with its own credentials, a TLS endpoint, automated backups, point-in-time recovery, and a connection pooler. Appwrite says Postgres compute starts at $10 a month and resizes between tiers without downtime, and lists PostGIS, pgvector, and pg_trgm among the supported extensions.
Two additions move Appwrite up the stack rather than further out of the way. Appwrite Firewall applies rule-based traffic control in front of a project's API, functions, and sites, and previews how many recent requests a rule would have matched before it is saved. Appwrite Domains makes the company a domain registrar, handling registration, transfers, and DNS delegation. Both are limited to Appwrite Cloud and are not part of the self-hosted Community Edition, which the company ties to its own registrar and network.
Underneath sits a new engine Appwrite calls Hyperloop B, a shift from Swoole's worker model to its coroutine scheduler that the company says delivers roughly seven times the throughput at six times lower memory on an I/O-bound workload, based on its own benchmarks. How far the portability pitch holds up depends on the parts that did not change: the database, functions, and realtime APIs most Appwrite projects are built against remain proprietary, and it is the services around them that now speak open protocols.
