Senlo — Infrastructure for Transactional & Lifecycle Emails
Senlo is an open-source, developer-first email infrastructure designed to handle the entire lifecycle of your product's emails. It provides the tools to build, manage, and deliver transactional and lifecycle emails without being locked into a specific delivery provider.
Why Senlo?
Most email platforms are built for marketing teams, bundling editing, sending, and analytics into closed ecosystems. Senlo is built for developers and product teams who need:
- Full Control: Self-host your email infrastructure and keep your data on your own servers.
- Provider Agnostic: Switch between AWS SES, Resend, Mailgun, or SMTP without changing your code.
- Visual & Code: A powerful drag-and-drop builder for designers, with a clean API for developers.
- Lifecycle Management: Manage everything from password resets to complex automated onboarding sequences.
Key Capabilities
- Visual Drag-and-Drop Editor: Build beautiful, responsive templates without writing HTML/MJML.
- API-First Approach: Trigger emails, manage contacts, and track events via a robust REST API.
- Dynamic Personalization: Use merge tags and conditional logic to tailor content for every recipient.
- Template Versioning: Track changes and roll back to previous versions of your email designs.
- Multi-Project Isolation: Manage multiple products or environments (Staging/Production) from a single instance.
Use Cases
- Transactional Emails: Reliable delivery for password resets, receipts, and verification codes.
- Product Lifecycle: Automated onboarding series, feature announcements, and re-engagement campaigns.
- Embedded Editor: Integrate the visual builder directly into your own SaaS product.
Deployment
The easiest way to deploy Senlo is using Docker Compose. Check our VPS Deployment Guide for step-by-step instructions.
Status
Senlo is currently in active development (MVP stage). We are stabilizing the API and adding core features. Contributions and feedback are welcome!
Check out our Roadmap for planned features and upcoming improvements.
Author
Igor Filippov
- GitHub: @IgorFilippov3