Beta
The Neon Auth with Better Auth is in Beta. Share your feedback on Discord or via the Neon Console.
Add your application domains to Neon Auth's allowlist to enable OAuth and email verification redirects in production.
Why domains are required
Neon Auth only redirects to domains in your allowlist. This prevents phishing attacks and unauthorized redirects by ensuring users are only sent to your legitimate application URLs.
Without adding your production domain, OAuth sign-in and verification links will fail when users try to access your application.
Add a domain
- Go to Console → Auth → Configuration → Domains
- Enter your domain with protocol:
https://myapp.com - Click Add domain
Repeat for each domain where your app runs.
note
Include the protocol (https://) and omit trailing slashes. For example: https://myapp.com not https://myapp.com/
Localhost is pre-configured
Development domains are automatically allowed, so you don't need to add them:
http://localhost:3000http://localhost:5173- Any
localhostport
Production domains
Add all domains where users access your application:
https://myapp.comhttps://www.myapp.com(if you support www subdomain)https://app.myapp.com(if using a subdomain)
important
Add each subdomain explicitly. Wildcards like *.myapp.com are not supported.
Common issues
Redirect blocked after OAuth sign-in:
- Verify the domain is in your allowlist
- Ensure you included
https://(nothttp://for production) - Check spelling matches exactly (including www vs non-www)
Verification link doesn't redirect:
- Verification links use the same domain allowlist
- Add the domain where users should land after clicking the verification link
Next steps
- Production checklist - Complete setup for launch
Need help?
Join our Discord Server to ask questions or see what others are doing with Neon. For paid plan support options, see Support.








