Beta
The Neon Auth with Better Auth is in Beta. Share your feedback on Discord or via the Neon Console.
Neon Auth is in active development. This page shows what's currently supported and what we're working on next.
General availability
Neon Auth is targeting general availability this quarter. We're actively working on additional plugins and features to bring Neon Auth out of beta.
Frameworks
Supported
| Framework | Status | Quick start |
|---|---|---|
| Next.js | ✅ Supported | Get started |
| Vite + React | ✅ Supported | Get started |
| React + React Router | ✅ Supported | Get started |
| React + TanStack Router | ✅ Supported | Get started |
The React quick start steps through a Vite + React app. If you use React Router for URLs and layouts, use the same Neon Auth URL, @neondatabase/neon-js client, and SDK calls from that guide, then integrate them into your router and route components. For file-based routing with TanStack, use the TanStack Router quick start instead.
On the roadmap
| Framework | Status |
|---|---|
| Standalone frontend + backend | 🔜 Coming soon |
| Other frameworks | Based on demand |
Standalone architectures
Architectures where frontend and backend are separate deployments (for example, Create-React-App with a separate Node/Express backend) are not yet supported. Neon Auth uses HTTP-only cookies for secure session management, and these cookies cannot be securely shared between frontend and backend applications on different domains. We're actively working on this.
Better Auth plugins
Neon Auth is built on Better Auth. Not all Better Auth plugins are currently supported.
Supported
| Plugin | Status |
|---|---|
| Email & password | ✅ Supported |
| Social OAuth (Google, GitHub, Vercel) | ✅ Supported |
| Email OTP | ✅ Supported |
| Admin | ✅ Supported |
| Organization | ⚠️ Partial (JWT token claims under development) |
| JWT | ✅ Supported |
| Magic Link | ✅ Supported |
| Open API | ✅ Supported |
| Phone Number | ✅ Supported |
See Set up OAuth for Neon-specific OAuth configuration (including Vercel). Email flows such as verification and password reset are covered in Email verification, Password reset, and User management.
Platform (Console, API, webhooks)
These capabilities are documented in Neon Auth guides but are not Better Auth plugins you enable through the SDK.
| Capability | Status | Documentation |
|---|---|---|
| Trusted domains (redirect allowlist) | Supported | Configure trusted domains |
| Webhooks (auth events) | Supported | Webhooks |
| Manage Auth via Neon API | Supported | Manage Auth in the Neon API |
| Manage Auth via Neon MCP (AI editor) | Supported | Set up with your AI editor |
Branch-aware auth (separate auth state per Neon branch) is supported; see Branching authentication and Authentication flow.
On the roadmap
| Plugin | Status |
|---|---|
| MFA support | 🔜 Coming soon |
| Admin plugin customization | 🔜 Coming soon |
| Other plugins | Based on demand |
SDK and UI references
| Surface | Documentation |
|---|---|
TypeScript client SDK (neon-js) | Neon TypeScript SDK |
| Next.js server SDK | Next.js Server SDK |
| Pre-built UI components | UI components |
Migration guides
Production and checklist
For launch readiness, see the production checklist.
Let us know
We prioritize based on demand. If you need a specific framework or plugin, let us know through our Discord or GitHub Discussions.
Need help?
Join our Discord Server to ask questions or see what others are doing with Neon. For paid plan support options, see Support.