Launch HN: Resend (YC W23) – Email API for developers using React

Hi HN! I'm Zeno, founder of Resend (https://resend.com https://resend.com). 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… - 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 <table> layouts thanks to our open source project (https://react.email https://react.email). - 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. - 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. - 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.