// open source · postgres-native

# Build in a weekend. Scale to millions.

Every Supabase project ships with a Postgres database, authentication, instant APIs, edge functions, realtime subscriptions, and object storage. Start with a `create table`, deploy with a `git push`, and let the platform carry the load when traffic finds you.

Start your project
Read the docs

All systems normal Press `⌘` `K` to search the docs.

// the stack

## The open source backend that grew up.

One project, six services, all standing on Postgres. Bring your own SQL — the rest of the platform speaks your schema.

Postgres 16

### A dedicated database, on day one.

Every project gets a fully-managed Postgres instance with extensions, point-in-time recovery, and read replicas. The `supabase` CLI streams migrations from `/supabase/migrations` straight to production.

Explore the database →
Row-level

### Auth that respects your schema.

Email, OAuth, magic links, and SAML — all writing to a `auth.users` table you can join against. Row-level security policies enforce access in the database, not in middleware.

See the auth flow →
Realtime

### Subscriptions over your data.

Listen to row inserts, updates, and deletes from the browser — no extra service, no manual fan-out. Realtime streams Postgres' write-ahead log to authorized clients over a single WebSocket.

Inspect the channel →

// get the launch kit

## Ship the schema. We'll handle the rest.

Inputs, focus rings, and edges all derive from `--border` and `--accent`. The primary CTA reuses `.btn-brand` unchanged — emerald fill, near-black label, pill radius. No raw hex anywhere in the component CSS.

Press `Enter` on the email field to submit. The focus halo lands at the documented brand-highlight tint (`rgba(62, 207, 142, 0.5)`) — visible against the canvas without dominating the page.

Full reference at tokens.css · spec at DESIGN.md.

// launch kit

Open
Work email

We'll send the starter repo and a Postgres schema you can `supabase db push` on day one.