Real Alpha
Try Pro free

Latent Space · 3 min · Nov 10, 2026

React Email gave Resend a path from templates to sending

Zeno Rocha · Co-founder & CEO, Resend

Zeno Rocha treated React Email as an open-source entry point, writing setup guides for rival sending services.

In this episode

Full analysis
  1. 7:01Email delivery depends on pacing and reputationPro pick 5 min
  2. 38:02An MCP should cover the whole product6 min
  3. 58:26Markdown pages can correct AI pricing answers7 min
  4. 32:23SES's low price can hide the surrounding infrastructure cost4 min
  5. 13:24Shared tracking domains expose senders to a neighbor's abuse3 min
  6. 17:19Support replies became documentation before they reached customers2 min
  7. 19:55Domain Connect turns DNS setup into an OAuth-style flow3 min
  8. 23:51React Email gave Resend a path from templates to sending3 min
Up next · My First MillionYour net-worth peak is a date, not a dollar amount3:43
“if people are, like, building the, like, the email template using React, like, now they'll need a platform to send it.”
Zeno Rochaat 24:37 · Latent Space
24:37

Takeaways

  1. Open source brought developers into an email-template workflow.
  2. Docs covered SendGrid, MailChimp and Mailgun.
  3. Resend positioned sending as the next problem to solve.

About this segment

Zeno Rocha treated React Email as an open-source entry point, writing setup guides for rival sending services. Once developers had templates, Resend could be the next step to deliver them.

Zeno Rocha

Zeno Rocha is cofounder and CEO of Resend.

Co-founded Resend, an email platform for developers, and launched React Email, open-source components for building email templates.

  • Shawn Wang (swyx), Host · Co-founder, AI Engineer

    Wrote “The Rise of the AI Engineer” and founded Smol AI, maker of AI News.

  • Alessio Fanelli, Host · Founder, Kernel Labs

    Partner at Decibel, backing technical founders who build developer tools.

From “Designing for Agents — Zeno Rocha, Resend”, Nov 10, 2026. Watch the full episode

Transcript

From the transcript Latent Space publishes with the episode.

  1. 23:55

    You had-- You made React Email the year before. Yeah. So you did dip your toes in open work. Yeah. Um, and then came the company. Yeah, React Email is our Next.js, right? So we wanted like an open source channel for top of the funnel, and I remember doing some things very intentionally. If you go to the docs, for example, you'll find there are docs about How do you set this up with SendGrid and MailChimp and Mailgun? I wrote every single one of those docs over there. Mm.

  2. 24:26

    Um, and I just wanted like, okay, this is for everyone, and we're trying to redefine how this is. And it was a strategy of like, we're gonna give, give, give, and then we ask. Uh, and if people are- Is, uh, Gary Vee? Yeah. And, and if, if people are, like, building the, like, the email template using React, like, now they'll need a platform to send it. Where do they do that? Here's Resend. So it was a, like, a storytelling kind of way of approaching the market.

  3. 24:56

    Like, we're gonna fix the first part of the, the journey, which is building the template, and then once you have the template, now that that problem is fixed, you need a platform to send it. Here's the platform. But, uh, did you have the idea for Resend when you started React Email, or was it a side project that- Yeah... then became a company? We started Resend, and as we were building Resend, I was, like, doing a lot of user research, and people were saying like, "Oh, the pain of writing the template. I get the f- the Figma file from my designer.

  4. 25:24

    It, it sucks. Like, it's HTML tables and, and everything." They would cut the images, right? Yeah. Oh my gosh. And [laughs] Uh-huh. It's, it's in there. Because there's nothing. And then there's, like, a special syntax of HTML that only works on email. Yeah. Right? It, it's a mess. Or, or CSS. Yeah. It, it's all inline CSS. Yeah. Inline CSS. Well, yeah. That's right. And then, like, for Outlook, you have, like, some special comments, and then you gotta... It's such a mess. It's like a- Yeah... it's a mess. Um. And so, like, I-- to me, the reason that React- Mm-hmm...

  5. 25:53

    works is that it is- Mm-hmm... basically a compiler. Yes. It's like, it's like, well, somebody writes this once, and then as long as you fit the API, it's going to work everywhere. Yeah. And you can import your tokens from Tailwind. Now you have a, a type definition with TypeScript. So no more, "Hey," empty comma, you know, like, on your emails. Yeah. Like, you can actually have, like, a string validation or whatever you want. Yeah. I think one of the initial people that pushed back on React Email was like- Mm-hmm... "Well, you're not actually using React.

  6. 26:19

    There's no state." Yeah. And, like, React [laughs] is supposed to be, uh, views as a function of state. Yeah. Uh, but so it's, it's mostly JSX is templating? Yes. Or is there actually, like, animations? Is there interactivity? No. Expanding, like accordions? No. Nothing, nothing like that. Okay. There's-- So you cannot ship JavaScript on an email. So then what you do is, yeah, w- we basically use- But CSS-...