I've been working on Mailofly , and email infrastructure platform for developers and wanted to share it with the r/saasbuild community.
As the idea cam out of fact that sending an email is trivial but email infrastructure itself is rather complex.
Like:
- SMTP setup
- SPF, DKIM, DMARC
- Deliverability
- Bounce management
- Tracking delivery
- Webhooks
- Email logs
- Retries
- Scaling
- Email workflows Management
Therefore, I developed Mailofly in order to abstract the email infrastructure pieces while providing a simple experience for the developer.
What Mailofly provides ?
- SMTP: Use Standard SMTP in your existing application without refactoring your entire email system.
- Email API: Sending transactional emails using an API.
- CLI: Sending and managing emails directly in terminal.
- Automations : Creating email workflows and automating email processes
- Logs & Webhooks: Tracking email actions and integrating delivery events into your application.
That's a basic idea behind making the email infrastructure an "afterthought," rather than one that needs continuous development and maintenance.
I am particularly curious to get feedback from other developers, especially those who have made any kind of SaaS product or API's:
- What do you hate most about your infrastructure ?
- Is it deliverability, DNS settings, troubleshooting bad email deliveries, pricing, the API interface, or something else?
Feedback and criticism would be greatly appreciated.
Mailofly: https://mailofly.com
Feel free to ask me any technical questions regarding how I built it.
Source: r/saasbuild · by /u/garib06