Database Setup & Configuration

diy-analytics stores all data in PostgreSQL, using Drizzle ORM and the postgres-js driver. Any standard PostgreSQL 14+ database with SSL works.

---

Why connection pooling matters

Serverless platforms like Vercel spin up many short-lived compute workers under load. If each worker opens a direct connection to Postgres, you'll exceed max_connections and start dropping requests.

A connection pooler — PgBouncer, or the native poolers built into Neon and Supabase — keeps a shared pool of persistent connections and multiplexes requests across them in transaction mode.

---

Supported providers

---

1. Neon (serverless Postgres) — recommended

In your Neon dashboard:

1. Select your database branch.
2. In the connection details, toggle to Pooled connection — look for the -pooler subdomain.
3. Copy the URI:

2. Supabase

In your Supabase project dashboard:

1. Go to Project Settings → Database → Connection string.
2. Select Transaction Mode (port 6543) — not Session Mode (port 5432).
3. Copy the pooled URI:

No additional Supabase SDKs or anon keys are needed — diy-analytics connects over standard PostgreSQL.

3. Vercel Postgres

If you're using the Vercel Postgres / Neon integration:

4. Railway & self-hosted PostgreSQL

Any standard PostgreSQL connection string works:

5. Local Docker container

For local development and contributions:

---

Applying schema migrations

When provisioning a new database, or upgrading an existing deployment, run the Drizzle migration runner:

Database commands

---

Next steps