Tool page

Appwrite

Item: Appwrite
Rating: 4.5

The open source backend that replaces Firebase auth, database, storage and functions.

Category: Stack
Pricing: €0 · Freemium
How often: Per project
My rating: 4.5 out of 5

Try Appwrite (official site, new tab)

In short

Appwrite is the best open source answer to Firebase. Ideal if you want a complete BaaS without depending on Google, with the option to host everything yourself.

Ideal for: Flutter, React Native or web developers who want a turnkey backend without vendor lock-in
Use case: Auth, database, file storage and serverless functions, all in one

Why I use it

Before: Firebase by default on almost all of my Flutter and web projects (auth, Firestore, storage, functions). The Google stack had the advantage of integrating everything out of the box.
The problem: Firebase's Blaze plan is capped at 5 projects. When you stack personal SaaS, client apps, prototypes and the nonprofit's account, you hit the wall, not to mention the Google lock-in on projects that had no need for Google OAuth or any specific Google API.
Why this tool won: Appwrite is open source and self-hostable on my VPS (a clear advantage over Supabase, which depends more on the cloud), and its Flutter SDK is mature. For any project that doesn't need Google OAuth or a native Google API, I have no reason to pay the Firebase bill or eat into one of my 5 slots.
Concrete result: Firebase is now reserved for apps that truly justify Google (OAuth, real-time Firestore, native Android integrations). Appwrite takes everything else, and there is no more 5-project cap.

How I use it every day

New Flutter app without Google

Context: When I start a Flutter app that doesn't need Google OAuth or Google APIs.
How: Self-hosted Appwrite on my Hostinger VPS via Coolify, official Flutter SDK. Email/password auth + magic link ready in under an hour.
Result: A complete backend (auth + database + storage) in place on day one, without touching the Firebase Blaze quota.

Long-term personal SaaS

Context: For my own SaaS products, where I want to control infrastructure cost as the user base grows.
How: Self-hosted Appwrite on the same VPS as my other services. Per-document permissions handled directly in Appwrite rather than with a custom middleware layer.
Result: Infrastructure cost capped at the price of the VPS, whatever the growth. And my data stays on my server.

Quick prototype

Context: When I want to test an idea without setting up dedicated infrastructure.
How: Appwrite Cloud Free (75k MAU, 2 GB storage) to get started in 5 minutes without touching the VPS. Auth + database ready to use.
Result: A working MVP in one evening, without burning a Firebase Blaze slot I'd rather keep for real projects.

Self-hosted serverless functions

Context: When a project needs server-side business logic without building a dedicated API.
How: Appwrite Functions in Node or Python, triggered by events (document creation, webhook). Logs and debugging directly in the console.
Result: No per-invocation billing like Cloud Functions. The logic runs on my VPS at a fixed cost.

What it costs

Entry price: €0. Prices taken from the official site, excluding tax.

What it costs
Plan	Per month	Per year	For whom
Self-hosted	€0	–	Developers who want full control and have a server
Cloud Free	€0	–	Prototyping and small projects
Cloud Pro · Recommended	€15/member	–	Teams and production projects

Alternatives I ruled out

Alternatives I ruled out
Alternative	Why I did not keep it
Firebase (Google)	Firebase if you want maturity. Appwrite if you want independence. Better at: Richer ecosystem, more scalable Firestore, built-in Google Analytics Worse at: Total vendor lock-in, prices that explode at scale, data at Google
Supabase	Supabase for projects that need SQL. Appwrite for Flutter or if you prefer the NoSQL approach. Better at: PostgreSQL (native SQL), more powerful Row Level Security, bigger community Worse at: More complex self-hosting, no Flutter SDK as mature

Strengths and limits

Pros

Open source (Apache 2.0): auditable, forkable, self-hostable
Full coverage: auth (email, OAuth, magic link), database, storage, functions, realtime
Official SDKs for Flutter, React, Vue, Next.js, Android, iOS, Node.js
Intuitive web console: set up auth and permissions without code
Easy migrations: versioned database schemas you can deploy

Cons

