Convex vs Appwrite: Reactive Backend vs Open-Source BaaS

Convex and Appwrite are both full backend platforms, but they are built on fundamentally different architectural models. Convex is a reactive backend: its core innovation is that database queries are reactive by default. When data that a query depends on changes, Convex automatically re-runs the query and pushes the updated result to all connected clients. This removes the need for polling, manual cache invalidation, or custom websocket management in applications that need live data.

Appwrite is a traditional Backend-as-a-Service. It provides REST and GraphQL APIs for auth, a document database, file storage, and serverless functions. Appwrite supports real-time event subscriptions via WebSocket, but this requires explicit subscription setup rather than being automatic for all queries. Appwrite's primary advantage is that it is fully open source under the BSD licence and deployable via Docker on any server, giving teams complete control over their data and infrastructure.

Appwrite changed its pricing model in September 2025, shifting from per-seat to per-project billing. The Cloud Pro plan now costs $25 per month per project. A free tier is available for development and side projects. Appwrite can also be self-hosted at no licensing cost beyond the server infrastructure required to run it.

Convex charges $25 per developer per month on the Professional plan, which includes 25 million function calls, 250GB-hours of compute, and 500,000 Chef AI tokens per month. The free tier supports up to 6 developers on 20 projects with 1 million function calls per month. Convex also offers a Starter plan as a pay-as-you-go option for usage beyond the free tier without committing to the Professional plan. There is no self-hosting option for Convex.

For a solo developer or small team, the cost structures are roughly equivalent. The key difference is Appwrite's self-hosting option, which eliminates cloud subscription costs entirely for teams willing to manage their own infrastructure.

Convex's reactive query model is the platform's most distinctive feature. Any query written in Convex automatically tracks the data it reads. When that data changes, Convex re-runs the query on the server and sends the updated result to subscribed clients without any additional developer configuration. Building a shared document, a live dashboard, or a multiplayer feature in Convex requires no special real-time implementation; it works the same way as any other query.

Appwrite supports real-time via WebSocket subscriptions. Developers subscribe to specific collections or documents and receive events when those records change. This is a solid and well-designed real-time system, but it requires explicit subscription setup for each piece of data you want to keep live. Convex's model is more automatic and less error-prone for complex real-time scenarios, while Appwrite's subscription model is more familiar to developers accustomed to traditional event-driven architectures.

Appwrite includes authentication as a first-class feature. It supports email and password, magic links, OAuth providers including Google, Apple, GitHub, and Microsoft, anonymous sessions, and phone-based OTP. Auth is integrated with the database through permission rules, allowing you to restrict collection access based on the authenticated user role or ID directly in the database configuration rather than in application code.

Convex does not include built-in authentication. The standard approach is to integrate Clerk, which is well-documented and deeply integrated with the Convex SDK. Auth0 and other providers can also be configured. This integration adds a setup step and introduces Clerk as an additional service, but the Clerk integration is mature and the combination is used in production by many Convex applications. For teams already using Clerk, the Convex integration is straightforward. For teams that prefer auth to be part of a single backend platform, Appwrite's built-in auth is a meaningful convenience.

Appwrite can be fully self-hosted via Docker Compose. A single command deploys the entire platform including auth, database, storage, functions, and the admin console to any Linux server. The community maintains updated Docker Compose configurations and Helm charts for Kubernetes deployments. This makes Appwrite suitable for organisations with data residency requirements, compliance frameworks that require data to remain within specific geographic boundaries, or teams philosophically opposed to vendor lock-in.

Convex is a managed service with no self-hosting option. Data stored in Convex remains on Convex's infrastructure. For most commercial applications, this is acceptable. For regulated industries, government projects, or organisations with strict data governance policies, the absence of self-hosting is a disqualifying limitation. EU hosting is available on Convex with a 30 percent pricing surcharge, which addresses some but not all data residency concerns.

Choose Convex if you are building a TypeScript application where real-time data synchronisation is important, the developer experience and end-to-end type safety are priorities, and you are comfortable with a managed service. The reactive query model provides genuine value for collaborative and live-data applications, and the TypeScript integration is among the best available in any backend platform.

Choose Appwrite if self-hosting is a requirement, you need built-in authentication without a third-party auth service, or you prefer open-source software with no risk of pricing changes or service discontinuation. The Docker deployment story is genuinely well-executed, and the $25 per project monthly cloud cost is competitive for teams that want managed hosting without self-hosting complexity. Both platforms have free tiers suitable for experimentation; the decision ultimately comes down to whether automatic reactivity or infrastructure ownership is the more important constraint for your project.