If you’re integrating your Vercel preview deployments with Neon, you’re already getting an isolated Postgres branch per preview. We just extended the same automation to authentication. When you use Neon through the Vercel integration and enable Auth, every Vercel deployment gets its own isolated authentication endpoint, with URLs injected automatically and trusted domains already configured […]

Neon

Neon's Vercel integration now automatically provisions isolated authentication endpoints for every preview deployment. When you enable Auth through the integration, each preview gets its own database branch and matching auth instance with URLs and trusted domains configured automatically. Authentication data lives in the database and branches alongside schema and data, enabling safe testing of auth changes in preview environments without manual configuration. The feature works with both Vercel-managed and Neon-managed integrations.

Auth That Just Works in Vercel Previews

A quick refresher on the Neon <> Vercel integrations

What’s new: Neon Auth now follows your Vercel deployments