Email automation, unbundled from delivery
FlowingMail is built by Sadonis. We ship tools that make event-driven infrastructure easier for small teams - and FlowingMail applies that philosophy to email.
Why FlowingMail exists
Every email automation platform we looked at bundled three things into one product: the workflow engine, the sending infrastructure, and the pricing model. That bundling is why lifecycle emails cost more at 50,000 contacts than an entire cloud bill - you are paying for deliverability you could buy wholesale from Resend, SendGrid, Mailgun, or Amazon SES for a fraction of the price. We built FlowingMail to unbundle that stack: you bring the provider, we bring the automation.
What we believe
- Email is code. Flows should trigger from your event stream, templates should version like source files, and every endpoint should be addressable through a REST API with a published OpenAPI spec.
- Pricing should scale with value, not list size. Flat plans, zero markup on sending, and a free tier that covers a typical seed-stage app for months.
- You own your data, your domains, and your sender reputation. Exports are one click. Self-hostable workers are available for regulated workloads.
- Small surface area is a feature. We would rather ship one good workflow canvas than twenty half-built channel integrations.
Who builds FlowingMail
FlowingMail is made by Sadonis, a small team that ships developer infrastructure. Our stack is opinionated - .NET on the backend, Next.js on the frontend, PostgreSQL for data, RabbitMQ for events - and we bring the same opinions to FlowingMail: composable, typed, event-first.
Questions, feedback, or want to chat about email infrastructure? [email protected]