Newsletter platform 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).
- Audience-scoped newsletter platform — subscribers with deliverability status, named lists, list membership, campaigns scheduled against a list, and per-subscriber send tracking.
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*"],
};Newsletter schema: subscribers, lists, campaigns & per-subscriber sends
- Subscribers & deliverability status — email addresses collected by an owner, with a status CHECK walking subscribed/unsubscribed/bounced
- Lists & list_subscriptions membership — named audience segments and the join table that places a subscriber on a list at most once
- Campaigns & scheduling — broadcasts targeting a list, with a status CHECK gating draft/scheduled/sent and a nullable scheduledAt timestamp
- Campaign_sends & delivery tracking — one append-only row per (campaign, subscriber) tracking the queued→delivered→opened→bounced lifecycle
import { relations, sql } from "drizzle-orm";
import {
check,
index,
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 SubscriberStatus = "subscribed" | "unsubscribed" | "bounced";
export type CampaignStatus = "draft" | "scheduled" | "sent";
export type CampaignSendStatus =
| "queued"
| "delivered"
| "opened"
| "bounced";
/** An email address on someone's audience. Owned by the user who collected it;
* status walks the deliverability lifecycle. The owner+email unique stops the
* same address landing on one owner's audience twice. */
export const subscribers = pgTable(
"subscribers",
{
id: uuid("id").primaryKey().defaultRandom(),
// Better Auth's user.id is text — match it, don't recast.
ownerId: text("owner_id")
.notNull()
.references(() => user.id, { onDelete: "cascade" }),
email: text("email").notNull(),
status: text("status")
.$type<SubscriberStatus>()
.notNull()
.default("subscribed"),
createdAt: timestamp("created_at", { withTimezone: true })
.notNull()
.defaultNow(),
},
(t) => [
unique("subscribers_owner_email_unique").on(t.ownerId, t.email),
index("idx_subscriber_owner").on(t.ownerId),
check(
"subscribers_status_check",
sql`${t.status} in ('subscribed','unsubscribed','bounced')`,
),
],
);
/** A named segment of an owner's audience (e.g. "Weekly digest"). */
export const lists = pgTable(
"lists",
{
id: uuid("id").primaryKey().defaultRandom(),
ownerId: text("owner_id")
.notNull()
.references(() => user.id, { onDelete: "cascade" }),
name: text("name").notNull(),
createdAt: timestamp("created_at", { withTimezone: true })
.notNull()
.defaultNow(),
},
(t) => [index("idx_list_owner").on(t.ownerId)],
);
/** list <-> subscriber join. The composite unique is the membership identity —
* a subscriber is on a list at most once. */
export const listSubscriptions = pgTable(
"list_subscriptions",
{
id: uuid("id").primaryKey().defaultRandom(),
listId: uuid("list_id")
.notNull()
.references(() => lists.id, { onDelete: "cascade" }),
subscriberId: uuid("subscriber_id")
.notNull()
.references(() => subscribers.id, { onDelete: "cascade" }),
createdAt: timestamp("created_at", { withTimezone: true })
.notNull()
.defaultNow(),
},
(t) => [
unique("list_subscriptions_list_subscriber_unique").on(
t.listId,
t.subscriberId,
),
index("idx_list_subscription_subscriber").on(t.subscriberId),
],
);
/** A broadcast targeting a list. status walks the lifecycle; scheduledAt is the
* send time once status is 'scheduled'. */
export const campaigns = pgTable(
"campaigns",
{
id: uuid("id").primaryKey().defaultRandom(),
listId: uuid("list_id")
.notNull()
.references(() => lists.id, { onDelete: "cascade" }),
subject: text("subject").notNull(),
status: text("status")
.$type<CampaignStatus>()
.notNull()
.default("draft"),
scheduledAt: timestamp("scheduled_at", { withTimezone: true }),
createdAt: timestamp("created_at", { withTimezone: true })
.notNull()
.defaultNow(),
},
(t) => [
index("idx_campaign_list").on(t.listId),
check(
"campaigns_status_check",
sql`${t.status} in ('draft','scheduled','sent')`,
),
],
);
/** One row per (campaign, subscriber) send attempt. status walks delivery; the
* campaign index drives the per-campaign delivery/open rollup. */
export const campaignSends = pgTable(
"campaign_sends",
{
id: uuid("id").primaryKey().defaultRandom(),
campaignId: uuid("campaign_id")
.notNull()
.references(() => campaigns.id, { onDelete: "cascade" }),
subscriberId: uuid("subscriber_id")
.notNull()
.references(() => subscribers.id, { onDelete: "cascade" }),
status: text("status")
.$type<CampaignSendStatus>()
.notNull()
.default("queued"),
sentAt: timestamp("sent_at", { withTimezone: true }),
},
(t) => [
// Drives the "delivery/open stats for this campaign" rollup query.
index("idx_send_campaign").on(t.campaignId),
check(
"campaign_sends_status_check",
sql`${t.status} in ('queued','delivered','opened','bounced')`,
),
],
);
export const subscribersRelations = relations(subscribers, ({ one, many }) => ({
owner: one(user, { fields: [subscribers.ownerId], references: [user.id] }),
listSubscriptions: many(listSubscriptions),
sends: many(campaignSends),
}));
export const listsRelations = relations(lists, ({ one, many }) => ({
owner: one(user, { fields: [lists.ownerId], references: [user.id] }),
listSubscriptions: many(listSubscriptions),
campaigns: many(campaigns),
}));
export const listSubscriptionsRelations = relations(
listSubscriptions,
({ one }) => ({
list: one(lists, {
fields: [listSubscriptions.listId],
references: [lists.id],
}),
subscriber: one(subscribers, {
fields: [listSubscriptions.subscriberId],
references: [subscribers.id],
}),
}),
);
export const campaignsRelations = relations(campaigns, ({ one, many }) => ({
list: one(lists, {
fields: [campaigns.listId],
references: [lists.id],
}),
sends: many(campaignSends),
}));
export const campaignSendsRelations = relations(campaignSends, ({ one }) => ({
campaign: one(campaigns, {
fields: [campaignSends.campaignId],
references: [campaigns.id],
}),
subscriber: one(subscribers, {
fields: [campaignSends.subscriberId],
references: [subscribers.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.
- The (ownerId, email) unique constraint on subscribers prevents the same address appearing twice on one owner's audience — deduplication is enforced at the DB level, not application code.
- campaign_sends is append-only per (campaign, subscriber): each row walks queued → delivered → opened → bounced via a text CHECK, making delivery/open rollups a straight aggregate over the idx_send_campaign index rather than a mutable counter.
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 Forum / community
- 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