Appwrite is a BSD-3-Clause backend platform with auth, databases, storage, functions, messaging and hosting; use the cloud or self-host.
- Pricing
- Freemium
- Deployment
- Self-hosting supported
- Source
- Open-source edition
- Platforms
- Not recorded
Key differences, specifications and fit guidance for Appwrite and PocketBase, compiled from official documentation and the iThub profiles.
Appwrite is a BSD-3-Clause backend platform with auth, databases, storage, functions, messaging and hosting; use the cloud or self-host.
PocketBase is a lightweight, self-hosted backend that ships as one executable with an embedded SQLite database, authentication, file storage and a realtime API.
Choose PocketBase if one server is enough: it is a Go backend that runs as a single executable with embedded SQLite, auth, file storage and realtime, scales only vertically, and is extended with Go or JavaScript code. Choose Appwrite if you need a wider platform with serverless functions, messaging, frontend hosting and several database options, used as a managed cloud or self-hosted with Docker or Kubernetes. Also weigh maturity: PocketBase is self-hosted only and does not guarantee backward compatibility before v1.0.0.
Shortlist Appwrite when you want serverless functions, messaging, frontend hosting and a choice of database engines in one platform, with a managed cloud and the option to self-host on Docker or Kubernetes.
Shortlist PocketBase when a self-contained app on one server is enough, you want a single executable with embedded SQLite to deploy and back up, and your team can extend it in Go or JavaScript and follow pre-1.0 changelogs.
| Aspect | ||
|---|---|---|
| Architecture and deployment | A hybrid monolithic-microservice architecture with background workers and a message queue, installed with Docker or with a Helm chart on Kubernetes that runs built-in or managed PostgreSQL, Redis, ClickHouse and S3. | One portable executable with no external dependency: upload it to a server and start it, optionally as a systemd service or behind a reverse proxy. It scales only vertically, on a single server. |
| Database | TablesDB for relational rows, DocumentsDB for schemaless data and VectorsDB for embeddings, all behind an Appwrite API with permissions and realtime, or managed PostgreSQL and MySQL with direct SQL access. | Embedded SQLite in WAL mode, with no plans to support other databases. All data and local uploads live in the pb_data directory, and the FAQ points to Litestream for replication and disaster recovery. |
| Authentication | Email and password with Argon2 hashing, phone, magic URL, email OTP, anonymous sessions, passkeys and OAuth 2 with GitHub, Google, Facebook and 30+ other providers. | Auth collections support password and one-time password logins and more than 15 OAuth2 providers. The web APIs are stateless: clients send a token and there are no server-side sessions. |
| Storage and custom code | Storage adds compression, encryption, image transformations and access control. Functions run code in isolated containers, triggered by HTTP requests, SDK methods, server events, webhooks or schedules. | Files are stored locally or in S3 and attached to records, with thumbnails generated on the fly. There are no cloud functions; custom logic is written in Go or JavaScript inside the backend itself. |
| Realtime and SDKs | Realtime pushes events from all Appwrite services to clients over a WebSocket. Client SDKs cover Web, Flutter, Apple, Android, React Native and Unity, plus server SDKs such as Node.js and Python. | Realtime uses Server-Sent Events for record changes. Official SDKs exist for JavaScript (browser, Node.js, React Native) and Dart (web, mobile, desktop, CLI). |
| Managed cloud and pricing | Appwrite Cloud has a free plan and paid plans. Database compute is serverless with a $0 fixed fee or dedicated from $10 a month per database, and a Free plan project freezes at a resource limit. | No hosting is offered: PocketBase is self-hosted only and free under the MIT license. The FAQ suggests any VPS provider with persistent storage for a traditional setup. |
| Maturity and versioning | Appwrite offers enterprise self-hosting with dedicated support and can sign a BAA. Upgrading a self-hosted server from an older version goes through the Appwrite migration tool. | Backward compatibility is not guaranteed before v1.0.0, and the docs do not recommend it for production critical apps unless you follow the changelog. It is a personal project developed on a volunteer basis. |
From the iThub profiles. “Not recorded” means the profile does not confirm it. Confirm prices and editions with each vendor.
| Attribute | ||
|---|---|---|
| Starting price | See vendor pricing ↗ | See vendor pricing |
| Open-source edition | Yes | Yes |
| Self-hosting | Supported | Supported |
| API | Yes ↗ | Yes |
| Founded | 2019 | Not recorded |
| Headquarters | San Francisco, USA | Not recorded |
| GitHub stars | 57.9K ↗ | 61.6K ↗ |
| Documentation | Official docs ↗ | Official docs ↗ |
Appwrite is an open-source backend platform for building and scaling apps. It describes itself as an MCP and agent-first platform: MCP support is included so coding agents can work on a live Appwrite project. The repository is licensed under BSD-3-Clause, and Appwrite runs as a managed cloud platform or can be self-hosted on infrastructure you control.
The platform is split into services. Auth covers email, SMS, OAuth, anonymous sessions and magic URLs. Databases can use Appwrite databases or managed PostgreSQL and MySQL. Storage handles files with compression, encryption, image transformations and access control. Functions run serverless code in isolated runtimes, Sites deploys frontends from Git, and Messaging sends email, SMS and push notifications.
PocketBase is an open-source backend distributed as a single Go executable. It embeds an SQLite database, built-in user authentication, file storage, a REST-ish API and an admin dashboard, and can also be used as a Go framework for custom logic. It is developed largely by one maintainer (Gani Georgiev) rather than a company. The README describes it as an open source Go backend and says it is licensed under the MIT License.
As a standalone app, you download the prebuilt executable for your platform, extract the archive and run ./pocketbase serve. The prebuilt executables come with the JS VM plugin enabled by default, so they can be extended with JavaScript. As a Go framework, PocketBase is a regular Go library package, so you can add your own business logic and still end up with a single portable executable; the README asks for Go 1.27+ for that route.
Appwrite and PocketBase are both open source backends with auth, data, file storage and realtime, but they target different scales. PocketBase ships as one Go executable with embedded SQLite that runs on a single server, while Appwrite is a multi-service platform with functions, messaging and frontend hosting that you use in Appwrite Cloud or self-host with Docker or Kubernetes.
Start from expected load and who will operate the backend. If one server with SQLite covers your traffic and your team can write custom logic in Go or JavaScript, PocketBase keeps operations small. If you need serverless functions, several database engines, a managed cloud or horizontal scaling, compare it with Appwrite and model the cost of its cloud plans or of running its services yourself. Factor in that PocketBase is still before v1.0.
Build the same small app on both: email and OAuth sign-up, a collection with per-user access rules, file upload with a thumbnail, a realtime feed and one piece of custom server logic (an Appwrite Function, a PocketBase hook). Run PocketBase as a single executable on a VPS and Appwrite on Appwrite Cloud or Docker, then compare setup time, backup and restore, the steps to upgrade between two versions, and the monthly cost estimate.
PocketBase is an open source Go backend with embedded SQLite, auth, file storage, realtime subscriptions and an admin dashboard, built for self-contained apps that run on a single server. Appwrite is a multi-service platform with auth, several database options, storage, functions, messaging, realtime and frontend hosting, available as a managed cloud or self-hosted on infrastructure you control.
No. The PocketBase FAQ says it does not support running cloud functions. Instead you use it as a framework and write custom business logic in Go or JavaScript, still ending up with one portable backend; the prebuilt executable comes with an embedded ES5 JavaScript engine. Appwrite Functions run user code in isolated containers, triggered by HTTP requests, SDK methods, server events, webhooks or schedules.
PocketBase scales only on a single server, vertically, and its FAQ positions it for small and midsize applications. For replication and disaster recovery it points to Litestream. Appwrite Cloud scales automatically, while a self-hosted Appwrite needs manual scaling configuration, and its production guidance covers load balancing across multiple instances.
No. PocketBase is self-hosted only. Its FAQ suggests any VPS provider with persistent storage, and the going to production guide notes there is no official Docker image but gives a minimal Dockerfile as an example. Backups and restore are built in from v0.16. Appwrite offers Appwrite Cloud with a free plan and paid plans, and can also be self-hosted.
PocketBase is still in active development, and full backward compatibility is not guaranteed before v1.0.0. Its documentation says it is not recommended for production critical applications yet, unless you are fine with reading the changelog and applying manual migration steps from time to time. It is a personal open source project with intentionally limited scope, developed on a volunteer basis.
Yes. The Appwrite repository is available under the BSD 3-Clause License. PocketBase is free and open source under the MIT License, and its README says you are free to do whatever you want with it, even offer it as a paid service. Both licences are permissive, so the practical differences are architecture, hosting and project maturity.
Facts on this page come from these official pages, checked on , and from the iThub profiles. Vendors change plans and features: confirm with them before buying.
Comparisons are decision aids, not rankings. Read the evaluation methodology or report a correction.