Appwrite

Operator's take

Appwrite sits in the backend-as-a-service category alongside Firebase and Supabase — the pitch is that you shouldn't have to stand up and glue together auth, a database, file handling, and server-side functions from scratch every time you start a project. It's the backend plumbing layer for developers building web or mobile apps who want a coherent API surface without assembling it from first principles. The distinguishing bets are open-source under a BSD-3-Clause license (so self-hosting is a first-class path) and language-agnostic SDKs — you're not locked into JavaScript or a specific cloud provider.

The realistic use case is an indie dev or small team that wants to move fast on a product without a dedicated backend engineer. Appwrite hands you a menu of login methods (email/password, OAuth2 across many providers, SMS, magic URL, email OTP, JWT, anonymous, and MFA), a document database with real-time subscriptions, file storage with built-in encryption, serverless functions, and now Appwrite Sites — a Vercel-style hosting layer for static, SSR, and CSR frontends — all accessible through a single console. The AI/agent angle has gotten real too: Appwrite ships an MCP server and Skills layer so AI coding agents can interact with your backend directly without custom integrations. The catch is that it's still a developer tool: you'll need someone who can set up a server or a Docker container and understand API calls. It's not no-code. The free cloud tier is generous enough to evaluate and build on, but the serious self-hosted path requires real infrastructure ownership.

What it's good at

• Authentication out of the box — multiple login methods including email/password, OAuth2 (many providers), SMS, magic URL, email OTP, JWT, anonymous, and MFA; team management and granular access controls included.
• Real-time database — document store with live subscription support, built-in caching, and permission rules; handles collections with relationships and custom validation.
• File storage with security built in — upload/download management, image transformations, compression, and encryption at rest and in transit.
• Cloud functions without servers — run custom backend logic, automate workflows, and respond to system events without managing your own server infrastructure.
• Multi-channel messaging — send email, SMS, and push notifications through a single API; avoids stitching together separate vendor SDKs for each channel.
• Frontend hosting (Appwrite Sites) — deploy static, SSR, and CSR frontends directly to your domain with CDN and DDoS protection built in; keeps the whole app lifecycle on one platform.
• AI agent integration — native MCP server and Skills layer let AI coding agents (Claude Code, Cursor, Codex, etc.) interact with your Appwrite backend without custom glue code.
• Self-hosting as a real option — BSD-3-Clause license means you can run it on your own infrastructure; no vendor lock-in on the data layer.

What it's not

• Not a no-code tool — requires a developer who can work with APIs, SDKs, and either Docker or a cloud console; non-technical operators can't build on it directly.
• Not Firebase with the Google ecosystem — if your team already uses Google Analytics, Firebase ML, or GCP tightly, the integrations and tooling won't transfer here.
• Not production-ready on the free tier alone — the free cloud plan caps at one database, two functions, and two projects total; growing apps hit those limits and need the Pro plan ($25/month) or a self-hosted setup.
• Not the right pick if you need a relational SQL database — the document model is capable but Supabase or a plain Postgres instance is the better fit if SQL and row-level security are load-bearing for your project.