Appwrite Review

Appwrite describes itself as an MCP and agent-first, open-source platform for building and scaling apps. The product is a set of modules behind one console and one API: Auth (email, SMS, OAuth, anonymous sessions, magic URLs), Databases (its own database plus managed PostgreSQL and MySQL options), Storage (compression, encryption, image transformations, access control), Functions (serverless functions with isolated runtimes and event-driven execution), Sites (static, SSR, and CSR frontends deployed from Git with instant previews), Messaging (email, SMS, and push through one service), Firewall (traffic rules and abuse controls), Realtime (subscribe to events across a project), and an MCP server that lets coding agents such as Cursor or Claude Code operate on a live project. Client and server SDKs cover the common web, mobile, and backend languages. The cloud and the self-hosted build are the same software, so what you prototype on the Free cloud plan can be moved to your own infrastructure. The repository is licensed BSD-3-Clause, a permissive license with no open-core split visible in the README.

Self-hosting needs Docker. The README gives a single docker run command that mounts the Docker socket and an appwrite folder and runs the installer image (version 2.5.0 at the time of review), with variants for Unix, Windows CMD, and PowerShell. The installer starts a setup wizard on port 20080 that is bound to localhost only and prints a one-time installer secret; you open the printed URL (or send the x-appwrite-installer-secret header) to finish setup, and for a remote server you tunnel to 127.0.0.1 over SSH. After installation the console is at http://localhost, and on non-Linux hosts the first start can take a few minutes. The README also covers a Docker API version mismatch error, upgrading from older versions, and one-click setups on partner platforms. The stack is several containers rather than a single binary, so plan for a server with enough memory and for operating a Docker host. We did not run the installer ourselves.

Everything is managed from a web console: you create a project, add platforms (web, Flutter, Apple, Android), and configure auth providers, databases, buckets, functions, and sites from one navigation. That consolidation is the main experience argument for Appwrite over assembling separate services. The README is notably agent-oriented: the hosted MCP server is presented as included on Cloud with no local install, and the Getting Started section has a dedicated Agents part next to SDKs. This section draws on the README and documentation links, not on a hands-on session.

• Auth with email, SMS, OAuth, anonymous sessions, and magic URLs
• Databases, including managed PostgreSQL and MySQL options
• Storage with compression, encryption, image transformations, and access control
• Serverless Functions with secure isolated runtimes
• Sites for static, SSR, and CSR frontends deployed from Git
• Messaging for email, SMS, and push notifications
• Realtime subscriptions and a Firewall for abuse controls
• Hosted MCP server for coding agents

• Covers most of what Firebase covers in one self-hostable, permissively licensed stack
• Same software on the cloud and on your own server, which keeps the exit path open
• Broad SDK coverage and a modular product set you can adopt piece by piece
• Very active repository, with a push on the day of the review and about 57,700 stars

• Self-hosting means running a multi-container Docker stack, with upgrades, backups, and scaling on you
• The cloud pricing page we could read lists plan names and database prices but not the per-plan limits for the Free and Pro tiers, so you must check the live comparison table
• The README leans heavily on agent and MCP positioning, which may matter less if you only want a classic backend
• Moving an existing Firebase project over is not covered by the README, so migration effort is something to test

Self-hosting is free under BSD-3-Clause. Appwrite Cloud has a Free plan, which freezes the project when its resource limits are reached, and a Pro plan where usage beyond the included limits is charged extra; the exact limits sit in a comparison table we could not read. Databases are priced separately: Serverless has a $0 fixed fee with $10 per month of compute credits included, and dedicated databases range from $10 per month (1 core, 1 GB) to $4,099 per month (32 cores, 256 GB).

Firebase is Google's hosted backend suite with deep Android and analytics integration, a very large user base, and no self-hosting option. Appwrite covers the same ground (auth, database, storage, functions, hosting, messaging) and lets you run it on your own infrastructure under a permissive license, but it will not match Google's global infrastructure or its ecosystem of surrounding services. Teams worried about lock-in or data residency are the ones who benefit most.

• Teams that want a Firebase-style backend they can self-host
• Mobile and web developers who prefer one console and one SDK family
• Projects that need data residency or want to avoid proprietary lock-in

• Teams that rely on other Google Cloud services alongside their backend
• Anyone who does not want to operate a Docker stack
• Projects that need a specific relational feature set best served by plain PostgreSQL tooling