Managed Postgres: Neon, Supabase, RDS

The default for production should usually be managed

Self-hosting Postgres is real work: backups, monitoring, version upgrades, patching, replication, failover. Managed providers handle all of that for a relatively modest premium. For most teams, the right starting point is managed; self-host only when you have a measured reason.

The major options

Supabase — managed Postgres + Auth + Storage + Realtime + edge functions. Generous free tier; opinionated platform-style approach. Great fit for solo and small-team SaaS.
Neon — serverless Postgres with branching (each git branch can have its own DB). Pay for what you use. Strong for ephemeral preview environments.
RDS / Aurora (AWS) — the enterprise default. Lots of knobs, predictable pricing, strong at scale.
AlloyDB (GCP), Azure Flexible Server — cloud-native equivalents.
Railway, Render, Fly.io — developer-experience focused; great for indie projects.

Things to compare

Free tier (for prototyping), backup automation, point-in-time recovery, supported extensions (pgvector? Anything more exotic?), connection pooling included, scale-up path, region availability, support story.

Code

Connect to a managed Postgres·bash

# Most providers give you a connection string in the dashboard
psql 'postgresql://app:****@db.zyx.supabase.co:5432/postgres?sslmode=require'

# Many require sslmode=require; check provider docs
psql 'postgresql://user:****@ep-x-123.us-east-2.aws.neon.tech/myapp?sslmode=require'

Supabase CLI essentials·bash

supabase login
supabase link --project-ref abc12345
supabase db push --include-all       # apply local migrations to remote
supabase db dump --file local.sql    # logical dump from remote
supabase secrets set FOO=bar          # env var for edge functions

Managed Postgres: Neon, Supabase, RDS

The default for production should usually be managed

The major options

Things to compare

Code

External links

Exercise

Progress

Comments 0