Do it yourself

Sure, SES is cheap

Everything you need before your first production email

• Create separate dev, staging and production email environments
• Implement a public email API that handles everyday traffic but scales instantly when your app goes viral
• Deal with email authentication (DKIM, SPF, DMARC, MAIL FROM... because email is weird)
• Add DNS records and wait for everything to verify
• Apply for production access to escape the SES sandbox
• Explain your sending use case to AWS and hope they approve it
• Configure domains and sending identities for every environment
• Build the 50+ boring transactional emails every SaaS eventually ends up needing
• Deal with responsive HTML emails that somehow render differently everywhere
• Build queueing so email failures do not break your app
• Handle retries when providers inevitably fail
• Process bounces and spam complaints
• Build unsubscribe handling and suppression lists
• Stop sending to dead email addresses before your reputation tanks
• Monitor deliverability and sender reputation
• Add rate limiting and abuse protection
• Test across Gmail, Outlook, Apple Mail and mobile
• Keep all of it working

EmailsDone

Or just send the email

Already works. Try it now.

That's it.

50+ transactional templates already included. Password resets, verification, magic links, notifications, billing, exports and more.