Skip to Content
Build an appBackend & data (e.g. Supabase)

Backend & data (e.g. Supabase)

What this layer solves

Most apps need durable data, who is logged in, and sometimes files. You can build that on a BaaS (backend-as-a-service), your own API + DB, or serverless functions talking to a database.

Options

OptionBest forTradeoffs
SupabasePostgres + auth + storage + realtime; generous free tierVendor-specific APIs; learn RLS for real security
FirebaseMobile-first, NoSQL, Google ecosystemDifferent data model than SQL
NeonServerless Postgres — you only pay when the DB is awake and processing queriesYou wire auth and APIs yourself
PlanetScale / RDSMySQL or managed PostgresMore traditional pricing model
Turso (libSQL)Edge-friendly SQLiteDifferent scaling story than big Postgres

NK Wiki default: Supabase — Postgres, row-level security, auth UI patterns, works well with Next.js.

Nick’s Pick — Neon DB

Neon for serverless Postgres — you only pay for the time the database is “awake” and processing queries. Perfect for projects that don’t have constant traffic. Pairs beautifully with Drizzle ORM and Vercel. If you want the full BaaS experience (auth + storage + realtime), Supabase is still great — but for pure database, Neon’s pricing model is hard to beat.

Outline: Supabase mental model

  1. Project = database + API + auth host — create in Supabase dashboard .
  2. Tables — design with migrations; don’t only use the GUI long-term.
  3. Auth — email magic link, OAuth providers; understand JWT flows at a high level.
  4. Row Level Security (RLS)who can read/write which rows — essential before production.
  5. Client vs service role keys — never expose service role in the browser.

When to pick an alternative

  • Firebase if you’re all-in on Google and document-style data fits.
  • Neon + Drizzle if you want maximal control, SQL-first ORM workflows, and pay-per-query pricing.
  • Supabase if you want auth + storage + database all in one dashboard.

Last reviewed: April 2026.