All courses
Zero → Job-ready

Supabase: The Complete Guide

A Supabase role is a Postgres role wearing an SDK, so this course teaches SQL from your first SELECT, then authorization-as-data until it's instinct, then wires it all into a deployed Next.js app. Real Postgres runs in your browser, so you don't read about Row Level Security: you watch it deny a stranger.

14 tiers · 84 concepts

/ three levels, one journey

Pick where you start.

Level 10/29

Foundations

The mental model, then SQL from zero.

No database experience? Start here.

  • Setup, the Mental Model & Your First Secure App
  • SQL I: Asking Questions of Data
  • SQL II: Tables, Types & Constraints
  • SQL III: Relationships & Joins
  • Composing Queries: CTEs & Window Functions
Level 20/17

Engineering

Correctness, speed, and schema as code.

Comfortable with SELECT and JOIN? Jump in.

  • Correct & Fast
  • Functions & Triggers in the Database
  • Schema as Code
Level 30/16

Security

Auth and Row Level Security, the heart.

This is the part that gets you hired.

  • Auth: Who Is Asking?
  • RLS: The Core
  • RLS at Scale
Level 40/14

Application

The Data API, Next.js, and the services.

Ready to ship a real app? Finish here.

  • The Data API & Your Next.js App
  • Services
Level 50/8

Job-ready

Production, system design, and the interview.

  • Production & the Interview Gauntlet

/ what you'll build

Real apps, not throwaway demos.

devlog.app
publicdraftthe draft is invisible to everyone but its author, enforced by Postgres
Capstone

DevLog, developer journal

A real app with public posts and private drafts, comments, likes, live updates, uploads and search, designed, secured and shipped across the whole course.

  • Schema designed from scratch
  • Every policy written and tested
  • Realtime, storage, search, digest email
ledger.app/acme
Acme IncGlobexusing ( org_id in (select org_id from members where …) )one table, one policy, provably no cross-tenant read
Drill · Multi-tenancy

Ledger, multi-tenant expenses

The single highest-signal project for a Supabase interview: many organizations, one database, and a tenant-isolation guarantee you can prove with a failing test.

  • Org / membership model
  • SECURITY DEFINER helper (no policy recursion)
  • Negative tests: cross-tenant reads return 0 rows
seatmap.app/e/412
seat 4C, one leftABON CONFLICTbookedrejected, not corrupted
Drill · Concurrency

Seatmap, ticket booking

Two people buy the last seat at the same millisecond. Exactly one wins and the database never lies. The transactions-and-races story every backend interview wants to hear.

  • Transactions & isolation levels
  • The lost-update race, and two fixes
  • Atomic booking via ON CONFLICT + RPC
vault.app/files
avatars/storage.foldername(name)[1]= auth.uid()a file is just a row, so the same policy language guards it
Drill · Storage

Vault, private file locker

Files are rows too. Bucket policies, the userId-as-first-folder convention, signed URLs that expire, and image transforms, with nothing readable by a stranger.

  • RLS on storage.objects
  • Signed URLs & upload URLs
  • Image transforms on the fly
recall.app/search
how do I keep my data private?full-text0 matchespgvector"A guide to RLS"embedding <=> query → rankno shared keyword, matched on meaning
Drill · AI

Recall, semantic search

Full-text search finds words. Vector search finds meaning. Build both, then fuse them into hybrid ranking, with embeddings generated by an Edge Function.

  • tsvector + GIN full-text
  • pgvector + HNSW
  • Hybrid ranking (RRF)

/ what you walk away with

Proof you can do the job.

SQL from zero, in a real Postgres

Not a simulator. A full PostgreSQL runs in your browser, so you write SELECTs, joins and security policies against the real thing: same planner, same errors, same behavior as production.

84 concepts, in job-gating order

SQL first, because a Supabase role is a Postgres role wearing an SDK. Every concept ships a visual, the gotcha that bites juniors, and the interview question it attracts.

Authorization you can prove

Row Level Security taught until it's instinct, including the trap that catches everyone: a failed SELECT returns zero rows silently, and only INSERT throws. You'll write tests that assert on nothing coming back.

Five portfolio projects

DevLog, plus a multi-tenant expense tracker, an atomic ticket-booking app, a private file vault, and semantic search, each with migrations in git, policy tests, and CI.

A measured Readiness Score

A 0–100 score across 8 skill dimensions, gated on shipped work: proof you're job-ready, not vibes.

Interview-ready

The real questions: INNER vs LEFT, why COUNT(col) skips NULLs, why you wrap (select auth.uid()), how you'd isolate tenants, and why the service_role key must never reach a browser.

Ready to start Supabase: The Complete Guide?

Free to start. No setup. Build something real today.