0

Supabase vs the alternatives & the README that converts

Interviewused in ~65% of apps

The product round always lands on two questions: "compare Supabase, Firebase, and Convex — where does each win?" and, separately, whoever reads your portfolio decides whether you get the call in the time it takes to skim one file. Neither question has a memorized answer. Both are testable against something concrete: the architecture you can actually defend, and the README section that either answers "is tenant data isolated, and is it tested?" in under 60 seconds, or doesn't.

Core idea. Supabase's whole pitch is Postgres with services attached: your data model is relational tables, your authorization is RLS written in the same SQL you already know, and every connection — your app, a cron job, a migration script — passes through the identical security layer. Firebase's Firestore is a document store gated by a separate rules DSL that only governs SDK access (the Admin SDK bypasses it entirely). Convex is a TypeScript-native reactive backend where the database is an implementation detail and every query is a live subscription by default. None of the three is strictly better; the interview-grade answer names the tradeoff each makes and ties it to a concrete project shape — and the same discipline (name the tradeoff, show the artifact) is what turns a README into an interview.
Playground, this isn't a screenshot
the README that converts — 8 sections60-second test: section 3 + 5
reads junior

"RLS is enabled."

reads senior

"RLS is ON for every table. Here are the policies. Here is the tenant-isolation guarantee. The secret key is server-only." Linked to the actual policy files.

-- policies/documents.sql
create policy "org isolation - read documents"
  on documents for select to authenticated
  using ( org_id = any (array(select public.user_org_ids())) );
The rule of thumb:a reviewer should be able to answer "is tenant data isolated, and is it tested?" from sections 3 and 5 alone, in under 60 seconds. If they can, you get the interview.
↑ play a little first, then dig in