Fewer services than AWS or GCP: no ML, no managed queue, no built-in CDN
Smaller community than Firebase: fewer resources and tutorials
Self-hosting requires server maintenance (Docker)
Realtime scales less well than Supabase on large volumes

Main features

Authentication: Email/password, OAuth (Google, GitHub, Apple...), magic link, anonymous, SMS Complete auth in under 1 hour without writing any backend code
Databases: NoSQL database with queries, per-document permissions, realtime Store and query data with per-user access rules
Limit: Less powerful than PostgreSQL for complex SQL queries
Storage: Upload, download, on-the-fly image transformations Manage user files (avatars, attachments) with permissions
Functions: Serverless functions with multi-runtime support (Node, Python, PHP, Ruby...) Server-side business logic without managing infrastructure
Realtime: Real-time events on document changes Chat, notifications, collaboration without polling

Compatibility

macOS : compatible
Windows : compatible
Linux : compatible
iOS : compatible
Android : compatible
Browser : compatible
API : compatible
n8n : compatible
Zapier : not compatible

Frequently asked questions

Is Appwrite really open source?

Yes, Apache 2.0. You can fork it, modify it and host it with no commercial restriction.

Is Appwrite GDPR compliant?

When self-hosted, yes: your data stays on your server. Appwrite cloud is hosted in Europe.

Appwrite vs Supabase: which one to choose?

Supabase for SQL/PostgreSQL. Appwrite for Flutter, NoSQL, or if you want simpler self-hosting.

Can you migrate from Firebase to Appwrite?

Yes, Appwrite has Firebase migration guides. It isn't automatic, but it is documented.

Final verdict

The best open source alternative to Firebase. Self-hostable, complete, and free of vendor lock-in.

I recommend it to: Flutter/mobile developers and web devs who want an open source BaaS without Google.
Not suited for: Projects that need advanced SQL or a very rich cloud ecosystem (ML, CDN, queue).
Value for money: Excellent · 4.5 out of 5

Other tools on the workbench

Stack · €0 (self-hosted)
n8n
Stack · €0
Docker
Stack · €0
Firebase

In short

Appwrite is the best open source answer to Firebase. Ideal if you want a complete BaaS without depending on Google, with the option to host everything yourself.

Ideal for: Flutter, React Native or web developers who want a turnkey backend without vendor lock-in
Use case: Auth, database, file storage and serverless functions, all in one

Why I use it

Before: Firebase by default on almost all of my Flutter and web projects (auth, Firestore, storage, functions). The Google stack had the advantage of integrating everything out of the box.
The problem: Firebase's Blaze plan is capped at 5 projects. When you stack personal SaaS, client apps, prototypes and the nonprofit's account, you hit the wall, not to mention the Google lock-in on projects that had no need for Google OAuth or any specific Google API.
Why this tool won: Appwrite is open source and self-hostable on my VPS (a clear advantage over Supabase, which depends more on the cloud), and its Flutter SDK is mature. For any project that doesn't need Google OAuth or a native Google API, I have no reason to pay the Firebase bill or eat into one of my 5 slots.
Concrete result: Firebase is now reserved for apps that truly justify Google (OAuth, real-time Firestore, native Android integrations). Appwrite takes everything else, and there is no more 5-project cap.

How I use it every day

New Flutter app without Google

Context: When I start a Flutter app that doesn't need Google OAuth or Google APIs.
How: Self-hosted Appwrite on my Hostinger VPS via Coolify, official Flutter SDK. Email/password auth + magic link ready in under an hour.
Result: A complete backend (auth + database + storage) in place on day one, without touching the Firebase Blaze quota.

Long-term personal SaaS

Context: For my own SaaS products, where I want to control infrastructure cost as the user base grows.
How: Self-hosted Appwrite on the same VPS as my other services. Per-document permissions handled directly in Appwrite rather than with a custom middleware layer.
Result: Infrastructure cost capped at the price of the VPS, whatever the growth. And my data stays on my server.

Quick prototype

Context: When I want to test an idea without setting up dedicated infrastructure.
How: Appwrite Cloud Free (75k MAU, 2 GB storage) to get started in 5 minutes without touching the VPS. Auth + database ready to use.
Result: A working MVP in one evening, without burning a Firebase Blaze slot I'd rather keep for real projects.

