Email notifications
Self-hosted operators configuring SMTP and admins troubleshooting missing notifications.
Configure SMTP for operational mail, understand what events generate messages, and troubleshoot delivery without blocking core product workflows.
Email is best-effort: installs, deploys, and billing continue even if SMTP is misconfigured. Use logs to diagnose missing mail rather than assuming silent failure in the app.
4 sections4 key takeaways3 related guides
Quick highlights
Email is best-effort: installs, deploys, and billing continue even if SMTP is misconfigured. Use logs to diagnose missing mail rather than assuming silent failure in the app.
Self-hosted operators configure SMTP on the API service; tnc-sh.cloud users receive platform mail without managing these variables directly.
What you will learn
- Categories span user, subscription, project, and marketing mail β not all are enabled in every deployment.
- Recipients resolve from GitHub profile email when available, with noreply fallback.
- SMTP settings are environment variables on the API service.
- Send failures are logged; they must not block project creation, deploys, or billing webhooks.
Sections in this guide