Backend for a First SaaS: Supabase, PocketBase, Appwrite
Which backend for a first SaaS? We compare Supabase, PocketBase and Appwrite on database, auth, licenses and self-hosting, with a clear pick for each case.
For a first SaaS, pick Supabase if you want a hosted Postgres database with auth and storage included, PocketBase if you want one small server you fully control, and Appwrite if you want a self-hostable platform that bundles messaging and hosting too. All three are open source, so you can leave later. The real choice is how much you want to operate yourself.
What does a first SaaS actually need from a backend?
Less than you think. You need a database, user sign-in, file storage for uploads, and somewhere to run a bit of server code (webhooks, scheduled jobs). Everything else can wait.
That is also the checklist we use below. We read each project's own README on GitHub, so the facts here are what the maintainers say about their product. Pricing changes often, so check each vendor's pricing page before you commit.
Supabase: Postgres with the extras attached
Supabase describes itself as a Postgres development platform. According to its GitHub README, it bundles a hosted Postgres database, authentication, auto-generated REST, GraphQL and realtime APIs, database and edge functions, file storage, and a vector toolkit for AI features. The code is Apache-2.0 licensed, and you can self-host.
Why founders pick it: your data lives in plain Postgres, the database most hosting tools and ORMs already support. If you outgrow the platform, you take your database with you.
It keeps moving fast. In its August 2026 developer update, Supabase listed a public alpha of Pipelines (streaming Postgres changes to BigQuery, on paid plans), an open beta of Unified Logs, and a Grafana Cloud connection that is available on the Free plan too. Separately, a July 2026 changelog entry says explicit extension versions are deprecated: from August 5, 2026 the requested version is ignored and the current default is installed. That is the kind of small change that surprises you at 2 a.m. if you never read changelogs.
Pick it if: you want SQL, a hosted dashboard and the least setup.
PocketBase: one file, one server
PocketBase is a Go backend that ships as a single executable. Per its README, it includes an embedded SQLite database with realtime subscriptions, user and file management, an admin dashboard and a REST-style API. It is MIT licensed, and you can extend it with Go or JavaScript.
The catch is stated plainly by the maintainers: the project is pre-1.0, and "full backward compatibility is not guaranteed before reaching v1.0.0." That does not make it unusable. It means you pin a version and read release notes before upgrading.
Because it is a single process with SQLite, you scale by giving one machine more resources, not by adding nodes. For a first product with a few hundred users, that is often fine. For a team that expects heavy concurrent writes, we would look elsewhere.
Pick it if: you are a solo builder, you want to run on a cheap VPS, and you like understanding every moving part.
Appwrite: a wider platform you can self-host
Appwrite calls itself an open-source cloud for agents and developers. Its README lists auth (email, SMS, OAuth, magic URLs), databases, storage, serverless functions, Sites for deploying frontends from Git, messaging (email, SMS, push), realtime and an MCP server. The license is BSD-3-Clause.
Self-hosting is container-based, typically Docker Compose or an orchestrator such as Kubernetes. Check the self-hosting docs for the current setup steps.
Pick it if: you need messaging or frontend hosting in the same place and are comfortable with Docker.
How do they compare side by side?
| Supabase | PocketBase | Appwrite | |
|---|---|---|---|
| Database | Hosted Postgres | Embedded SQLite | Appwrite Databases |
| Auth | Included | Included | Included |
| License | Apache-2.0 | MIT | BSD-3-Clause |
| Self-host | Yes | Single binary | Yes, via Docker |
| Stability note | Fast-moving platform | Pre-1.0 | Check release notes per version |
How to choose in ten minutes
- Write down your three core tables and who can see which rows.
- If row-level rules matter and you know SQL, start with Supabase.
- If you would rather ship a binary than manage a platform, try PocketBase locally first. It runs with
./pocketbase serve. - If you need push or SMS notifications built in, spin up Appwrite with Docker on a test machine.
- Build the sign-up flow in your top choice before anything else. If it takes more than an afternoon, you picked wrong.
When you are ready to show the product to people, list it in Woodander's Discover directory and browse more developer tools and APIs for the parts of the stack around your backend.
FAQ
Is Supabase free to start?
Supabase's own update notes mention a Free plan, but plan limits change. Check the current pricing page before you build around any quota.
Can I move off these platforms later?
Yes, that is the point of open-source licenses. Supabase gives you Postgres and PocketBase gives you a SQLite file you can copy out.
Is PocketBase safe for production?
The maintainers warn about breaking changes before v1.0.0. Pin versions and test upgrades on a copy first.
Do I need a backend at all?
If your product is a static site with a form, no. Once you store user data or take payments, you do.
