🧭 Decision Guide
Why trending now: 材料显示 Appwrite 当前强调“agent-first”和内置 MCP,可连接 Cursor、Claude Code、Codex;同时当日新增 232 星、总星数 58,227,最新版本为 2.7.3。结合这些信息,当前受关注的直接原因更可能是智能体开发场景与一体化云服务的结合,但材料无法进一步证明具体传播来源。
Try it if you
-
你要让 Cursor、Claude Code 或 Codex 操作真实 Appwrite 项目README 的 Getting Started 和正文写明可通过 hosted MCP server 连接这些 agents;MCP included on Cloud。
-
你希望一个平台同时提供 Auth、Databases、Storage、Functions 和 RealtimeREADME 的 Products 章节列出 Auth、Databases、Storage、Functions、Messaging、Firewall 和 Realtime。
-
你需要在 Docker CLI 可运行的基础设施上自托管README 的 Self-Hosting 章节说明 Appwrite 可安装在任何能运行 Docker CLI 的操作系统上。
-
你的数据库方案需要在 Appwrite、PostgreSQL 和 MySQL 之间选择README 的 Databases 产品说明同时支持 Appwrite databases、managed PostgreSQL 和 MySQL。
Skip it if you
-
运行环境不能安装 Docker CLI,或无法处理 localhost:20080 的安装流程README 的 Self-Hosting 章节将 Docker CLI 列为前置条件,安装器监听 127.0.0.1:20080。
-
你需要把远程安装器端口 20080 直接公开到所有网络接口README 明确要求远程主机通过 SSH 隧道访问 127.0.0.1:20080,而不是把端口发布到所有接口。
-
你要升级旧版 Appwrite,但不准备使用 migration toolREADME 的 Upgrade from an Older Version 章节要求安装完成后使用 Appwrite migration tool。
Requirements
- 自托管前必须安装 Docker;README 原文为“Before running the installation command, make sure you have Docker installed on your machine.”
- 安装器使用 localhost 的 20080 端口,并打印一次性 installer secret 到 STDOUT。
- 远程主机需要 SSH 隧道连接 127.0.0.1:20080。
- 如果出现 Docker API 1.52 与最大支持版本 1.42 的错误,需要设置 DOCKER_API_VERSION=1.42 或升级主机 Docker。
- 项目最新版本为 2.7.3;README 安装命令使用 appwrite/appwrite:2.7.2。
First step (verbatim from README)
docker run -it --rm \
--publish 127.0.0.1:20080:20080 \
--volume /var/run/docker.sock:/var/run/docker.sock \
--volume "$(pwd)"/appwrite:/usr/src/code/appwrite:rw \
--entrypoint="install" \
appwrite/appwrite:2.7.2
Watch out
-
安装器只发布到 127.0.0.1:20080,远程主机应使用 SSH 隧道。README 的 Self-Hosting 章节明确说明 setup wizard listens on port 20080 and is published on localhost only。
-
Docker API 版本不匹配时,安装和升级都可能失败。README 的 Docker API version mismatch 章节给出 client version 1.52 与 maximum supported API version 1.42 的错误。
-
旧版升级不能只运行 setup,还要执行 Appwrite migration tool。README 的 Upgrade from an Older Version 章节要求 setup 完成后使用 migration tool。
Not stated in the README
- README 未说明 Auth、Databases 或 Functions 的具体资源上限、性能指标和计费边界。
- README 未说明 Appwrite Cloud Free plan 的具体配额、超额价格和服务等级。
- README 未提供 MCP 支持的完整工具列表、权限模型和审计细节。
- README 未说明 Docker、操作系统、CPU、内存和存储的最低版本或容量要求。
- README 的技术生态数据未给出 TypeScript、PHP、C、Rust 与 CSS 各模块的具体职责分布。
💡 Deep Analysis
6
Yes
I use Cursor, Claude Code, and Codex, and want agents to do more than generate code by connecting to live projects, APIs, and documentation and operating Appwrite resources; is MCP suitable for this workflow?
Yes. Appwrite is a strong fit because MCP is provided as a platform capability specifically to let agents operate on a live Appwrite project rather than generate code disconnected from the runtime environment.
- The README states: “MCP is included, so coding agents can operate on a live Appwrite project.”
- It explicitly names Cursor, Claude Code, and Codex and says they can connect through the hosted MCP server to Appwrite projects, APIs, and documentation.
- MCP is included on Cloud with no local installation required, while SDKs, CLI, and Terraform remain available as non-agent interfaces.
- The agent can potentially reach Auth, Databases, Storage, Functions, Messaging, Realtime, and Hosting, making permission boundaries more significant than in ordinary code completion.
This does not mean production access should be unrestricted. The README does not define operation-level permissions, approval workflows, audit fields, or safeguards for destructive actions, so those details must be verified separately.
- README introduction: `MCP is included, so coding agents can operate on a live Appwrite project.`
- README introduction: `Connect Cursor, Claude Code, Codex, and other agents through the hosted MCP server`
- README, “Products”: Appwrite MCP connects agents to projects, APIs, and docs; Cloud requires no local install
- README, “Products”: Auth, Databases, Storage, Functions, Messaging, Realtime, and Hosting
Yes
I am building a mobile application with Flutter and React Native and need email, SMS, OAuth, anonymous sessions, file storage, and push notifications; can Appwrite replace several separately integrated backend services?
Yes. Appwrite is a good fit because the README directly covers authentication, files, messaging, realtime behavior, and multiple mobile client entry points.
- Auth supports email, SMS, OAuth, anonymous sessions, and magic URLs, reducing the need to integrate several identity providers into the mobile clients.
- Storage provides compression, encryption, image transformations, and access control for avatars, attachments, and media files.
- Messaging unifies email, SMS, and push notifications, while Realtime lets clients subscribe to project resource changes.
- The architecture lists Flutter, iOS, Android, Web, SDKs, and REST, WebSocket, GraphQL, and S3 interfaces, so the platform is not limited to one frontend framework.
However, the README does not establish that every mobile quota, push-provider limitation, or offline synchronization requirement is covered. Those details require the Cloud plan and the relevant SDK documentation.
- README, “Products”: Auth supports email, SMS, OAuth, anonymous sessions, and magic URLs
- README, “Products”: Storage supports compression, encryption, image transformations, and access control
- README, “Products”: Messaging sends email, SMS, and push notifications; Realtime supports event subscriptions
- README, “Architecture”: entry points include Flutter, iOS, Android, Web, and SDKs; APIs include REST, WebSocket, GraphQL, and S3
- Project data: topics include flutter, ios, android, react-native, and swift
It depends
My host Docker Engine supports only API 1.42, and I need to upgrade from an older Appwrite version to the current release; can I use the installation and upgrade path in the README directly?
It depends. The README provides a compatibility path for Docker API 1.42, but the upgrade cannot be treated as an image replacement because the host API version and migration process both matter.
- The README explicitly describes the error
client version 1.52 is too new. Maximum supported API version is 1.42and says to setDOCKER_API_VERSION=1.42or upgrade the host Docker Engine. - Its installation command uses
appwrite/appwrite:2.7.2, while project data lists 2.7.3 as the latest release, so the example tag and current release are not identical. - The README says to use the same
--env DOCKER_API_VERSION=...flag with--entrypoint="upgrade"and points advanced deployments to environment variables, docker-compose.yml, and .env files. - Custom Compose is supported, but the provided README excerpt does not include the complete upgrade command or rollback procedure after a failed migration.
- README, “Docker API version mismatch”: `client version 1.52 is too new. Maximum supported API version is 1.42`
- README, “Docker API version mismatch”: `DOCKER_API_VERSION=1.42` and `--entrypoint="upgrade"`
- README, “Docker API version mismatch”: public `docker-compose.yml` and `.env` files are available
- Project data: latest release is `2.7.3`; the README example image is `appwrite/appwrite:2.7.2`
docker run -it --rm \
--env DOCKER_API_VERSION=1.42 \
--publish 127.0.0.1:20080:20080 \
--volume /var/run/docker.sock:/var/run/docker.sock \
--volume "$(pwd)"/appwrite:/usr/src/code/appwrite:rw \
--entrypoint="install" \
appwrite/appwrite:2.7.2
Yes
I use Next.js and need to deploy an SSR or CSR frontend from Git with previews, run event-driven backend functions, and subscribe to realtime changes; can Appwrite place these capabilities on one platform?
Yes. Appwrite’s Sites, Functions, and Realtime capabilities map directly to Next.js hosting, event-driven backend logic, and live data subscriptions.
- Sites can deploy static, SSR, and CSR frontends from Git and provide instant previews, covering common Next.js deployment modes.
- Functions provide secure isolated runtimes and event-driven execution, allowing backend-triggered logic without exposing secrets in the browser.
- Realtime supports subscriptions to project resource changes, while the architecture includes Queue, Workers, Executor, and Open Runtimes for background jobs and function execution.
- REST, WebSocket, and GraphQL APIs can connect to existing client or server code, reducing dependence on a single SDK.
The README does not specify the supported Next.js versions, SSR runtime limits, function execution duration, or preview-environment isolation. Those details must be checked before deploying a complex SSR application.
- README, “Products”: Sites deploys static, SSR, and CSR frontends from Git with instant previews
- README, “Products”: Functions provide secure isolated runtimes and event-driven execution
- README, “Products”: Realtime supports subscriptions to project resource changes
- README, “Architecture”: Queue, Workers, Executor, and Open Runtimes; REST, WebSocket, and GraphQL are supported
- Project data: topics include nextjs, react, and web
It depends
I want to move my React or Next.js application from prototype to production on AWS, DigitalOcean, or Azure instead of keeping data in a hosted BaaS; is Appwrite self-hosting suitable for me?
It depends: Appwrite fits developers who value infrastructure control and are willing to operate Docker, but not those who expect the platform to handle backups, upgrades, and security response for them.
- The README explicitly supports both a managed cloud and self-hosting, with deployment guides for AWS, DigitalOcean, Google Cloud, and Azure.
- Auth, Databases, Storage, Functions, Messaging, Realtime, Sites, and Firewall are unified under one project model, covering common backend needs for React and Next.js applications.
- Its hybrid monolithic-microservice architecture uses caching, queues, and background workers, providing a scaling path, while the operator still owns networking, storage, domains, upgrades, and migrations.
- The installation example mounts the Docker socket and binds port 20080 to 127.0.0.1, so production exposure and isolation remain the deployer’s responsibility.
- README, “Self-Hosting” and “One-Click Setups”: managed cloud, self-hosting, and AWS, DigitalOcean, Google Cloud, and Azure guides
- README, “Products”: Auth, Databases, Storage, Functions, Sites, Messaging, Firewall, and Realtime
- README, “Architecture”: hybrid monolithic-microservice architecture, background workers, and message queue
- README, “Docker API version mismatch”: `--publish 127.0.0.1:20080:20080` and `--volume /var/run/docker.sock:/var/run/docker.sock`
It depends
I already work with PostgreSQL or MySQL and want to retain my existing data technology while using REST, GraphQL, WebSocket, or S3 to integrate authentication, storage, and functions; can Appwrite reduce migration constraints?
It depends. Appwrite offers multiple database directions and standard interfaces, but that does not mean Appwrite Databases, PostgreSQL, and MySQL behave as fully equivalent substitutes.
- The Databases product explicitly supports Appwrite databases or managed PostgreSQL and MySQL, preserving choice for teams with existing database experience.
- The architecture lists REST, GraphQL, WebSocket, and S3, making it possible to connect server applications, realtime clients, and existing object-storage tooling through familiar protocols.
- Auth, Storage, Functions, and Messaging are unified with the database layer, reducing the need to assemble identity, files, compute, and notifications from separate vendors.
- However, the project insights state that database compatibility does not guarantee identical query, index, permission, transaction, or data-model behavior. Complex SQL, database-specific features, and rollback plans still require separate validation.
It is therefore suitable for gradual backend consolidation, but not for assuming an existing application can migrate without changes merely because PostgreSQL and MySQL are listed.
- README, “Products”: Databases supports Appwrite databases or managed PostgreSQL and MySQL
- README, “Architecture”: REST, WebSocket, GraphQL, and S3 are supported
- README, “Products”: Auth, Databases, Storage, Functions, and Messaging are provided together
- Project insights, “usage_limitations”: database compatibility does not guarantee identical query, index, permission, transaction, and data-model behavior
✨ Highlights
-
Built-in MCP lets Cursor and Claude Code operate projects
-
Auth, Databases, Storage, and more are unified
-
Supports Appwrite Cloud and self-hosting with Docker CLI
-
Has 58,227 stars and 5,888 forks, indicating a large community
🔧 Engineering
-
MCP connects Cursor and Claude Code to live Appwrite projects
-
Auth supports OAuth, SMS, anonymous sessions, and magic URLs
-
Functions provides isolated runtimes and event-driven execution
-
Sites deploys static, SSR, and CSR frontends from Git
-
Databases supports Appwrite databases, PostgreSQL, and MySQL
⚠️ Risks
-
Self-hosting requires Docker, and the installer listens on localhost:20080
-
Remote hosts require an SSH tunnel; README does not advise exposing port 20080
-
Docker API 1.52 can conflict with a host supporting only version 1.42
-
Older-version upgrades require the Appwrite migration tool after setup
👥 For who?
-
Web teams needing integrated Auth, Storage, and Functions
-
Agent-focused developers using Cursor, Claude Code, or Codex
-
Teams needing Docker CLI self-hosting and infrastructure control