Database and migrations

Database requirements

• Postgres 16+ (Neon recommended)
• pgvector extension enabled
• Pooled connection string for serverless (Neon -pooler host)

Migrations include extension setup in drizzle/0000_init.sql.

Running migrations

# With DATABASE_URL in .env.local
bun run db:migrate

The migrate script (scripts/migrate.ts) applies all SQL files in drizzle/ in order.

Migration history

Corsair creates additional tables via bun run corsair:setup — not managed by Drizzle migrations.

Drizzle Studio

Inspect data interactively:

bun run db:studio

Useful tables for debugging:

• users — tenant IDs, backfill status
• classifications — lanes, embeddings, scheduling intent
• webhook_logs — inbound webhook audit
• snoozes, scheduled_sends, thread_meetings

Schema source of truth

Application schema: src/lib/db/schema.ts

Auth schema: src/lib/db/auth-schema.ts (re-exported from schema)

Key enums:

• triage_lane: reply, schedule, fyi, done
• priority: high, medium, low
• draft_tone: professional, friendly, brief
• scheduled_send_status: pending, sent, cancelled, failed

pgvector embeddings

classifications.embedding is a 768-dimensional vector (EMBEDDING_DIMENSIONS in providers.ts).

Index strategy uses user-scoped queries:

• classifications_user_idx
• classifications_user_thread_idx
• classifications_user_provider_idx

Semantic search filters by userId and active embedding_provider.

Production migrations

Migrations run manually against Neon — they are not part of the Vercel build.

Recommended flow:

1. Set DATABASE_URL to production Neon URL locally
2. Run bun run db:migrate
3. Run bun run corsair:setup if fresh database
4. Deploy app

Never run corsair:reset against production unless you intend to wipe OAuth tokens.

Related

• Database schema reference
• Local development