Appwrite Review

Appwrite's pitch is one subscription for auth, databases, storage, functions, realtime and hosting, and the code is open source, so the same stack can run on your own server. That pairing is why it earns a place on backend shortlists.

The hesitation is structural: the free tier is hard-capped, and the paid model is described two ways on Appwrite's own pages. Toolradar data: of the 110 low-code backend tools we evaluated, 4 of the 10 top picks publish a paid price, with a median cheapest paid plan of $25 a month, so transparent pricing is the exception in this category.

This review covers what each plan includes, which meters move the bill, and when Supabase or Firebase is the better buy. For the wider field, see our backend-as-a-service roundup.

Toolradar profiles for Supabase, Firebase and PocketBase sit beside Appwrite's, so the comparison below can be checked against them.

Appwrite is an open-source backend platform under the BSD-3-Clause license, bundling auth, databases, storage, functions, messaging, hosting and realtime behind one API.

Its repository describes it as a cloud for agents and developers, and says it can be self-hosted on infrastructure you control, with a Docker image as the install path (appwrite/appwrite:2.4.0 in its current README). The default database engine is TablesDB, not raw Postgres.

PostgreSQL, MySQL, DocumentsDB and VectorsDB are selectable as well, so the engine is a setup decision to make before you write data.

Toolradar's Appwrite profile sits beside the other backends we rank, and our self-hosting tools roundup covers teams that want to run everything themselves.

You create an organization, then projects inside it. Plans attach to the whole organization, resources are allocated per project, and most resource limits reset at the start of each billing period.

Appwrite's billing docs say extra resources are bought automatically when you go over a limit, up to a budget cap you set in the organization's Billing tab, and members get emails as usage approaches that cap. So a paid plan keeps buying capacity until the cap is reached, and the bill grows with it.

Set the cap before launch, not after the first invoice, and watch the Usage tab during a traffic spike. Free works differently: at a limit, API access is denied, which turns a viral week into downtime rather than a surprise charge.

If you are weighing a serverless approach instead, our serverless platforms roundup compares that model.

Appwrite's own pages describe its paid model two ways, so this review quotes only figures that its docs, changelog and announcements state. Its December 2023 launch post gives Pro at $15 per member per month. Its current billing docs say plans apply to an entire organization, with resources allocated per project.

Confirm the Pro fee on appwrite.io/pricing before you budget, because the answer changes whether a team pays per head or per project set.

The meters are where the real bill sits. Appwrite's realtime changelog, dated March 2026, sets Pro at 6 million messages and 500 concurrent connections a month, with extra messages at $2.50 per million and extra connections at $5 per 1,000, enforced from April 30, 2026.

Its database announcement from March 2025, which the page shows as updated in June 2026, gives Pro 1.75 million reads and 750,000 writes a month, then $0.060 per 100,000 reads and $0.10 per 100,000 writes.

Its database pricing page adds a $0 fixed serverless fee, a $10 monthly database compute credit for every account, and dedicated databases from $10 a month each.

On the free plan, the documented caps are two projects per organization, from September 2025, and two functions per project, since January 2026.

Free storage, bandwidth and monthly user caps are left out, because Appwrite's pages give no figure this review can cite.

Methodology: Appwrite figures come only from appwrite.io pages, its changelog, its announcements and its repository, read on 10 October 2026.

Supabase figures come from supabase.com/pricing and Firebase figures from firebase.google.com/pricing, both verified on the vendor pages in October 2026.

PocketBase is checked on its homepage, which lists no hosted price. Third-party listings were not used as a source for any figure here. For free database options beyond these four, see our free database hosting roundup.

Appwrite suits small teams that want an open-source backend they can move off, and solo builders who expect to self-host eventually. It is a sensible home for a prototype that may grow. The free tier is usable for building, and the code runs on your own server later.

Teams with heavy realtime use should model connections and messages first. Pro includes 500 concurrent connections, and extra connections cost $5 per 1,000, so a busy collaborative app can run up that line quickly. It is a weaker fit for a launch that cannot go dark.

It is also the wrong choice for teams that need managed Postgres with a flat monthly bill. For managed Postgres, see our Postgres hosting roundup and the Neon review.