Supabase

What Supabase is for

If you are building a web app as a one-person business, you usually need three things on the backend: a database, user authentication, and somewhere to store user-uploaded files. Historically that meant either a) building from scratch on a VPS or b) using Firebase and accepting Google lock-in.

Supabase is the third option. Postgres as the database, built-in auth that handles email/password, magic links, OAuth, and social providers, plus storage for files and a realtime subscription system. All in one dashboard, with a generous free tier and an escape hatch (it is open source and self-hostable).

For most indie SaaS launches in 2026, Supabase is the fastest path from "I have an idea" to "users can sign up and use it".

What you actually use

• Database. A real Postgres database with tables, foreign keys, indexes, and standard SQL. The dashboard has a table editor for non-technical use and an SQL editor for everything else.
• Auth. Sign up, sign in, password reset, magic links, OAuth (Google, GitHub, Apple, etc.) all built in. Generates JWTs your frontend uses for authenticated requests.
• Row-Level Security. Postgres RLS policies tied to the authenticated user. Lets you write rules like "users can only read their own rows" without writing custom backend logic.
• Storage. S3-compatible storage with auth-aware policies. Upload images, attach to records.
• Edge Functions. Deno-based serverless functions that run close to your database. Useful for webhooks and small backend logic.

Where Supabase falls short

The free tier auto-pauses inactive projects after 7 days. The first request after that is slow (5-10 seconds) while the project wakes up. Fine for hobby work, annoying for anything in active use that has dry weeks.

The Pro tier ($25/mo) is reasonable but the jump from free is steep. There is no middle plan for "hobby project with light traffic".

Edge Functions on Supabase are usable but less robust than Vercel or Cloudflare Workers. For latency-sensitive logic, run that elsewhere and let Supabase be the database.

The dashboard tries to do many things and can feel dense. Once you know which tabs you need (Table Editor, SQL Editor, Auth, Storage), the rest fades into the background.

Comparison points

• Firebase: similar capability, more polished UX, NoSQL not Postgres. The lock-in is the main downside vs Supabase.
• PlanetScale: MySQL-focused, no built-in auth or storage. Pure database play.
• Neon: Postgres, same model, simpler scope (database only).
• Self-host Postgres: cheapest at scale, you become a DBA.

Verdict

For one-person indie SaaS, Supabase is the right default in 2026. The free tier is enough for validation, the Pro tier is reasonable for production traffic, and the open-source escape hatch removes the lock-in fear that haunts Firebase.