React Email

United States · react.email · 10 vendors

Resilience scores

Technology vendors

Services catalogue

2 services in catalogue across 2 categories; runs on 10 sub-vendors.

Insights

Last updated 2026-08-13 · revision 1

10 direct vendors, 211 subvendors

Direct vendors by controlling owner country (sample)

Subvendors by controlling owner country (sample)

Migration Readiness: 7/10

Assessed by AI based on technology stack characteristics (cloud-native vs legacy, containerization, microservices), regulatory environment, data residency requirements, financial stability, and vendor lock-in risks. The score ranges from 0-10, where higher scores indicate better readiness for technology migration.

React Email demonstrates high migration readiness, primarily due to its modern and cloud-native friendly tech stack. The use of React, Next.js, TypeScript, Node.js, and reliance on platforms like Vercel and AWS SES (via Resend) indicates a highly adaptable and modular architecture. The products themselves, being open-source and built with component libraries, suggest a design that is not heavily tied to proprietary systems. The small number of critical vendors (Vercel, GitHub, AWS SES) simplifies the scope of vendor relationship management and contract complexities during a potential migration, compared to a company with a vast and diverse vendor ecosystem. While there is some inherent platform lock-in with Vercel for deployment and hosting, the underlying technologies are widely adopted and portable, making a transition to another cloud provider or self-hosting feasible, albeit requiring effort. Key challenges and unknowns for migration readiness include the lack of data on financial stability, which could impact the funding available for a migration project. Additionally, the absence of specified regulatory environment or data residency requirements means potential hidden complexities could emerge if these factors become critical during a migration. However, the overall technological foundation positions React Email well for future migrations.

Compliance

6 in-scope frameworks identified; showing 3.

GDPR (source) — Assessment Required

React Email is an open-source MIT-licensed developer library maintained by Resend (a US-based company). As a software library/toolkit, React Email itself does not collect, store, or process personal data — it renders email HTML on the developer's side. However, Resend (the parent company behind react.email) operates a commercial email delivery platform that serves EU/EEA customers and processes personal data (e.g., recipient email addresses, developer account data) on their behalf. The react.email website itself may collect visitor analytics data from EU/EEA users. GDPR is therefore applicable to Resend's operations underpinning React Email. Risk is Medium rather than High because the core product is a stateless open-source library, but the associated commercial platform and website do process EU personal data. No public DPO appointment or GDPR audit evidence was found for react.email specifically.

Evidence: https://react.email, https://react.email/docs, https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32016R0679

CAN-SPAM Act — Assessment Required

The CAN-SPAM Act (15 U.S.C. § 7701) regulates commercial email senders in the United States. React Email is a tool that helps developers build email templates — it is not itself a commercial email sender. However, Resend (the parent company) operates an email delivery platform that sends commercial emails on behalf of customers. Resend as an email service provider (ESP) has obligations to enforce CAN-SPAM compliance among its customers and may have direct obligations as a sender. Risk is Low for React Email the library, but Medium for Resend's email delivery platform.

Evidence: https://react.email/docs/integrations/resend, https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business

SOC 2 (source) — Assessment Required

React Email itself is an open-source library and does not operate as a cloud service. However, react.email offers a cloud-based Editor product ('Add an email editor to your product') and is backed by Resend, which is a cloud email delivery platform. If Resend processes customer data through cloud infrastructure, SOC2 Type II certification would be expected by enterprise customers. No SOC2 report was found for React Email or Resend in the sources reviewed. The risk is Medium because the absence of SOC2 certification could be a barrier to enterprise adoption and signals potential gaps in security controls documentation, though the core product is an open-source library with no data custody.

Evidence: https://react.email, https://react.email/docs/editor/overview, https://www.aicpa-cima.com/resources/landing/system-and-organization-controls-soc-suite-of-services

Financials

Three-year financials

Financial Resilience Score: 6/10

React Email itself has no independent financials—it is an open-source project fully sponsored by Resend, a private, VC-backed US email API company. Resend has never publicly disclosed revenue, EBIT, or equity, so any resilience assessment relies on qualitative signals and funding history rather than audited financial performance. Resend's resilience is underpinned by a tier-1 investor base (Andreessen Horowitz lead, Y Combinator, SV Angel, plus prominent operator-angels) and a fresh US$18M Series A closed in December 2024, providing multi-year runway for a ~48-person globally distributed team. The company has strong product-led distribution via React Email (300k weekly npm downloads, ~19.6k GitHub stars), 200,000+ signed-up developers, and blue-chip customer logos including Warner Bros., Decathlon, Vercel, Raycast, Gumroad, MrBeast, and Replit. However, the company is early-stage, likely still burning capital ahead of revenue, and operates in a highly competitive market against SendGrid (Twilio), Mailgun, Postmark, Amazon SES, and Mailchimp Transactional, with structural pricing pressure from AWS SES. Concentration on the developer/startup segment exposes Resend to venture-funding cyclicality, and React Email specifically is a cost center dependent entirely on Resend's willingness to fund it. Overall, resilience is moderate—strong for an early-stage startup, but lacking the disclosed financial metrics that would support a higher score.

Key strengths: Tier-1 investor base (a16z, Y Combinator, SV Angel, operator-angels from Pixar, Twitter, Mailchimp, Vercel, Figma, GitHub, Stripe), Fresh US$18M Series A closed December 2024 providing multi-year runway, Strong product-led growth via React Email OSS (300k weekly npm downloads, ~19.6k GitHub stars), 200,000+ registered developers within ~18 months of public launch, Blue-chip customer logos (Warner Bros., Decathlon, Vercel, Raycast, Gumroad, MrBeast, Replit), Usage-based recurring revenue model with typically high gross margins and sticky retention

Risk factors: No disclosed revenue, EBIT, or profitability—likely still burning capital, Highly competitive email API market (SendGrid, Mailgun, Postmark, AWS SES, Mailchimp Transactional), Structural pricing pressure from Amazon SES, Concentration on developer/startup segment exposes company to venture-funding cyclicality, Key-person risk tied to founder Zeno Rocha's technical brand; small 48-person team, React Email is a pure cost center with no direct revenue, Deliverability and regulatory risk (CAN-SPAM, GDPR, DMARC, anti-spam list operators)

Workforce by country

Signed-in users can see whether their own company is exposed to this vendor's disruption, plus the full sub-vendor list and country breakdowns, every in-scope compliance framework plus gaps and next steps, and alerts when any of it changes.

View the full interactive report