Bring-Your-Own (BYO) Email Providers
Deliver magic links, invitations, and password resets from your own custom domain using Resend, Postmark, Amazon SES, or custom SMTP.
Why custom email providers matter
Transactional authentication emails (magic link login codes, password resets, organization invitations) are among the most critical touchpoints in your user journey. Using a shared generic email provider causes two major problems:
- Deliverability and Spam Risk: Shared sender IPs can be degraded by unrelated senders, causing login links to land in spam folders.
- Brand Trust and Phishing Protection: Users expect emails to arrive from
[email protected], not a third-party platform address.
HVT allows each project to configure its own isolated email provider with dedicated domain reputation, custom sender headers, and automated error handling.
Supported providers
HVT provides native first-class integrations with the leading email infrastructure providers:
| Provider Value | Platform | Required Fields |
|---|---|---|
resend | Resend API | api_key (re_...), from_email |
postmark | Postmark Server API | api_key (Server API token), from_email |
ses | Amazon SES | aws_region, aws_access_key_id, aws_secret_access_key, from_email |
smtp | Custom SMTP Server | smtp_host, smtp_port, smtp_username, smtp_password, from_email |
system_default | HVT Platform Mailer | None (default fallback) |
Zero plaintext leakage: Encryption at rest
All provider secrets (api_key, smtp_password, aws_secret_access_key) are encrypted at rest using AES-128-CBC via Django MultiFernet cryptography.
has_api_key, has_smtp_password, and has_aws_secret_access_key.Inspect current email settings
Fetch the current email configuration for a specific project:
Configuration recipes by provider
Update your project's email provider settings using a PATCH request:
1. Resend
2. Postmark
3. Amazon SES
4. Custom SMTP
Testing email delivery
Before activating your email configuration in production, use the test endpoint to send a verification message. This validates DNS SPF/DKIM alignment, API credentials, and SMTP handshakes without triggering real user events: