A developer introduction

Supabase: Postgres, plus the backend around it.

Every project starts with a full Postgres database. Add Auth, Data APIs, Edge Functions, Realtime, Storage and Vector as you need them.

Source: supabase.comSupabase for developers

Core capabilities

Start with Postgres. Add what you need.

Supabase pitches its products as "use one or all": separate tools that are integrated as one platform.

Full Postgres, described as 100% portable

Row Level Security built into Auth

Extensions, Cron and Queues on top

Postgres

one database
per project

Auth

Sign-ups and logins, secured with RLS

Data APIs

Instant REST APIs, plus GraphQL

Edge Functions

Custom code without managing servers

Storage

Large files under RLS access policies

Realtime

Database changes and broadcast

Vector

Store, index and search embeddings

Sources: supabase.com · supabase.com/docs02 / 05

Example architecture

Example: an AI-assisted notes app

Illustrative example, not a customer case

Client

Web + mobile

Next.js web app and an Expo app, both using supabase-js

1

Supabase project

AuthSign-in and sessions

Data APIRead and write notes

RealtimeLive shared edits

StorageAttachments

Edge FunctionsSummaries and embedding jobs

Postgresnotes tables · RLS policies · vector embeddings

2

External

Model API

For example OpenAI or Hugging Face

1The client signs in and queries tables directly; RLS decides which rows each user can see.

2An Edge Function holds the API key and calls the model, so no extra server is needed.

3Embeddings are written back to Postgres, then searched with Vector.

Example design based on capabilities at supabase.com and supabase.com/docs03 / 05

Prototype to production

Same Postgres, from laptop to launch.

01

Run locally

npx supabase init

Pin the CLI per project
Develop against a local stack

02

Build

@supabase/supabase-js

Framework quickstarts and starter templates
Table editor, SQL editor, RLS policies

03

Harden

Security Advisor

RLS enabled on every table
SSL, network limits, MFA
Indexes and load tests

04

Ship

GitHub integration

Deploy migrations from main
Preview branches for schema changes
Backups and point-in-time recovery

Sources: supabase.com/docs · supabase.com/docs/guides/deployment/going-into-prod04 / 05

Step one comes from the docs' getting-started flow: install the CLI as a dev dependency so the version is pinned, then run supabase init. Step two: quickstarts exist for React, Next.js, Vue, SvelteKit, Flutter, Swift, Kotlin, Python and more, and the dashboard has Table Editor, SQL Editor and RLS policy tools. Steps three and four summarize Supabase's own Production Checklist: review Security and Performance Advisors, enable RLS on all tables, turn on SSL enforcement and network restrictions, protect accounts with MFA, add indexes and load test on staging. For deployment, connect GitHub so schema changes deploy from main instead of manual db push, and use branching to test migrations. Note that some features, like branching and point-in-time recovery, depend on plan or add-ons; check current pricing yourself rather than relying on this deck.

How to evaluate

Judge it as infrastructure, not a shortcut.

Prototype in a weekend, then check the parts that matter for production: portability, control and responsibility.

It's Postgres underneath

A full database per project, with migration guides from Firebase, Neon, RDS and others.

Open source, self-hostable

Built in the open: read, contribute or self-host, so you are not locked in.

Shared responsibility

The site lists SOC 2 Type 2, HIPAA and ISO 27001. RLS, indexes and load tests remain your job.

Sources: supabase.com · supabase.com/docs · Production checklist05 / 05