Framework integrations
Mount Radon's auth routes into your framework in one line. Ten integrations — Next.js, Express, Fastify, Hono, and six more in Pro.
An integration is the thin layer that exposes Radon's auth flows over HTTP inside
your framework. You mount one handler on a catch-all route and it serves
every endpoint (/email-code/send, /magic-link/verify, /logout,
/session, …). Each also ships a way to read the current user and guard your
own routes.
The universal pattern
Every integration works the same way:
Mount the handler on a catch-all route under a base path (e.g. /api/auth).
Your frontend calls those routes (or the user's browser navigates to them, for
links and OAuth). A successful sign-in sets an HttpOnly radon_session cookie.
Guard your own routes with the integration's requireAuth / getUser helper,
which reads that cookie and gives you the user.
Free integrations
Next.js
App Router catch-all handler + server helpers + middleware.
Express
Router middleware + requireAuth guard.
Fastify
Plugin + preHandler guard.
Hono
Wildcard handler + middleware. Runs on the edge.
Pro integrations
NestJS
Controller handler + CanActivate guard.
Koa
Middleware + requireAuth.
SvelteKit
+server.ts handler + getUser.
Nuxt
Nitro/h3 event handler + getUser.
Remix
loader/action handler + getUser.
Astro
Endpoint handler + getUser.
Same routes everywhere
No matter which integration you mount, the HTTP surface is identical — the routes in each auth method guide work the same on all ten. Switching frameworks never changes your frontend.
Phone / SMS OTP
Passwordless sign-in with a one-time code over SMS. The same flow as email codes, delivered by Twilio (or any SMS sender). A Radon Pro feature.
Next.js
Mount Radon in a Next.js App Router app — one catch-all route, plus helpers to read the user in route handlers, server components, and middleware.