Booking / scheduling 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).
- Calendar-scoped booking — bookable resources with capacity, time-windowed availability slots, party-size reservations, and per-reservation payment settlement.
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*"],
};Booking & scheduling schema: resources, availability & reservations
- Resources & ownership — bookable things (rooms, seats, staff) owned by a Better Auth user, each carrying an integer capacity cap
- Availability slots & calendar windows — time windows a resource publishes, indexed by (resourceId, startsAt) for calendar range queries
- Reservations & party size — holds and confirmations against a slot, consuming partySize units and walking held → confirmed → cancelled via CHECK
- Booking payments & settlement — one payment record per reservation, storing amountCents as integer and an opaque providerPaymentId for Stripe/etc.
import { relations, sql } from "drizzle-orm";
import {
boolean,
check,
index,
integer,
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 ReservationStatus = "held" | "confirmed" | "cancelled";
export type BookingPaymentStatus = "pending" | "paid" | "refunded";
/** A bookable thing (room, table, seat, staff member). Owned by the user who
* publishes it; capacity caps how many can be reserved against one slot. */
export const resources = pgTable(
"resources",
{
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" }),
name: text("name").notNull(),
capacity: integer("capacity").notNull().default(1),
createdAt: timestamp("created_at", { withTimezone: true })
.notNull()
.defaultNow(),
},
(t) => [index("idx_resource_owner").on(t.ownerId)],
);
/** A time window a resource publishes. isOpen lets the owner close a window
* without deleting it (and its reservations). The resource+startsAt index
* drives the calendar lookup. */
export const availabilitySlots = pgTable(
"availability_slots",
{
id: uuid("id").primaryKey().defaultRandom(),
resourceId: uuid("resource_id")
.notNull()
.references(() => resources.id, { onDelete: "cascade" }),
startsAt: timestamp("starts_at", { withTimezone: true }).notNull(),
endsAt: timestamp("ends_at", { withTimezone: true }).notNull(),
isOpen: boolean("is_open").notNull().default(true),
},
(t) => [
// Drives the "slots for this resource, in time order" calendar query.
index("idx_slot_resource_time").on(t.resourceId, t.startsAt),
],
);
/** A hold/booking against a slot. status walks the lifecycle; partySize is how
* many of the slot's capacity this reservation consumes. */
export const reservations = pgTable(
"reservations",
{
id: uuid("id").primaryKey().defaultRandom(),
slotId: uuid("slot_id")
.notNull()
.references(() => availabilitySlots.id, { onDelete: "cascade" }),
bookedBy: text("booked_by")
.notNull()
.references(() => user.id, { onDelete: "cascade" }),
status: text("status")
.$type<ReservationStatus>()
.notNull()
.default("held"),
partySize: integer("party_size").notNull().default(1),
createdAt: timestamp("created_at", { withTimezone: true })
.notNull()
.defaultNow(),
},
(t) => [
// Drives the "my reservations" lookup.
index("idx_reservation_user").on(t.bookedBy),
check(
"reservations_status_check",
sql`${t.status} in ('held','confirmed','cancelled')`,
),
],
);
/** Payment settling a reservation. amountCents keeps money integer; status
* walks the settlement states. */
export const bookingPayments = pgTable(
"booking_payments",
{
id: uuid("id").primaryKey().defaultRandom(),
reservationId: uuid("reservation_id")
.notNull()
.references(() => reservations.id, { onDelete: "cascade" }),
// Money as integer cents — no float money in the ledger.
amountCents: integer("amount_cents").notNull().default(0),
status: text("status")
.$type<BookingPaymentStatus>()
.notNull()
.default("pending"),
// ponytail: opaque payment-provider id (Stripe/etc.) — no provider FK needed.
providerPaymentId: text("provider_payment_id"),
createdAt: timestamp("created_at", { withTimezone: true })
.notNull()
.defaultNow(),
},
(t) => [
index("idx_payment_reservation").on(t.reservationId),
check(
"booking_payments_status_check",
sql`${t.status} in ('pending','paid','refunded')`,
),
],
);
export const resourcesRelations = relations(resources, ({ one, many }) => ({
owner: one(user, { fields: [resources.ownerId], references: [user.id] }),
slots: many(availabilitySlots),
}));
export const availabilitySlotsRelations = relations(
availabilitySlots,
({ one, many }) => ({
resource: one(resources, {
fields: [availabilitySlots.resourceId],
references: [resources.id],
}),
reservations: many(reservations),
}),
);
export const reservationsRelations = relations(
reservations,
({ one, many }) => ({
slot: one(availabilitySlots, {
fields: [reservations.slotId],
references: [availabilitySlots.id],
}),
bookedByUser: one(user, {
fields: [reservations.bookedBy],
references: [user.id],
}),
payments: many(bookingPayments),
}),
);
export const bookingPaymentsRelations = relations(
bookingPayments,
({ one }) => ({
reservation: one(reservations, {
fields: [bookingPayments.reservationId],
references: [reservations.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.
- Capacity is on the resource, not the slot: a reservation consumes partySize units of the slot's capacity, so multiple parties can share one slot up to its cap.
- availabilitySlots carries an isOpen boolean so an owner can close a window without deleting it (and its child reservations); the cascade is intentionally one-way downward (slot → reservation → payment).
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, 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