Better Auth that branches,
managed by Neon
Test real login flows. When you deploy a Neon branch, auth branches too, so your previews fully reflect production.
- Foundation
Built on Better Auth
The Better Auth foundation your team (and agent) already knows, plus branching.
Better Auth
Familiar APIs
Open source
- Managed
Managed by Neon
Neon operates the auth layer for you, so you can ship authentication without provisioning, maintaining, or scaling separate infrastructure.
No infrastructure
Built-in auth
- SDKs
Client and server SDKs
Use client and server SDKs to add sign-in, sessions, OAuth, and account flows without wiring everything together yourself.
Client + server
Sign-in & sessions
Users, sessions, and auth live in Postgres. Keep identity data and auth configuration right in your backend, not on an external service.
Inspect auth with SQL. The neon_auth schema gives teams a concrete place to inspect auth state and connect identity to RLS-based access rules.
Keep identity with your data. Keep users and sessions close to application data without syncing identity from another provider.
Build previews you can actually log into
Sign up, log in, reset a password, complete OAuth. When you're done testing, delete the branch.
Deploy one Neon branch per preview
Sign up
Login
OAuth
Password reset
RLS
Ask your coding agent to deploy and configure Managed Better Auth. Deploy a preview branch and start testing.
Enable
Turn on Managed Better Auth on the Neon branch, from the prompt, the CLI, or the Console.
Configure
Add Google OAuth, email and password, trusted domains on that branch.
Wire your app
The agent installs the SDK, env vars, and sign-in routes for your framework.
Preview
A child branch gets its own users, sessions, and auth URL. Test real logins, then delete it.
Your questions,
answered.
Managed authentication built on Better Auth, as part of the Neon backend. Users, sessions, and OAuth config live in your database, in the
neon_authschema, so you can query them with SQL and pair them with RLS. There is no auth server to run. Configure it in the Console, then use the client or server SDK in your app.
Your auth branches with everything else. Create a branch and your whole backend forks with it — database, storage, auth, and a gateway endpoint of its own.
Built for agents and
the developers behind them.
Every service is designed with the same API and operational model, whether it's used by a developer or called directly by an AI agent. Build once, then let both humans and agents use the same platform without additional integration work.
Branchable
Spin up isolated environments to test model changes safely, without touching production. Merge changes only when they're ready.
Serverless
Usage-based infrastructure that scales automatically with your traffic, so you only pay for what you use and nothing while idle.
Agent-ready
Provision and operate every service through APIs that AI agents can call directly, using the same interfaces as developers.
Trusted at scale. Neon has been part of the Databricks Platform since May 2025.
20M+
Databases started daily - built for scale and reliability.
3M+
Developers building on Neon worldwide
Neon's serverless philosophy is aligned with our vision: no infrastructure to manage, no servers to provision, no database cluster to maintain.
Talk to us.
Fill out a short form and we’ll get back to you within a few business days.
