AI Wrapper 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).
- AI-wrapper app — per-user profile extending Better Auth, per-call token metering, and append-only prompt/completion history.
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*"],
};AI app schema: user profiles, token metering & prompt logs
- User profiles extending Better Auth — one profile per Better Auth user, carrying default model preference and soft monthly token budget
- Per-call token usage & cost metering — append-only rows (one per upstream LLM call) that drive the per-user budget rollup and cost reporting
- Prompt & completion log history — auditable record of every exchange — prompt, completion, token split, latency, and ok/error/filtered status
import { relations, sql } from "drizzle-orm";
import {
bigint,
check,
index,
integer,
jsonb,
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 CallStatus = "ok" | "error" | "filtered";
/** One profile per Better Auth user — extends identity with AI-app preferences
* and the soft monthly token budget the metering layer enforces. */
export const userProfiles = pgTable(
"user_profiles",
{
id: uuid("id").primaryKey().defaultRandom(),
// Better Auth's user.id is text — match it, don't recast. One profile per
// user, so the FK itself is unique (this is the 1:1 extension of `user`).
userId: text("user_id")
.notNull()
.unique()
.references(() => user.id, { onDelete: "cascade" }),
displayName: text("display_name"),
// Default model this user's requests fall back to (e.g. gpt-4o-mini).
defaultModel: text("default_model").notNull().default("gpt-4o-mini"),
// Soft cap the metering layer checks token_usage against per calendar month.
monthlyTokenBudget: bigint("monthly_token_budget", { mode: "number" })
.notNull()
.default(0),
createdAt: timestamp("created_at", { withTimezone: true })
.notNull()
.defaultNow(),
},
(t) => [index("idx_profile_model").on(t.defaultModel)],
);
/** Append-only token meter: one row per upstream LLM call. Roll up by
* user + window for budget enforcement and cost reporting. */
export const tokenUsage = pgTable(
"token_usage",
{
id: uuid("id").primaryKey().defaultRandom(),
userId: text("user_id")
.notNull()
.references(() => user.id, { onDelete: "cascade" }),
// Which upstream model was billed (provider model id, opaque to us).
model: text("model").notNull(),
promptTokens: integer("prompt_tokens").notNull().default(0),
completionTokens: integer("completion_tokens").notNull().default(0),
// ponytail: store cost in micro-cents as an integer — no float money, and
// fine-grained enough for sub-cent per-token pricing without a numeric type.
costMicrocents: bigint("cost_microcents", { mode: "number" })
.notNull()
.default(0),
createdAt: timestamp("created_at", { withTimezone: true })
.notNull()
.defaultNow(),
},
(t) => [
// Drives the "tokens used this month" rollup + budget check.
index("idx_usage_user_time").on(t.userId, t.createdAt),
index("idx_usage_model").on(t.model),
],
);
/** Append-only prompt/completion history — the auditable record of every
* exchange (prompt in, completion out, model, token split, outcome). */
export const promptLogs = pgTable(
"prompt_logs",
{
id: uuid("id").primaryKey().defaultRandom(),
userId: text("user_id")
.notNull()
.references(() => user.id, { onDelete: "cascade" }),
model: text("model").notNull(),
prompt: text("prompt").notNull(),
// Null while a streamed completion is still in flight.
completion: text("completion"),
promptTokens: integer("prompt_tokens").notNull().default(0),
completionTokens: integer("completion_tokens").notNull().default(0),
latencyMs: integer("latency_ms"),
status: text("status").$type<CallStatus>().notNull().default("ok"),
// ponytail: opaque per-call metadata (tool calls, finish_reason, etc.) —
// jsonb bag beats a column-per-provider-field churn.
metadata: jsonb("metadata"),
createdAt: timestamp("created_at", { withTimezone: true })
.notNull()
.defaultNow(),
},
(t) => [
// Drives the per-user history feed (most-recent-first).
index("idx_log_user_time").on(t.userId, t.createdAt),
check(
"prompt_logs_status_check",
sql`${t.status} in ('ok','error','filtered')`,
),
],
);
export const userProfilesRelations = relations(userProfiles, ({ one }) => ({
user: one(user, {
fields: [userProfiles.userId],
references: [user.id],
}),
}));
export const tokenUsageRelations = relations(tokenUsage, ({ one }) => ({
user: one(user, { fields: [tokenUsage.userId], references: [user.id] }),
}));
export const promptLogsRelations = relations(promptLogs, ({ one }) => ({
user: one(user, { fields: [promptLogs.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.
- user_profiles.userId carries a UNIQUE constraint — it is the 1:1 extension of Better Auth's user row; the FK itself is the identity, so no separate join table is needed.
- token_usage is append-only and stores cost as costMicrocents (bigint integer): no float money, fine-grained enough for sub-cent per-token pricing without a numeric type.
Related stacks
- Same stack, built for SaaS
- 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, 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