React Email templating integration: type-safe, component-driven email templates without leaving the codebase.
Less mature than Mailchimp or Kit for marketing-email editorial workflows (drip campaigns, A/B testing, segmentation UI).
- ✓You're building transactional email into a SaaS or indie app and want best-in-class API ergonomics.
- ✓You're sending cron-triggered operator notifications and the free tier covers your volume.
- ✓You're comfortable templating email in React Email rather than a WYSIWYG editor.
- ✗You need a full marketing-email platform with editorial UI, drip campaigns, and audience segmentation. Pick Kit, Mailchimp, or Brevo.
- ✗Your team's email workflow is editor-led rather than developer-led. Resend's console UX is API-first by design.
Overview
Resend is the email API Vibetoolstack uses for every operator-side notification: the 2x daily digest of new content, instant live-notifications when a doc promotes, and 🔄 UPDATED notifications when a cluster-update doc ships. Three separate Node scripts (send-daily-digest.mjs, send-live-notifications.mjs, send-test-email.mjs) all call Resend's API directly.
Resend's positioning is "Stripe for email": a small, opinionated API surface with clean SDK ergonomics, React Email integration for templating, and modern primitives (broadcasts, audiences, webhooks). It's the email API for builders who don't want SendGrid's 2010-era console.
Pros & Cons
Pros
• Cleanest email-API ergonomics in the category as of 2026. The send() call is one line in any modern SDK
• React Email templating integration is genuinely useful. Type-safe templates with component reuse
• Free tier (3,000 emails/month) is enough for any indie operator side project
• Domain verification flow is smooth; SPF/DKIM/DMARC records work out of the box
• Modern primitives (broadcasts, audiences, webhooks) without SendGrid's decade-old console UX
Cons
• Less mature than Mailchimp / Kit / Brevo for editorial marketing-email workflows
• Limited template editor in dashboard. You're mostly working in code or React Email
• Smaller community + integration ecosystem than SendGrid / Mailgun (improving rapidly)
• Pricing climbs at higher-volume tiers; budget if you're scaling past 50k/month
My Experience
How VTS uses Resend
Three production scripts, each invoked from GitHub Actions on cron. send-daily-digest.mjs runs at 05:30 and 17:30 Berlin time and emails a digest of newly-published docs to the operator address. send-live-notifications.mjs fires from publish-scheduled-updates.mjs cron whenever a doc promotes from draft to live. send-test-email.mjs is a one-shot smoke test for new template work.
All three call resend.emails.send() with simple HTML strings (no React Email templating yet on VTS, though it's on the roadmap). Total volume: maybe 60 emails per month, well within the free tier (3,000/month).
What we use beyond send
Domain verification via DNS records was a one-time setup, completed in roughly 20 minutes. SPF, DKIM, DMARC all pass with default Resend records. Deliverability has been clean (no spam-folder reports from the operator inbox over 8 months).
What broke (so you don't have to)
The default From address in Resend's dashboard is the verified domain; if you want to send from a subdomain (e.g., notifications@your-site.com), you need to add the subdomain as a separate verified domain. Not hard, but the docs could surface this earlier.
Rate limits on the free tier are generous but the 100 emails/day Free-tier ceiling can hit you fast if you broadcast to a list. Pro tier ($20/month) lifts to 50,000/month, which is the right tier for any operator running newsletters or marketing emails.
What we'd do again
Default to Resend over SendGrid or Mailgun for any new project in 2026. The API ergonomics, SDK quality, and pricing curve all favor Resend at indie-operator scale. If you outgrow Resend's top tiers, you outgrow the tool category and into enterprise email infrastructure (SparkPost, Postmark Enterprise).
Integrate React Email for templating once you have more than 2 email templates. Inline HTML strings are fine for 1-2 templates; the maintenance cost climbs fast beyond that.
Best Use Cases
Transactional email for SaaS and indie apps
Resend's primary use case. Account verification, password reset, payment receipts, weekly digests. The API surface (one send() call with from/to/subject/html) is the minimum to ship correctly. Deliverability is strong if you complete domain verification.
Operator-side notifications
What Vibetoolstack uses Resend for. Cron-triggered emails that report state changes (new doc published, draft promoted, daily digest). Low volume, predictable schedule, free tier covers everything.
Newsletters and broadcasts
Resend's Audiences feature handles list management and Broadcasts handle send-to-list. Less mature than Mailchimp's editorial UI but the API integration is cleaner. Strong fit if you're building newsletter functionality into your own product rather than buying an email-marketing platform.
Marketing email at scale
Less mature than Mailchimp, ConvertKit (Kit), or Brevo for traditional marketing-email workflows. If you need drip campaigns, segmentation, A/B testing, and editorial calendars, pick a dedicated email-marketing platform. Resend is better at the API and infrastructure layer than the marketing-workflow layer.