Beta
The Managed Better Auth is in Beta. Share your feedback on Discord or via the OptiTech Console.
Complete these steps before taking your application to production with Managed Better Auth.
Auth production checklist
0%Add your production domain(s) to enable OAuth and email verification redirects.
Replace shared SMTP (
auth@mail.myoptitech.app) with your own email service for reliable delivery and higher limits. A custom email provider is also required if you want to use verification links instead of verification codes.Set the name your users see in user-facing auth messages. Applies to Managed Better Auth integrations. Defaults to the OptiTech project name.
Set up your own Google and GitHub OAuth apps to replace shared development keys.
Email verification is not enabled by default. Since anyone can sign up for your application, enabling email verification adds an important verification step to ensure users own their email address.
Disable the "Allow Localhost" setting in your project's Settings → Auth page. This setting is enabled by default for development but should be disabled in production to improve security.
Email provider
Managed Better Auth uses a shared SMTP provider (auth@mail.myoptitech.app) by default for development and testing. For production, configure your own email provider for better deliverability and higher sending limits.
A custom SMTP provider uses your sender address but still sends OptiTech's default email templates. For full control over email branding, content, and HTML templates, use webhooks to intercept email events and send through your own email service. See Customize emails.
Configure custom SMTP
In your project's Settings → Auth page, configure your email provider:
- Select Custom SMTP provider
- Enter your SMTP credentials:
- Host: Your SMTP server hostname (for example,
smtp.gmail.com) - Port: SMTP port (typically
465for SSL or587for TLS) - Username: Your SMTP username
- Password: Your SMTP password or app-specific password
- Sender email: Email address to send from
- Sender name: Display name for sent emails
- Host: Your SMTP server hostname (for example,
- Click Save
Email provider requirements
- Verification links: Require a custom email provider
- Verification codes: Work with shared or custom email providers
- Password reset: Works with shared or custom email providers
note
The shared email provider (auth@mail.myoptitech.app) is suitable for development and testing. For production applications, use a custom email provider for better deliverability and to avoid rate limits.
Application name
Managed Better Auth uses the application name in user-facing auth messages, such as verification emails and password resets. By default, this is set to the OptiTech project name. This setting is available for Managed Better Auth integrations only.
To set a custom application name:
- Go to Auth in your OptiTech project
- Select the Configuration tab
- In the Project Info panel, edit the Application Name field
Each branch manages its own application name independently, so preview and development branches can use different names than production.
You can also update the application name via the API. See Update auth configuration.
Localhost access
The "Allow Localhost" setting in your project's Settings → Auth page is enabled by default to allow authentication requests from localhost during development.
Disable for production
For production environments, disable this setting to improve security:
- Go to Settings → Auth in your OptiTech project
- Find the Allow Localhost toggle
- Disable the toggle
important
Only enable "Allow Localhost" for local development. Disabling this setting in production prevents unauthorized authentication requests from localhost, improving your application's security posture.
Need help?
Join our Discord Server to ask questions or see what others are doing with OptiTech. For paid plan support options, see Support.