starter.wiki中文

Backend platform

Supabase

A managed backend platform centered on PostgreSQL with integrated Auth, Storage, Realtime, Edge Functions, and generated APIs.

Visit official site

Editorial verdict

Choose Supabase when PostgreSQL, Auth, Storage, Realtime, and generated APIs belong in one coherent backend boundary. Prefer focused services when the product wants independent ownership or different providers for those layers.123

Best for

  • Products that want a PostgreSQL-centered backend with integrated services
  • Teams using row-level security deliberately for client-accessible data
  • Applications that benefit from shared identity, database, storage, and realtime context
123

Not ideal for

  • Teams that want a database-only service without broader platform coupling
  • Products lacking the expertise to design and test row-level security policies
  • Architectures requiring independent vendors or lifecycle boundaries for auth, storage, and data
12
Main trade-off

Supabase can reduce integration work across backend layers, but consolidates security, quotas, cost, availability, and migration decisions around one platform and PostgreSQL project model.125

Product boundary

Whether an integrated PostgreSQL backend platform is preferable to composing database, identity, storage, realtime, and API services separately.

Supabase combines multiple services around a project database. It does not remove responsibility for PostgreSQL design, row-level security, authorization, connection behavior, backups, quotas, egress, and product-specific limits.123

For: Web and mobile teams that want PostgreSQL plus integrated backend services and are prepared to own schema and access-policy design

  • The product wants independent lifecycle and vendor boundaries for database, auth, and storage.
  • The team cannot safely design and test row-level security for client data access.
  • Required regions, extensions, connection behavior, backups, or quotas do not fit the service.

Why teams consider Supabase

  • Full PostgreSQL databaseEach project uses PostgreSQL rather than a proprietary database abstraction.1
  • Integrated servicesAuth, Storage, Realtime, Functions, and APIs are designed around the project database.234
  • Row-level security modelPostgreSQL policies can govern direct client data access when designed correctly.2
  • Shared platform contextRealtime, storage policies, generated APIs, logs, and other services share the project boundary.34

Pricing

Plans combine organization or project packaging with product-specific included usage and overages across compute, database disk, egress, Auth users, Storage, Realtime, and Functions.5

Prototype

Free — $0/month

The current page lists two active projects, 50,000 monthly active users, 500 MB database size, 5 GB egress, and 1 GB file storage; inactive projects can pause.5

Production

Pro — from $25/month

The current page lists the first project, a $10 monthly compute credit, 100,000 MAU, 8 GB disk, 250 GB egress, and 100 GB file storage before dimension-specific overages.5

Compute
Project compute is billed by size; current paid packaging includes compute credit5
Cost shape
Plan plus active projects, compute, database, egress, storage, Auth usage, Realtime, Functions, and add-ons5
Architecture boundary
Auth, Storage, Realtime, and APIs share the PostgreSQL-centered project context5
Pricing checked View official pricing

Supabase vs alternatives

Neon plus focused services

Choose when
Choose composition when a focused PostgreSQL service and independent auth, storage, or realtime vendors are preferred.
Compared with Supabase
The team owns more integration and cross-service operations.111

Firebase

Choose when
Evaluate it when its document data model, mobile SDKs, and Google platform fit better than PostgreSQL.
Compared with Supabase
Data modeling, querying, portability, and backend semantics differ.78

Appwrite

Choose when
Evaluate it when its backend service model or self-hosting route better fits the organization.
Compared with Supabase
Database semantics, ecosystem, and operating model differ.910

Resources and sources

Official product, architecture, and pricing

  • Supabase database overview
    Open
  • Supabase Auth architecture
    Open
  • Supabase Storage
    Open
  • Supabase Realtime
    Open
  • Supabase pricing
    Open
  • Supabase status
    Open

Starter stacks

  1. 1
    Supabase database overview

    Supabase · Accessed Official

  2. 2
    Supabase Auth architecture

    Supabase · Accessed Official

  3. 3
    Supabase Storage

    Supabase · Accessed Official

  4. 4
    Supabase Realtime

    Supabase · Accessed Official

  5. 5
    Supabase pricing

    Supabase · Accessed Official

  6. 6
    Supabase status

    Supabase · Accessed Official

  7. 7
    Firebase documentation

    Google · Accessed Official

  8. 8
    Cloud Firestore data model

    Google · Accessed Official

  9. 9
    Appwrite documentation

    Appwrite · Accessed Official

  10. 10
    Appwrite self-hosting

    Appwrite · Accessed Official

  11. 11
    Why Neon

    Neon · Accessed Official