IoT telemetry 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).
- IoT telemetry — user-owned devices, append-only sensor readings, threshold alert rules, and fired alert instances.
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*"],
};IoT telemetry schema: devices, readings, alert rules & alerts
- Devices — user-owned device registry with a unique device_key and an online/offline status CHECK
- Sensor readings (time-series) — append-only rows of metric + numeric value per device, indexed for time-range rollups
- Alert rules & alerts — per-device threshold rules (gt/lt/gte/lte comparator CHECK) and the alert instances they fire, with firing/resolved lifecycle
import { relations, sql } from "drizzle-orm";
import {
check,
index,
numeric,
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 const devices = pgTable(
"devices",
{
id: uuid("id").primaryKey().defaultRandom(),
ownerId: text("owner_id").notNull().references(() => user.id, { onDelete: "cascade" }),
name: text("name").notNull(),
deviceKey: text("device_key").notNull().unique(),
status: text("status").notNull().default("offline"),
createdAt: timestamp("created_at", { withTimezone: true }).notNull().defaultNow(),
},
(t) => [
index("idx_device_owner").on(t.ownerId),
check("devices_status_check", sql`${t.status} in ('online','offline')`),
],
);
// Append-only time-series; roll up by device + window.
export const sensorReadings = pgTable(
"sensor_readings",
{
id: uuid("id").primaryKey().defaultRandom(),
deviceId: uuid("device_id").notNull().references(() => devices.id, { onDelete: "cascade" }),
metric: text("metric").notNull(),
value: numeric("value").notNull(),
recordedAt: timestamp("recorded_at", { withTimezone: true }).notNull(),
},
(t) => [index("idx_reading_device_time").on(t.deviceId, t.recordedAt)],
);
export const alertRules = pgTable(
"alert_rules",
{
id: uuid("id").primaryKey().defaultRandom(),
deviceId: uuid("device_id").notNull().references(() => devices.id, { onDelete: "cascade" }),
metric: text("metric").notNull(),
comparator: text("comparator").notNull(),
threshold: numeric("threshold").notNull(),
createdAt: timestamp("created_at", { withTimezone: true }).notNull().defaultNow(),
},
(t) => [check("alert_rules_comparator_check", sql`${t.comparator} in ('gt','lt','gte','lte')`)],
);
export const alerts = pgTable(
"alerts",
{
id: uuid("id").primaryKey().defaultRandom(),
ruleId: uuid("rule_id").notNull().references(() => alertRules.id, { onDelete: "cascade" }),
deviceId: uuid("device_id").notNull().references(() => devices.id, { onDelete: "cascade" }),
status: text("status").notNull().default("firing"),
triggeredAt: timestamp("triggered_at", { withTimezone: true }).notNull().defaultNow(),
resolvedAt: timestamp("resolved_at", { withTimezone: true }),
},
(t) => [
index("idx_alert_device").on(t.deviceId),
check("alerts_status_check", sql`${t.status} in ('firing','resolved')`),
],
);
export const devicesRelations = relations(devices, ({ one, many }) => ({
owner: one(user, { fields: [devices.ownerId], references: [user.id] }),
readings: many(sensorReadings),
rules: many(alertRules),
}));
export const sensorReadingsRelations = relations(sensorReadings, ({ one }) => ({
device: one(devices, { fields: [sensorReadings.deviceId], references: [devices.id] }),
}));
export const alertRulesRelations = relations(alertRules, ({ one, many }) => ({
device: one(devices, { fields: [alertRules.deviceId], references: [devices.id] }),
alerts: many(alerts),
}));
export const alertsRelations = relations(alerts, ({ one }) => ({
rule: one(alertRules, { fields: [alerts.ruleId], references: [alertRules.id] }),
device: one(devices, { fields: [alerts.deviceId], references: [devices.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.
- devices.device_key carries a unique constraint — it is the physical device's identity token and must be generated once at provisioning time, never regenerated.
- sensor_readings is append-only (no update path, composite index on device_id + recorded_at) — roll up by device + time window for dashboards rather than mutating any running aggregate.
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 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