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

- 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. … Perhaps "Email API for Developers, with React components" would resolve the issue. ... It's likely to be brittle and also very slow - slow enough to almost cause an incident when we tried to use it in production because emails were taking _seconds_ to render. Rapzid on June 14, 2023 ... At scale, those calls are actually handled by a message queue (like Redis). If you let the front-end code handle it, you would likely get throttled by the transactional email service provider. That does sound like something better dealt with on the backend at sufficient scale. The Resend API rate limit appears to be 10/sec. … Another thing, thinking of living the future. ... - Poor observability: Postmark (and every other service I've used) provides events.[2] - Designed for marketers only: Postmark is clearly designed for developers, as are several other services. I am rooting for you! ... BUT their JS library has been a shitshow for years now. Like, it works. But the readme links to outdated documentation and 404s. And in the library documentation you can get into an infinite loop of “click here for more info” taking you to back to the page you’re on. It’s still usable. I can just find the page I need with a bit of googling, and actually I stopped using the JS library and just interact with their API directly with HTTP these days. But it’s definitely a sign that they’re not paying attention to that side of the business and developer experience anymore. ... We also have a big problem with automated tools like mimecast or Office365 because customers don't receive emails that were blocked by some rule or heuristic or other but they just contact us because they can't see what their receiving system has done. Even when we show them the logs. … Other problem is to do with IP ranges of the sending servers. Using SES probably mitigates some of that (I assume most providers whitelist SES) but if you ever wanted to move to your own hosts, without a /16 subnet, you can easily get blacklisted (again for unknown reasons) and without enough servers to move to, your deliverability suffers. … Reliably sending email is an insanely hard, you can never guarantee delivery with email anyway. If the 'React' email template editor is the novelty in Resend, I'd suggest them using something like SES to actually send the email. Don't try this yourself, until you verified your product-market-fit and have the scale to invest (heavily) in your own delivery network. … Deliverability is the #1 problem all developers actually face with this imo. We have perpetual issues with extremely high importance, but extremely low volume transactional email from admin panels alerting various (usually non technical) people to things. For example; an important extremely high value custom order has been requested and requires senior signoff in a platform. As far as I can tell nothing really suits this, it's too low volume (<1k emails a month - maybe even a few emails a month) for it to work well with dedicated IPs and shared IPs constantly get spam blocked on the major MSPs.