Neon•7d ago

neon auth in development branch

Hello, I'm trying to develop an application and I'd like to have a developing environment where I can test the user flows without affecting the production branch. The problem that I see is that the integration with neon auth always creates users in the production branch. Is there a work around? Thank you
Also if I go to the branch and using the api i try to create a neon auth it tells me that I already got one, but If I go to delete it it tells me that I dont have one

instant-harlequin•12/9/25, 3:26 PM

Hey!
Unfortunately no, StackAuth does not do user branching, and there isn't a workaround I'm aware of.
For your second point, I'm guessing you're seeing this because you can only remove Auth from the production branch, and can't add Auth to any other branch

verbal-lime•12/10/25, 11:23 PM

@Domingo Today we launched the new implementation of Neon Auth with branching support. It is build on top of better-auth and not stack auth.

https://neon.com/blog/neon-auth-branchable-identity-in-your-database

If you already have stack auth enabled for your project, you can continue will continue to work fine, but at project level.
From today, when you enable it for new projects, you will get it with better-auth and branching support. - https://neon.com/docs/auth/overview

Neon

Meet the New Neon Auth: Branchable Identity in Your Database - Neon

We rebuilt Neon Auth on a new foundation. It now stores identity directly in your Neon database, making auth fully branch-compatible.

Neon

Neon Auth - Neon Docs

Neon Auth is a managed authentication service that stores users, sessions, and auth configuration directly in your Neon database. When you branch your database, your entire auth state branches with it...