Forum / community 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).
- Forum / community — slug-keyed category taxonomy, threaded discussions with open/locked status and pinning, and per-reply up/down votes.
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*"],
};Forum / community schema: categories, threads, replies & votes
- Categories taxonomy — slug-unique top-level categories each thread must belong to exactly one of
- Threads (status & pinning) — threads scoped to a category and author, with open/locked status and an is_pinned flag for surfacing
- Thread replies — flat replies within a thread, each carrying a body and an author FK into Better Auth's user table
- Reply votes — append-style up/down votes on replies, uniquely constrained per (reply, voter) pair
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 ThreadStatus = "open" | "locked";
/** Top-level taxonomy. Every thread hangs off exactly one category. */
export const categories = pgTable(
"categories",
{
id: uuid("id").primaryKey().defaultRandom(),
slug: text("slug").notNull().unique(),
name: text("name").notNull(),
createdAt: timestamp("created_at", { withTimezone: true })
.notNull()
.defaultNow(),
},
(t) => [index("idx_category_slug").on(t.slug)],
);
/** A discussion thread: lives in one category, authored by one user. */
export const threads = pgTable(
"threads",
{
id: uuid("id").primaryKey().defaultRandom(),
categoryId: uuid("category_id")
.notNull()
.references(() => categories.id, { onDelete: "cascade" }),
// Better Auth's user.id is text — match it, don't recast.
authorId: text("author_id")
.notNull()
.references(() => user.id, { onDelete: "cascade" }),
title: text("title").notNull(),
status: text("status").$type<ThreadStatus>().notNull().default("open"),
isPinned: boolean("is_pinned").notNull().default(false),
createdAt: timestamp("created_at", { withTimezone: true })
.notNull()
.defaultNow(),
},
(t) => [
// Drives the category listing (newest/pinned threads per category).
index("idx_thread_category").on(t.categoryId),
index("idx_thread_author").on(t.authorId),
check(
"threads_status_check",
sql`${t.status} in ('open','locked')`,
),
],
);
/** A reply within a thread, authored by one user. */
export const threadReplies = pgTable(
"thread_replies",
{
id: uuid("id").primaryKey().defaultRandom(),
threadId: uuid("thread_id")
.notNull()
.references(() => threads.id, { onDelete: "cascade" }),
authorId: text("author_id")
.notNull()
.references(() => user.id, { onDelete: "cascade" }),
body: text("body").notNull(),
createdAt: timestamp("created_at", { withTimezone: true })
.notNull()
.defaultNow(),
},
(t) => [
// Drives the thread view (replies in order for a given thread).
index("idx_reply_thread").on(t.threadId),
index("idx_reply_author").on(t.authorId),
],
);
/** One vote per (reply, voter). value is -1 (down) or +1 (up). */
export const replyVotes = pgTable(
"reply_votes",
{
id: uuid("id").primaryKey().defaultRandom(),
replyId: uuid("reply_id")
.notNull()
.references(() => threadReplies.id, { onDelete: "cascade" }),
voterId: text("voter_id")
.notNull()
.references(() => user.id, { onDelete: "cascade" }),
value: integer("value").notNull(),
createdAt: timestamp("created_at", { withTimezone: true })
.notNull()
.defaultNow(),
},
(t) => [
// A voter casts at most one vote per reply — the vote's identity.
unique("reply_votes_reply_voter_unique").on(t.replyId, t.voterId),
check("reply_votes_value_check", sql`${t.value} in (-1,1)`),
],
);
export const categoriesRelations = relations(categories, ({ many }) => ({
threads: many(threads),
}));
export const threadsRelations = relations(threads, ({ one, many }) => ({
category: one(categories, {
fields: [threads.categoryId],
references: [categories.id],
}),
author: one(user, { fields: [threads.authorId], references: [user.id] }),
replies: many(threadReplies),
}));
export const threadRepliesRelations = relations(
threadReplies,
({ one, many }) => ({
thread: one(threads, {
fields: [threadReplies.threadId],
references: [threads.id],
}),
author: one(user, {
fields: [threadReplies.authorId],
references: [user.id],
}),
votes: many(replyVotes),
}),
);
export const replyVotesRelations = relations(replyVotes, ({ one }) => ({
reply: one(threadReplies, {
fields: [replyVotes.replyId],
references: [threadReplies.id],
}),
voter: one(user, { fields: [replyVotes.voterId], 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.
- Vote identity is enforced by a composite unique on (reply_id, voter_id): one vote per reply per voter, value constrained to (-1, 1) via CHECK rather than a separate enum.
- Thread status uses text + CHECK ('open','locked') so new statuses ship without an ALTER TYPE migration; the same pattern applies to vote value.
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 Helpdesk / support
- Same stack, built for Booking / scheduling
- Same stack, built for Social network
- 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, with Clerk instead of Better Auth
- Same stack, built for Video platform
- Same stack, built for Product analytics
- Same stack, built for Fitness tracker
- Same stack, built for IoT telemetry