Supabase
First met in aicp-c3-basecamp-02 · Backend, hosting & code
SupabaseFirst met in aicp-c3-basecamp-02 · Backend, hosting & code
A managed back end in a box — Postgres database, auth, storage, and edge functions — with a generous free tier, so vibe-coded apps get real infrastructure.
You're graduating an app out of a vibe-coding platform's walled garden and want real Postgres you control — vs Lovable Cloud's zero-setup lock-in or Convex.
Row-level security (RLS) — table-level protection the course treats as non-negotiable
Real Postgres underneath — nothing proprietary to migrate off later
Edge functions keep API keys server-side, out of your front end
Hosts your database with row-level security (RLS) per table
Handles signup/login (email validation, OAuth) without you writing auth
Runs server-side edge functions so API keys stay off the front end
Migrates via SQL you paste into its editor (or CLI when working locally)
Doesn't protect data unless RLS is actually enabled — real Lovable apps have leaked tables
Doesn't wire smoothly into Lovable anymore — Lovable pushes its own Cloud instead (BC2's live pivot)
Doesn't replace deployment — the app still needs hosting (Vercel etc.)
The back end for anything you graduate out of a vibe-coding platform: local dev with Claude Code + Supabase + Vercel is the course's 'serious' stack.
Backend, hosting & code
The KB is static-file by design; no multi-user backend needed.
If the course site ever grows accounts/notes sync, this is the default choice; RLS discipline from BC2 applies to any future client build.
current
lovable-cloud: Lovable's bundled replacement; speed vs lock-in trade-off
convex: mentioned as the peer managed-backend
claude-code: Supabase MCP makes migrations conversational from local dev
| Session | Coverage | Moment | What happened |
|---|---|---|---|
| Basecamp 2: Vibe Coding | demonstrated | 1:16:52 | Org/project creation, password, automatic RLS, project URL + publishable/service-role keys, SQL editor migration run creating profiles/projects/tasks tables — then abandoned for Lovable Cloud when wiring fought back |
| Session 19: Content Strategy Pipeline — the YouTube Growth Stack, Built by an Agent Team of Chats | demonstrated | Database layer via MCP server; its jobs chat reported done first | |
| Session 4: How to Build Micro Prototypes | mentioned | 1:58:11 | The database you'd configure locally when a complex app leaves Lovable Cloud — deferred to the build phase |
| Session 10: Building on Cursor & connect with AI workflows | mentioned | 1:11:06 | The beginner-friendly database alternative (also handles auth) |
| Session 12: Claude Code — Design & Building Agents (App-First: a Game, a GTM Board, and a Live Deploy) | mentioned | 2:36:16 | Named (with MongoDB) as the database path deferred to a future technical session |
| Session 14: Claude Code — Advanced Workflows | mentioned | 0:21:30 | Listed among platforms whose CLIs plug into Claude Code |
| Session 16: GitHub 101 — Fundamentals & Essentials | mentioned | 0:24:10 | In the multi-cloud example (database piece); also surfaced in Sayed's escape-room variant (Supabase auth on the membership door, 2:24:38) |
| Session 18: Nano Banana + Veo 3.1 Multi-Shot Video — UGC Genie, an AI-UGC Product Built Live | mentioned | Named (with MongoDB) as the missing persistence layer — reload currently loses state | |
| Session 24: Building a Marketing OS — Sector-Agnostic Command Center on an Open-Source Stack | mentioned | Spotted configured in a cohort member's parallel build ('that's crazy that Supabase is also set up') | |
| AI Masterclass: Exploring Antigravity 2 — Four Products, Four Slash Commands, and Two Live Builds | mentioned | 'Antigravity can handle Supabase — give it the information' (as-heard 'Superbase') | |
| AI Sprint: Vibe Coding to Production — Day 1 (Deployment, DNS, and the Five Locks) | mentioned | Named as the Postgres-managed alternative; 'higher, costlier side' vs Atlas in his view | |
| AI Sprint: Windsurf & Devin — Day 1 (Vibe to Agentic: GitHub as Pizza, the Four Spec Concerns, and the IDE Lineage) | mentioned | Auth via edge functions — 'don't ask me what an edge function is, for now just take it' |