Supabase Documentation

What it is

Supabase is an open-source backend platform built on PostgreSQL. Each project gives you a Postgres database, user authentication (email, magic links, OAuth providers), file storage, auto-generated APIs, realtime subscriptions and serverless edge functions. The documentation covers each of these with guides for Next.js, React, Flutter, Swift, Kotlin and other stacks.

Why it suits a first SaaS

A paid web app needs sign-in, a database, per-user data and somewhere to store files, before it needs any of your clever features. Supabase provides those as one service, with a real SQL database underneath, so you are not locked into an unusual data model. Row-level security lets you write rules such as "users can only read rows from their own team" in the database itself.

Pricing (as of 2026-09)

Supabase's pricing page lists:

• Free: two active projects, 500 MB database and 50,000 monthly active users. Free projects pause after a week without activity.
• Pro: from $25 a month per organisation, with more capacity and compute credits, and a spend cap on by default.

A product with paying customers should not run on a free project that can pause. Budget for the Pro plan at launch.

What to read first

1. The quickstart for your framework.
2. The Auth guide, including email confirmation and password reset.
3. Row-level security: read this carefully, because a missing policy can expose every user's data.
4. Database backups and how to restore them.

Common questions

Is Firebase a better choice? Both work. Firebase uses a document database and fits some mobile apps well; Supabase fits products whose data is naturally relational, like teams, projects and invoices.

Can I leave later? Yes. It is Postgres, so you can export and move your data.

Source: supabase.com/pricing and supabase.com/docs, checked 2026-09.