CRM on Next.js 16 (App Router) + Postgres (Neon) + Better Auth
Type-checked against the real SDKs, migration applied to a live Postgres, pooling tested — then tracked for upstream drift and re-verified when it moves. How we verify →
What you're getting
- Next.js 16 App Router — file-based routing, server components, and the Edge proxy (Next 16's renamed middleware).
- Postgres on Neon via Drizzle ORM and the postgres-js driver.
- Better Auth — self-hosted auth running inside your app against your Postgres (Drizzle adapter).
- Sales CRM — companies, contacts, named pipelines, deal-stage tracking, and an append-only activity trail.
Setup
bun add next react react-dom drizzle-orm postgres better-authEnvironment variables:
DATABASE_URL— Neon pooled (-pooler) connection stringBETTER_AUTH_SECRET— generate with `openssl rand -base64 32`BETTER_AUTH_URL— your app's base URL
Apply the schema: bunx drizzle-kit push
Initialization
src/lib/db.ts — Database client
import { drizzle } from "drizzle-orm/postgres-js";
import postgres from "postgres";
// Neon pooled endpoint = PgBouncer transaction mode → prepared statements off.
// ponytail: single module-level client; the serverless runtime + PgBouncer do
// the pooling, so no custom pool/globalThis singleton dance needed.
const client = postgres(process.env.DATABASE_URL!, { prepare: false });
export const db = drizzle({ client });src/lib/auth.ts — Auth instance
// Better Auth instance (self-hosted, Next.js 16 (App Router)).
import { betterAuth } from "better-auth";
import { drizzleAdapter } from "better-auth/adapters/drizzle";
// Reuse the SAME postgres-js/Drizzle client the db slice exported in
// src/lib/db.ts — Better Auth shares the pooled `DATABASE_URL` connection.
import { db } from "./db";
export const auth = betterAuth({
// Drizzle adapter over the shared client; provider "pg" => Postgres DDL
// for Better Auth's own user/session/account/verification tables.
database: drizzleAdapter(db, { provider: "pg" }),
// ponytail: email+password is the shortest real auth that works out of
// the box — add socialProviders / plugins here when the app needs them.
emailAndPassword: { enabled: true },
secret: process.env.BETTER_AUTH_SECRET,
baseURL: process.env.BETTER_AUTH_URL,
});
export type Session = typeof auth.$Infer.Session;app/api/auth/[...all]/route.ts — Route handler
// Mount Better Auth on Next's route layer.
import { toNextJsHandler } from "better-auth/next-js";
import { auth } from "@/lib/auth";
export const { GET, POST } = toNextJsHandler(auth);proxy.ts — Route protection
// Session-protection proxy for Next.js 16 (App Router) (Next 16 renamed middleware.ts → proxy.ts).
// ponytail: getSessionCookie only checks the cookie EXISTS (no DB hit at
// the Edge runtime) — do the real auth.api.getSession() check inside
// protected Server Components / route handlers. This just bounces
// logged-out users before render.
import { NextResponse, type NextRequest } from "next/server";
import { getSessionCookie } from "better-auth/cookies";
export function proxy(request: NextRequest) {
const sessionCookie = getSessionCookie(request);
if (!sessionCookie) {
return NextResponse.redirect(new URL("/sign-in", request.url));
}
return NextResponse.next();
}
export const config = {
// ponytail: guard the SaaS app surface; widen the matcher per app-type.
matcher: ["/dashboard/:path*", "/settings/:path*"],
};Sales CRM schema: companies, contacts, pipelines, deals & activities
- Companies & contacts — account records (companies de-duped on domain) and the contacts that belong to them, with nullable company FK to support unattached leads
- Pipelines & deals — named sales pipelines and the opportunities (deals) moving through them, each carrying a contact FK, an owner FK to Better Auth user, and amount stored as integer cents
- Deal stage tracking — stage column on deals enforced by CHECK constraint with an index that powers pipeline-board grouping by stage
- Activity interaction log — append-only calls/emails/notes logged against a deal by a Better Auth actor, forming the per-deal audit timeline
import { relations, sql } from "drizzle-orm";
import {
bigint,
check,
index,
pgTable,
text,
timestamp,
uuid,
} from "drizzle-orm/pg-core";
// Better Auth owns identity; we only reference its `user` table by id.
import { user } from "./auth-schema";
export type DealStage = "lead" | "qualified" | "won" | "lost";
export type ActivityType = "call" | "email" | "note";
/** Account record: the organization a set of contacts belongs to. */
export const companies = pgTable(
"companies",
{
id: uuid("id").primaryKey().defaultRandom(),
name: text("name").notNull(),
// Primary web domain — opaque key we de-dupe accounts on.
domain: text("domain"),
createdAt: timestamp("created_at", { withTimezone: true })
.notNull()
.defaultNow(),
},
(t) => [index("idx_company_domain").on(t.domain)],
);
/** A person we sell to. Company is nullable (a lead can exist before we know
* their employer); owner is the Better Auth user accountable for the contact. */
export const contacts = pgTable(
"contacts",
{
id: uuid("id").primaryKey().defaultRandom(),
// Nullable: unattached leads get a company once qualified.
companyId: uuid("company_id").references(() => companies.id, {
onDelete: "set null",
}),
email: text("email").notNull(),
name: text("name"),
// Better Auth's user.id is text — match it, don't recast.
ownerId: text("owner_id")
.notNull()
.references(() => user.id, { onDelete: "cascade" }),
createdAt: timestamp("created_at", { withTimezone: true })
.notNull()
.defaultNow(),
},
(t) => [
index("idx_contact_company").on(t.companyId),
index("idx_contact_owner").on(t.ownerId),
],
);
/** Named sales pipeline deals move through (e.g. Inbound, Enterprise). */
export const pipelines = pgTable("pipelines", {
id: uuid("id").primaryKey().defaultRandom(),
name: text("name").notNull(),
createdAt: timestamp("created_at", { withTimezone: true })
.notNull()
.defaultNow(),
});
/** An open/closed opportunity against a contact, in a pipeline, owned by a
* Better Auth user. amount in integer cents (no float money). */
export const deals = pgTable(
"deals",
{
id: uuid("id").primaryKey().defaultRandom(),
contactId: uuid("contact_id")
.notNull()
.references(() => contacts.id, { onDelete: "cascade" }),
pipelineId: uuid("pipeline_id")
.notNull()
.references(() => pipelines.id),
ownerId: text("owner_id")
.notNull()
.references(() => user.id, { onDelete: "cascade" }),
title: text("title").notNull(),
// ponytail: money as integer cents — no float, no numeric type churn.
amountCents: bigint("amount_cents", { mode: "number" })
.notNull()
.default(0),
stage: text("stage").$type<DealStage>().notNull().default("lead"),
closeDate: timestamp("close_date", { withTimezone: true }),
createdAt: timestamp("created_at", { withTimezone: true })
.notNull()
.defaultNow(),
},
(t) => [
// Drives the pipeline board "deals grouped by stage" query.
index("idx_deal_stage").on(t.stage),
index("idx_deal_contact").on(t.contactId),
check(
"deals_stage_check",
sql`${t.stage} in ('lead','qualified','won','lost')`,
),
],
);
/** Append-only interaction trail against a deal, logged by a Better Auth user. */
export const activities = pgTable(
"activities",
{
id: uuid("id").primaryKey().defaultRandom(),
dealId: uuid("deal_id")
.notNull()
.references(() => deals.id, { onDelete: "cascade" }),
// Who logged the interaction.
actorId: text("actor_id")
.notNull()
.references(() => user.id, { onDelete: "cascade" }),
type: text("type").$type<ActivityType>().notNull().default("note"),
body: text("body"),
occurredAt: timestamp("occurred_at", { withTimezone: true })
.notNull()
.defaultNow(),
},
(t) => [
// Drives the per-deal timeline (most-recent-first).
index("idx_activity_deal_time").on(t.dealId, t.occurredAt),
check(
"activities_type_check",
sql`${t.type} in ('call','email','note')`,
),
],
);
export const companiesRelations = relations(companies, ({ many }) => ({
contacts: many(contacts),
}));
export const contactsRelations = relations(contacts, ({ one, many }) => ({
company: one(companies, {
fields: [contacts.companyId],
references: [companies.id],
}),
owner: one(user, { fields: [contacts.ownerId], references: [user.id] }),
deals: many(deals),
}));
export const pipelinesRelations = relations(pipelines, ({ many }) => ({
deals: many(deals),
}));
export const dealsRelations = relations(deals, ({ one, many }) => ({
contact: one(contacts, {
fields: [deals.contactId],
references: [contacts.id],
}),
pipeline: one(pipelines, {
fields: [deals.pipelineId],
references: [pipelines.id],
}),
owner: one(user, { fields: [deals.ownerId], references: [user.id] }),
activities: many(activities),
}));
export const activitiesRelations = relations(activities, ({ one }) => ({
deal: one(deals, { fields: [activities.dealId], references: [deals.id] }),
actor: one(user, { fields: [activities.actorId], references: [user.id] }),
}));
Connection & security
## Next.js 16 ↔ Postgres pooling (Neon pooled endpoint, PgBouncer transaction mode)
Connect through Neon's **pooled** endpoint (`-pooler` host) via `DATABASE_URL`. Serverless
functions are short-lived and concurrent, so PgBouncer in **transaction mode** is what keeps
Postgres' connection ceiling from being blown.
### `prepare: false` is mandatory
Transaction-mode PgBouncer hands each transaction a different backend, so server-side prepared
statements (postgres-js' default) silently break across the pool. Disable them on the client:
`postgres(url, { prepare: false })`. This is also why **Drizzle, not Prisma**, is paired here —
Prisma's prepared-statement reliance is a blocked intersection on this endpoint.
### Connection reuse
- Construct the postgres-js client at **module scope** (`src/lib/db.ts`) so warm function
instances reuse one socket instead of opening one per request.
- Cap the driver pool small — `max: 1` per instance. The shared pool lives in PgBouncer, not in
your function; a large per-instance `max` just multiplies idle connections across instances.
- Keep `idle_timeout` ~20s and `connect_timeout` ~10s so frozen instances release backends fast.
### No session-level features
Transaction mode forbids anything that spans transactions on one backend: `LISTEN/NOTIFY`,
session-scoped `SET`, advisory-lock sessions, server-side cursors, and `WITH HOLD`. Need any of
those? Use Neon's **direct** (non-pooled) endpoint for that path only.
### Thresholds
- Drizzle/postgres-js: `prepare: false`, `max: 1`, `idle_timeout: 20`, `connect_timeout: 10`.
- Neon Free pooled budget is ~10k client connections; keep concurrency well under the project's
`max_connections` (often 100–900 by plan) by leaning on PgBouncer, never on driver pooling.
Decisions & compatibility
- Auth runs in proxy.ts (Next 16's renamed middleware) on the Edge runtime: it gates on the session cookie's presence only — full session validation happens in Server Components and route handlers, not in the proxy.
- prepare: false is mandatory — Neon's pooled endpoint is PgBouncer in transaction mode, where server-side prepared statements break across the pool.
- Drizzle is paired here (not Prisma): Prisma's prepared-statement reliance is incompatible with transaction-mode pooling.
- Self-hosted: Better Auth creates and owns the user/session/account tables in your database, so app-type schemas can foreign-key to `user` directly.
- Deal stage is text + CHECK ('lead','qualified','won','lost') on the deals table — new stages ship without an ALTER TYPE migration; the idx_deal_stage index drives the pipeline board's 'deals grouped by stage' query.
- activities is append-only (no updates, no deletes cascaded from deal): the per-deal timeline is always a raw log, never a mutated summary, queried via idx_activity_deal_time (deal_id, occurred_at).
Related stacks
- Same stack, built for SaaS
- Same stack, built for AI Wrapper
- Same stack, built for E-commerce store
- Same stack, built for Marketplace
- Same stack, built for Blog / CMS
- Same stack, with Clerk instead of Better Auth
- Same stack, built for LMS (learning platform)
- Same stack, built for Project management
- Same stack, built for Helpdesk / support
- Same stack, built for Booking / scheduling
- Same stack, built for Social network
- Same stack, built for Forum / community
- Same stack, built for Newsletter platform
- Same stack, built for Job board
- Same stack, built for Fintech ledger
- Same stack, built for Notes / knowledge base
- Same stack, built for Video platform
- Same stack, built for Product analytics
- Same stack, built for Fitness tracker
- Same stack, built for IoT telemetry