Infrastructure
Email relay for self-hosted applications
Based on 8 of 9 factors
Overview
AIThis description was written by a model from public signals. The facts behind it are listed under Evidence.
- Problem
- Self-hosted applications on VPS providers struggle with SMTP port blocking and email delivery limitations. Developers either need to hack together workarounds like Postfix relays or lose access to features like anti-spam filtering that are gated behind paid tiers of email services.
- Solution concept
- A lightweight, self-hosted email gateway that sits between applications and transactional email providers, bypassing SMTP port blocks. It would support multiple providers, include built-in security features (anti-spam, rate limiting, honeypot fields), and work uniformly across different applications with minimal setup.
- Who has it
- Developers and system administrators running self-hosted applications (Ghost, Gitea, Mastodon, Umami, Comentario) on VPS providers like DigitalOcean; creators with static sites using contact forms.
- How they handle it today
- Today, they either configure Postfix relays manually, use free email form services that hit usage limits, or accept reduced functionality. For static sites, they use services like Formspree but encounter rate limits on free tiers and must upgrade to paid plans for anti-spam features.
- Why now
- VPS providers increasingly block default SMTP ports to combat spam and abuse, making this a growing pain for self-hosted deployments. The rise of self-hosted alternatives to SaaS (Ghost, Mastodon, Gitea) has expanded the audience facing this problem.
- How it could charge
- Freemium or open-source with optional commercial support and managed hosting; or value-added services like hosted relay infrastructure, advanced analytics, and premium integrations.