By Jake Mcdonald, founder of ShipEmber · November 10, 2026 · About a 9-minute read · Checked against the Next.js, Auth.js, and Stripe docs
I'm Jake Mcdonald. Once a SaaS has a Free plan and a Pro plan, every new feature comes with the same quiet question: who is allowed to use this, and where do I check? The first answer most of us reach for is to hide the button for Free users and maybe add a redirect in middleware. It looks done. It isn't.
This post is the gating setup I use in Next.js App Router apps: one server-only helper that reads the plan from the database, a requirePro() wrapper for pages and Server Actions, a 401/403 check for route handlers, and a short list of places where a check looks like protection but isn't. Everything here was checked against the Next.js authentication guide , the Auth.js protecting resources docs , and Stripe's fulfillment docs on November 10, 2026.
The rule: every entry point checks for itself
A Next.js app has more doors than it looks like.…