Operate Your Project
Domains
Configure the base URLs for your authentication services, email delivery, admin portal, and hosted UI.
Banata Auth uses domains to control the base URLs for your authentication services, email delivery, admin portal, and hosted AuthKit UI. You manage all of your domains from the dashboard — no manual environment variable editing required.
Default Domains
Every project ships with four default domains. These are created automatically the first time you visit the Domains page in your dashboard.
| Domain | Default Value | Purpose |
|---|---|---|
banata.dev | Sender address for authentication emails and Admin Portal invitations | |
| Admin Portal | setup.banata.dev | Base URL for your Admin Portal |
| Authentication API | auth.banata.dev | Base URL for authentication requests |
| AuthKit | auth-ui.banata.dev | Base URL for your hosted authentication UI |
Default domains cannot be deleted, but you can edit their values at any time.
Important: Update your domain values to match your production URLs before you deploy. The defaults point to local or staging URLs.
Editing Domains in the Dashboard
- Open your project in the dashboard and navigate to Domains in the sidebar.
- Click the pencil icon next to any domain to edit its value inline.
- Press Enter to save your change or Escape to cancel.
Your updated domain value takes effect immediately within Banata Auth's configuration. If you are pointing to a new custom domain, you will also need to set up DNS and SSL — see Custom Domains below.
Adding Custom Domains
In addition to the four defaults, you can create custom domains for any additional services your project needs.
- On the Domains page, click Add domain.
- Enter a title, description, and domain value.
- Save the new domain.
To remove a custom domain later, click the trash icon next to it. Default domains cannot be deleted.
Custom Domains
When you change a domain value to your own domain (for example, switching from auth.banata.dev to auth.mycompany.com), you need to configure DNS and SSL so traffic reaches your Banata Auth deployment.
DNS Setup
Create a CNAME record with your DNS provider that points your custom domain to your Banata Auth service host.
auth.mycompany.com CNAME your-banata-deployment.vercel.appDNS propagation can take up to 48 hours. During this window, you may need both the old and new domains to remain accessible.
SSL Certificates
All production domains must serve traffic over HTTPS. If you deploy to Vercel, SSL certificates are provisioned automatically for custom domains. For other hosting providers, make sure you provision and install a valid SSL certificate for each custom domain.
Security
- Admin-only access — Only users with an admin role can view or modify domain configuration.
- Default domains are protected — The four built-in domains cannot be deleted, only edited.
- HTTPS required — In production, every domain value should resolve to an HTTPS endpoint.
Troubleshooting
"Authentication required" — You must be signed in as an admin to manage domains. Verify that your session is active and your user has an admin role.
"Domain value not taking effect" — Updating a domain value in the dashboard does not automatically configure DNS or SSL. Make sure you have created the correct DNS records and that the domain resolves to your deployment.
"Default domains missing" — Navigate to the Domains page in your dashboard. The four defaults are seeded automatically on first visit.
Next Steps
- Redirects — Configure redirect URIs for your authentication flows.
- Environment Variables — Set the environment variables your project needs.
- Deploying to Production — Walk through a full production deployment.