Middleware runs on the Edge runtime -- pg and argon2 don't

Next.js middleware runs on the Edge runtime by default, which can't load the pg driver or native argon2 -- auth logic has to live in node-runtime route handlers instead.

This is one of the things Multi-Tenant Auth & RBAC Core already handles. Sign-in, organisations, invites and roles — with one customer's data provably unable to reach another's.

Buy for $1492 of 3 clean-room builds passed · full refund if it fails on your machine

Is this you?

Next.js middleware executes on the Edge runtime, a restricted JavaScript environment that doesn't support Node-native modules or TCP sockets. Code that tries to check a session by querying Postgres directly inside middleware.ts -- a natural place to put "run this check before every request" -- fails at build or runtime, because the pg driver and native argon2 bindings simply cannot load there.

Why this one is easy to get wrong

Middleware is explicitly designed and documented as the place to run logic before a request reaches a route -- "gate every request through one auth check" reads like exactly what middleware is for, and the Edge-runtime restriction is a platform-level constraint that isn't visible from the application code being written, only from trying to run it.

What you get instead

Core decision 19 states there is no middleware.ts in this pack at all -- every auth check runs inside node-runtime route handlers via a shared requireSession() helper, which is free to use pg and native argon2 because the node runtime supports both. The tradeoff (no request-level gating before routing) is accepted explicitly rather than worked around with an Edge-compatible reimplementation of session lookup.

Source: ARCHITECTURE.md core decision 19 — checkable in the pack you receive

How you actually use this

You don’t install a library or wire up an SDK. Your own coding agent builds the code in your project, and you keep it — no runtime dependency on us.

Step 1
Download and unzip
You get a folder: the docs that tell an agent what to build, a starting skeleton, and the test suite that decides when it's done.
Step 2
Open it in Claude Code or Cursor
Point your coding agent at the folder. Nothing to install, no account with us, no API key.
Step 3
Paste one prompt
The pack contains the exact prompt. Paste it as your first message and leave it alone — it works through the build itself, choosing a cheaper or stronger model per task.
Step 4
Run ./verify.sh
One command. It prints a pass or fail for every check. Green means the build is done — the same script we ran to produce the receipt on this page.

Typical build: about 12 minutes of your agent working, mostly unattended. Then you integrate the working module into your app the way you would any code you’d written yourself.

Why you can believe this

2 of 3 runs passed

We ran this pack from an empty folder 3 times and published exactly what happened — every check, the model, the token cost, the wall time. Not a testimonial, and not our opinion: the same verify.sh you run yourself. Read the full receipt →

Buy for $149 14-day refund if verify.sh fails →