Environments: local, preview, production

Purpose

Three environments, clear rules for what runs where.

Env	What	Data	Who
`local`	your machine, `npm run dev`	local Supabase (Docker) or the dev Supabase project	you
`preview`	Vercel preview per PR	dev Supabase project, seeded	reviewers
`prod`	Vercel production from `main`	prod Supabase project	users

Each web tool has two Supabase projects: <tool>-dev and <tool>-prod. Never point local at prod.
Preview URLs are shareable inside the team only (they can expose dev data).
Migrations run against dev first, then prod as part of the release (09.03).
Prod config changes are made through Vercel/Supabase dashboards by the owner and noted in the release.

Owner: Matt · Last reviewed: 2026-09