SQLite or PostgreSQL — which should I pick?
2 min
SQLite for solo / local work. PostgreSQL for anything you'll deploy or share.
Avery's scaffold wizard asks which database to use. Two factors decide:
1. Are you the only user? SQLite is fine. The database file lives next to your code; backups are a `cp`. 2. Will this run somewhere remote? PostgreSQL is the right pick. SQLite needs the file local to the app; serverless platforms (Vercel) need an external Postgres anyway.
Note: the schema-composer runs `downgradeEnumsForSqlite` for SQLite scaffolds — every Prisma `enum` block becomes a `String` field with `@default("...")`. Your generated code still treats those as typed values; the difference is only in the on-disk schema. PostgreSQL keeps real enums.
You can switch later — Prisma migrations work for both, and the generated code is database-agnostic.
Live recipes need the desktop
This article is a static preview. The in-app Help sidecar inside Avery NXR can fire each step against your live project — install the desktop to use it interactively.