How do I get started with Appwrite and what should I check before choosing it?
You can get started with Appwrite by creating a project through Start project and reading the View docs entry point, then checking whether its modules match your stack. Appwrite describes itself as an MCP & agent-first, open-source platform for building and scaling apps, bundling Auth, Databases, Storage, Functions, Messaging, Realtime, and Hosting in one place. Before committing, verify three things: which services you actually need, whether your frameworks/languages and agent tools are supported, and what the pricing page says about cost.
Getting started: the first two steps
- Create a project. Use the Start project action on appwrite.io. This is the entry point for provisioning a new Appwrite project.
- Read the docs. Use View docs to understand how the services are configured and called. The docs are where you confirm concrete details like SDK availability and runtime support, since the homepage only summarizes capabilities.
Expected result: you have a project context and a working understanding of which Appwrite services you'll wire into your app first.
What Appwrite actually provides
Appwrite positions its products as modular but unified, from first prototype to production scale. The core modules listed on the site:
| Service | What it does (per Appwrite) |
|---|---|
| Auth | Authenticate users with email, SMS, OAuth, anonymous sessions, and magic URLs |
| Databases | Model, query, and scale with Appwrite databases or managed PostgreSQL and MySQL |
| Storage | Store files with compression, encryption, image transformations, and access control |
| Functions | Deploy serverless functions with isolated runtimes and event-driven execution |
| Sites | Deploy static, SSR, and CSR frontends from Git with instant previews |
| Messaging | Send email, SMS, and push notifications through one service |
| Firewall | Protect apps with traffic rules, abuse controls, and edge security |
| Realtime | Subscribe and react to events across your project as they happen |
The Databases row is the one worth reading twice: Appwrite offers both its own database and managed PostgreSQL/MySQL, so the choice depends on your use case and team needs rather than a single default.
Check compatibility before you commit
Appwrite says it is optimized for "the frameworks, languages and agents you love," and it lists official integrations with Cursor, Claude Code, and Codex, plus six more. If your workflow depends on a specific agent tool, confirm it appears in that list before standardizing on Appwrite.
The site also publishes an AI Arena benchmark comparing models against Appwrite tasks (Auth, TablesDB, Functions, Storage, Sites, Messaging), with per-model cost per 1M tokens and accuracy percentages. Treat this as Appwrite's own benchmark of how well different models operate the platform — useful if you plan to let agents drive Appwrite, not as an independent evaluation.
Security and production readiness
Appwrite states it takes a "security-first approach" with "embedded security across every layer of the architecture," and the Firewall product adds traffic rules, abuse controls, and edge security per project. The homepage also cites teams "from fast-moving startups to global enterprises" building in production. These are vendor claims; for a production decision, map them against your own compliance and threat model rather than treating the headline as sufficient.
Cost: where to look
The site links to a Pricing page. Nothing in the available material states that any tier is free, so check that page directly for plan limits and terms before assuming a free starting point.
A quick decision checklist
- Need auth, storage, functions, and a database behind one API? Appwrite's bundled model fits.
- Need managed PostgreSQL or MySQL specifically? Confirm the Databases option covers your version and scaling needs.
- Rely on a particular AI coding agent? Verify it's in the official integration list.
- Have strict security or compliance requirements? Review the Firewall and security documentation, not just the homepage.
- Budget-sensitive? Read the Pricing page before prototyping.