Skip to main content

Guide

Postgres for indie SaaS

When to use Supabase vs. raw Postgres, and the schema patterns we copy into every project.

KoustavNovember 2, 20258 min readDevelopment

Postgres is the default for indie SaaS. Supabase is how we usually host it.

When Supabase wins

You want auth, Postgres, storage, and edge functions in one dashboard. MVPs and early-stage products.

When raw Postgres wins

Existing infra, complex migrations, or team already on RDS/Neon with custom tooling.

Schema patterns we copy

users table mapped to auth provider id

created_at / updated_at on every table

Soft deletes only when you actually need audit trails

JSONB for flexible metadata, not as a substitute for relations

Migrations

We use Supabase migrations or Prisma depending on client preference. Both work, pick one and stick with it.

Want this built for you?

Fixed-scope MVP sprints and AI integrations. Same stack as this guide.