Resend - Email for developers

Hi PH! I'm Zeno, founder of Resend. We're building a modern email sending platform focused on providing the best developer experience. Why? When you look at all the biggest competitors like Sendgrid, Mailgun, Postmark, and SparkPost, you'll notice that they were all founded around 2009/2010, and they all have been acquired by now. Because of that, it's common to see them only prioritizing enterprise requirements and optimizing for sales-led growth. Nobody is building an exceptional developer experience. Nobody is trying to innovate. There isn't a single developer-first email platform in the market today. We want to change that. Email sending is the kind of thing that you should integrate and forget, but instead, you have… 1. 🛠️ Templates that are hard to build: Typically, you can only send emails using HTML or plain text. Although we support both, we're introducing a new way of developing and sending your emails. With Resend, you can code your email using React instead of outdated layouts thanks to our open source project (https://react.email). 2. 🐢 Slow performance: Current solutions only offer a single region for email sending, even when all your end users are located in another part of the world. We allow you to choose what region your emails should be sent from (US, Europe, or LATAM), which minimizes latency and improves time-to-inbox. 3. 👀 Poor observability: Most tools keep you in the dark without knowing what really happened after you sent an email. Resend exposes all the events associated with your email via webhooks. 4. 🙋 Designed for marketers only: Existing solutions are too generic and built exclusively for product marketers and product managers. We're building a platform with a clean REST API and SDKs for Node.js, Python, Ruby, Elixir, Go, and Java. We also have examples of how to send emails using Vercel Edge Functions, Cloudflare Workers, Supabase Edge Functions, and other serverless solutions. What's our backstory? When I was a CPO at Liferay, I faced the problem of sending emails at scale. We had enterprise customers complaining about deliverability, and I've been frustrated with existing services ever since. More recently, as a VP of Developer Experience at WorkOS, I once again had to deal with emails landing in the spam folder. After looking at all the different solutions out there, I've been obsessed with the idea of solving this problem once and for all. We need to stop developing emails like it's 2010 and rethink how email can be done in 2023 and beyond. We believe that email development needs a revamp. A renovation. Modernized for the way we build apps today. That's why we're building Resend. What issues have you had with email sending? I would love to hear your ideas, experiences, and feedback on any and all of the above.

I appreciate how much care Resend is putting into the details and entire user experience for developers. Gives me early Stripe vibes. What's been the biggest surprise or learning so far, @zenorocha?

Impressive! Would be happy to try!

developers finally have a user-friendly email sending platform. it was about time! we recently implemented React Email at Documenso. will definitely share Resend with the team. keep up your great work, @zenorocha and team! 👏👏

Resend is a no brainer tool for any business. The team have built an amazing tool for developers, it just took couple of mins for me to setup & send first email to my customers.

Great product! We use Resend to power our emails in Zeabur and it's convinient and great! Congrats on the launch! Looking forward to a further collaboration :)

We use and LOVE Resend. Absolutely phenomenal product worth trying

I haven't met any developer who likes setting up transactional email on an app. This is a super cool product, well done!

That's nice! I hope you will add marketing feature soon (with sequences). I will try for my next project 🚀

Congrats on your launch and on raising the money for your next steps., Zeno. Your product sounds great. What I didn't understand on first sight is how you design emails inside Resend. What's the way you recommend?