0

The cast: Postgres, PostgREST, Auth, Realtime, Storage

Modelused in ~90% of apps

"Supabase" sounds like one product, and the marketing site's logo grid makes it look like five unrelated tools bolted together. Neither is true, and the gap between those two wrong ideas is where a junior gets lost the first time something breaks in production: they don't know which of five processes to even look at, let alone that four of those five are quietly reading and writing the exact same database you already know.

Core idea. Supabase is a small cast of independent processes — PostgREST, Auth, Realtime, Storage, Edge Functions — each with exactly one job, sitting in front of a single, ordinary Postgres database. The unifying fact that makes the whole platform learnable in one course is this: none of those processes has its own private data store. Auth's users, Storage's file metadata, and Realtime's message log are all just tables, in their own schemas, inside the SAME Postgres you already write SQL against — which is why RLS, the one security model you are learning, protects all of them.
Playground, this isn't a screenshot
one Postgres

Five processes. Every arrow above ends at the same database.

PostgREST
Turns your schema into a REST API
HTTP · stateless
reads public (or any schema you expose)

Reads your database's schema on boot and generates one endpoint per table. It runs every request as a low-privilege Postgres role (anon / authenticated) and lets RLS decide what comes back. PostgREST has no database of its own — it is a pure translator sitting in front of yours.

↑ play a little first, then dig in