What Services and Features Does Appwrite Provide?
Appwrite is an open-source developer platform that bundles the backend services most apps need into one place: Auth, Databases, Storage, Functions, Sites, Messaging, Realtime, and Firewall. You'd use it if you want to build and scale an app without stitching together separate vendors for authentication, file storage, serverless logic, and hosting — and it's positioned as "MCP & agent-first," meaning AI agents in your workflow can operate on a live Appwrite project directly.
Auth
Authenticate users through multiple methods, all managed within the platform:
- Email and SMS
- OAuth providers
- Anonymous sessions
- Magic URLs
This covers the common cases where you need sign-in without building credential handling yourself.
Databases
Model, query, and scale your data. Appwrite gives you two paths:
- Appwrite databases — the built-in option
- Managed PostgreSQL and MySQL — for teams that need a specific relational engine
The stated purpose is to let you match the database to your use case and team needs rather than forcing one model.
Storage
Store files with:
- Compression
- Encryption
- Image transformations
- Access control
This is aimed at apps that handle user-uploaded or generated media and need both delivery flexibility and permission boundaries.
Functions
Deploy serverless functions with:
- Secure isolated runtimes
- Event-driven execution
Use this for backend logic that runs in response to events rather than a always-on server.
Sites
Deploy frontends from Git, covering:
- Static
- SSR (server-side rendering)
- CSR (client-side rendering)
Instant previews are included, with Appwrite running behind the deployed site.
Messaging
Send notifications through a unified service across:
- SMS
- Push
One interface instead of three integrations.
Realtime
Subscribe and react to events across your project as they happen — useful for live updates, presence, and reactive UI.
Firewall
Protect apps with:
- Traffic rules
- Abuse controls
- Edge security
Applied per project, sitting at the edge of the architecture.
How the pieces fit together
The platform is described as modular products that "feel unified from the first prototype to production scale." In practice that means you can adopt one service (say, Auth) and add others later without changing platforms. The build-deploy-protect-scale framing maps to: Functions and Databases for build, Sites for deploy, Firewall for protect, and the managed database options plus Realtime for scale.
Agent and framework support
Appwrite states it works with Cursor, Claude Code, and Codex (listed as official integrations, plus six more), and publishes benchmarks comparing model performance across its services — Auth, TablesDB, Functions, Storage, Sites, and Messaging. If you're evaluating whether an AI agent can drive your backend tasks, that benchmark table is the place to check per-service accuracy rather than assuming uniform support.
What to check before committing
- Pricing and plan limits aren't specified in the material here — see the pricing page for current terms.
- Managed PostgreSQL/MySQL availability and configuration details matter if you need a specific relational setup; confirm before designing around it.
- Firewall is marked as new, so verify maturity against your security requirements.
If your project needs auth, data, files, serverless logic, hosting, messaging, and realtime in one stack — and you want agents able to operate on it — Appwrite covers that surface. If you only need one of these, a narrower service may be simpler.