Developer Workflow Guide
How to use SchemaLens alongside the Supabase CLI in your day-to-day development process, and how source control ties them together.
Step 1 of 12
Two Tools, One Workflow
How SchemaLens and Supabase CLI complement each other.
Complementary Roles
Neither tool replaces the other. Supabase CLI manages how changes happen. SchemaLens tracks what the schema looks like after those changes.
| Supabase CLI | SchemaLens CLI | |
|---|---|---|
| Philosophy | Imperative — ordered migration steps | Declarative — current schema state |
| Artifacts | supabase/migrations/*.sql (sequential) | schema/<env>/ (per-object SQL files) |
| Answers | "How did the schema get here?" | "What does the schema look like now?" |
| Strength | Authoring changes, local dev, migration replay | Auditing state, cross-env diffing, PR reviews |
1 / 12
Quick Reference
Supabase CLI
supabase start
supabase migration new <name>
supabase db diff
supabase db reset
supabase db push
SchemaLens CLI
schemalens init
schemalens pull --env <env>
schemalens build --migrations <dir>
schemalens status --env <env>
schemalens deploy --env <env>
schemalens diff --from <env> --to <env>
schemalens upgrade