Self-hosted serverless functions

Context: When a project needs server-side business logic without building a dedicated API.
How: Appwrite Functions in Node or Python, triggered by events (document creation, webhook). Logs and debugging directly in the console.
Result: No per-invocation billing like Cloud Functions. The logic runs on my VPS at a fixed cost.

Plan

Per month

Per year

For whom

Self-hosted

€0

–

Developers who want full control and have a server

Cloud Free

€0

–

Prototyping and small projects

Cloud Pro · Recommended

€15/member

–

Teams and production projects

Alternatives I ruled out

Alternatives I ruled out
Alternative	Why I did not keep it
Firebase (Google)	Firebase if you want maturity. Appwrite if you want independence. Better at: Richer ecosystem, more scalable Firestore, built-in Google Analytics Worse at: Total vendor lock-in, prices that explode at scale, data at Google
Supabase	Supabase for projects that need SQL. Appwrite for Flutter or if you prefer the NoSQL approach. Better at: PostgreSQL (native SQL), more powerful Row Level Security, bigger community Worse at: More complex self-hosting, no Flutter SDK as mature

Strengths and limits

Pros

Open source (Apache 2.0): auditable, forkable, self-hostable
Full coverage: auth (email, OAuth, magic link), database, storage, functions, realtime
Official SDKs for Flutter, React, Vue, Next.js, Android, iOS, Node.js
Intuitive web console: set up auth and permissions without code
Easy migrations: versioned database schemas you can deploy

Cons

Fewer services than AWS or GCP: no ML, no managed queue, no built-in CDN
Smaller community than Firebase: fewer resources and tutorials
Self-hosting requires server maintenance (Docker)
Realtime scales less well than Supabase on large volumes

Main features

Authentication: Email/password, OAuth (Google, GitHub, Apple...), magic link, anonymous, SMS Complete auth in under 1 hour without writing any backend code
Databases: NoSQL database with queries, per-document permissions, realtime Store and query data with per-user access rules
Limit: Less powerful than PostgreSQL for complex SQL queries
Storage: Upload, download, on-the-fly image transformations Manage user files (avatars, attachments) with permissions
Functions: Serverless functions with multi-runtime support (Node, Python, PHP, Ruby...) Server-side business logic without managing infrastructure
Realtime: Real-time events on document changes Chat, notifications, collaboration without polling

Frequently asked questions

Is Appwrite really open source?

Yes, Apache 2.0. You can fork it, modify it and host it with no commercial restriction.

Is Appwrite GDPR compliant?

When self-hosted, yes: your data stays on your server. Appwrite cloud is hosted in Europe.

Appwrite vs Supabase: which one to choose?

Supabase for SQL/PostgreSQL. Appwrite for Flutter, NoSQL, or if you want simpler self-hosting.

Can you migrate from Firebase to Appwrite?

Yes, Appwrite has Firebase migration guides. It isn't automatic, but it is documented.

Final verdict

The best open source alternative to Firebase. Self-hostable, complete, and free of vendor lock-in.

I recommend it to: Flutter/mobile developers and web devs who want an open source BaaS without Google.
Not suited for: Projects that need advanced SQL or a very rich cloud ecosystem (ML, CDN, queue).
Value for money: Excellent · 4.5 out of 5

Appwrite

In short

Why I use it

How I use it every day

New Flutter app without Google

Long-term personal SaaS

Quick prototype

Self-hosted serverless functions

What it costs

Alternatives I ruled out

Strengths and limits

Pros

Cons

Main features

Compatibility

Frequently asked questions

Final verdict

Other tools on the workbench

n8n

Docker

Firebase

Appwrite

In short

Why I use it

How I use it every day

New Flutter app without Google

Long-term personal SaaS

Quick prototype

Self-hosted serverless functions

What it costs

Alternatives I ruled out

Strengths and limits

Pros

Cons

Main features

Compatibility

Frequently asked questions

Final verdict

Other tools on the workbench

n8n

Docker

Firebase