Open-source email delivery platform pairing a Next.js dashboard with Amazon SES to send transactional and marketing messages without per-contact fees.
useSend pairs a Next.js and Tailwind control panel with Amazon Simple Email Service (SES) to dispatch transactional messages and audience newsletters from self-hosted infrastructure. The TypeScript platform delivers email through a REST API or an SMTP relay while storing subscriber lists in PostgreSQL without per-contact charges. By delegating raw delivery to AWS, the system keeps email expenses tied strictly to outbound message count rather than audience size.
Resend offers polished developer ergonomics, clean API conventions, and fully managed infrastructure, but monthly subscription tiers and message overages climb quickly as delivery volume grows. Proprietary services also penalize companies with expanding contact databases, charging storage premiums even for inactive subscribers. For startups and digital agencies handling multiple client domains, those recurring platform fees compound rapidly.
useSend mirrors that developer workflow—combining REST endpoints, delivery analytics, and a visual template editor—while routing outbound traffic through your own Amazon SES credentials. Because Amazon SES charges ten cents per thousand emails, sending one hundred thousand messages costs ten dollars rather than the hundred-dollar tiers standard across hosted platforms. The tradeoff is operational responsibility: Resend manages IP pool warming and infrastructure reliability automatically, whereas useSend requires you to maintain container uptime, manage Redis queues, and monitor AWS sending quotas.
Is useSend free for commercial use? Yes, useSend is open source and free for commercial applications, with operational expenses limited to server hosting and Amazon SES delivery charges.
useSend vs Resend — which should a team pick? Choose Resend for managed IP warming and zero server maintenance; pick useSend to eliminate volume markups and own your email data.
Can useSend run without Amazon SES? No, useSend currently requires Amazon SES for outbound delivery, meaning an active AWS account with verified sending identities is mandatory.
useSend is a practical choice for teams sending high-volume transactional or broadcast email who want to cut monthly SaaS bills by using raw AWS infrastructure. It is not suitable for organizations needing turnkey inbound email routing or managed IP warming without in-house operations. Active development through September 2026 and an AGPL-3.0 license that guarantees full code auditability make it an effective self-hosted alternative to proprietary developer mail services.
Free IDE for Java, Kotlin, Go, TypeScript and Python. Built on IntelliJ Community, fully open source, 300+ plugins.
Show that useSend is listed as an open-source alternative. Paste into your README: