Helpdesk / support 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).
- Customer support desk — tickets with status/priority queues, threaded messages with internal notes, agent profiles, and seed-managed SLA policies.
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*"],
};Helpdesk schema: tickets, messages, agents & SLA policies
- Tickets & status/priority queue — the core support request with open/pending/solved/closed status and low/normal/high/urgent priority, indexed for queue views
- Ticket messages & internal notes — append-only thread rows on each ticket; is_internal hides agent-only notes from the requester
- Agents & team assignment — one agent profile per Better Auth user (unique on user_id), with an optional team field for queue segmentation
- SLA policies per priority — seed-managed response and resolution targets in integer minutes, keyed by priority tier
import { relations, sql } from "drizzle-orm";
import {
boolean,
check,
index,
integer,
pgTable,
text,
timestamp,
unique,
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 TicketStatus = "open" | "pending" | "solved" | "closed";
export type TicketPriority = "low" | "normal" | "high" | "urgent";
/** A customer support request. Requester is a Better Auth user. */
export const tickets = pgTable(
"tickets",
{
id: uuid("id").primaryKey().defaultRandom(),
// Better Auth's user.id is text — match it, don't recast.
requesterId: text("requester_id")
.notNull()
.references(() => user.id, { onDelete: "cascade" }),
subject: text("subject").notNull(),
status: text("status")
.$type<TicketStatus>()
.notNull()
.default("open"),
priority: text("priority")
.$type<TicketPriority>()
.notNull()
.default("normal"),
createdAt: timestamp("created_at", { withTimezone: true })
.notNull()
.defaultNow(),
},
(t) => [
index("idx_ticket_requester").on(t.requesterId),
// Drives the queue view: filter/sort by status then priority.
index("idx_ticket_status_priority").on(t.status, t.priority),
check(
"tickets_status_check",
sql`${t.status} in ('open','pending','solved','closed')`,
),
check(
"tickets_priority_check",
sql`${t.priority} in ('low','normal','high','urgent')`,
),
],
);
/** The thread on a ticket. is_internal hides agent-only notes from the requester. */
export const ticketMessages = pgTable(
"ticket_messages",
{
id: uuid("id").primaryKey().defaultRandom(),
ticketId: uuid("ticket_id")
.notNull()
.references(() => tickets.id, { onDelete: "cascade" }),
authorId: text("author_id")
.notNull()
.references(() => user.id, { onDelete: "cascade" }),
body: text("body").notNull(),
isInternal: boolean("is_internal").notNull().default(false),
createdAt: timestamp("created_at", { withTimezone: true })
.notNull()
.defaultNow(),
},
(t) => [
// Loads a ticket's conversation oldest-first.
index("idx_message_ticket").on(t.ticketId, t.createdAt),
],
);
/** A user who staffs the desk. One agent record per user; team groups the queue. */
export const agents = pgTable(
"agents",
{
id: uuid("id").primaryKey().defaultRandom(),
userId: text("user_id")
.notNull()
.references(() => user.id, { onDelete: "cascade" }),
team: text("team"),
createdAt: timestamp("created_at", { withTimezone: true })
.notNull()
.defaultNow(),
},
(t) => [
// One agent profile per user (a user is an agent or they are not).
unique("agents_user_unique").on(t.userId),
],
);
/** Response/resolution targets per priority (seed-managed). Minutes keep math integer. */
export const slaPolicies = pgTable(
"sla_policies",
{
id: uuid("id").primaryKey().defaultRandom(),
name: text("name").notNull(),
priority: text("priority").$type<TicketPriority>().notNull(),
firstResponseMins: integer("first_response_mins").notNull(),
resolveMins: integer("resolve_mins").notNull(),
},
(t) => [
check(
"sla_policies_priority_check",
sql`${t.priority} in ('low','normal','high','urgent')`,
),
],
);
export const ticketsRelations = relations(tickets, ({ one, many }) => ({
requester: one(user, {
fields: [tickets.requesterId],
references: [user.id],
}),
messages: many(ticketMessages),
}));
export const ticketMessagesRelations = relations(ticketMessages, ({ one }) => ({
ticket: one(tickets, {
fields: [ticketMessages.ticketId],
references: [tickets.id],
}),
author: one(user, {
fields: [ticketMessages.authorId],
references: [user.id],
}),
}));
export const agentsRelations = relations(agents, ({ one }) => ({
user: one(user, { fields: [agents.userId], 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.
- Status and priority are text + CHECK (not pgEnum), so adding a new value (e.g. 'escalated') ships without an ALTER TYPE migration — consistent with the house style in packages/db/src/schema.ts.
- agents carries a unique constraint on user_id (one profile per user) and sla_policies carries no unique on priority, allowing multiple named policies at the same priority tier for different customer tiers.
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, built for CRM
- Same stack, built for LMS (learning platform)
- Same stack, built for Project management
- Same stack, built for Booking / scheduling
- Same stack, with Clerk instead of Better Auth
- 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