Email and newsletters decision
Resend
A capable engineer can build a usable transactional email sender and basic dashboard in about a week, but reproducing Resend's managed deliverability features (dedicated IP warmup/autoscaling, multi-region pristine IP pools) and enterprise compliance is expensive and operationally heavy, so keeping the paid service is reasonable for production-grade deliverability.
Visit website↗$20/mo
$240/yr
Read off the official pricing page.
$50one-off30 h to build
$25/mo3 h/mo upkeep
On cash alone, building overtakes the subscription at 2 seats.
Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Resend alternatives, with the arithmetic →
What a replacement has to do
- Accept an API request to send an email → render template → hand off to SMTP/SES → persist delivery log → expose webhook events and a small UI/log viewer.
What it still won’t have
- Managed dedicated IPs with automated warmup and autoscaling
- Built-in deliverability monitoring, blocklist tracking and BIMI/VMC guidance
- SOC 2-backed enterprise compliance and advanced security features out of the box
- Multi-region delivery infrastructure and pristine shared IP pools
- Polished broadcast editor, contact management UI and built-in analytics
What remains hard
- Compliance and regulation
SOC 2 Type II certification
- Infrastructure at scale
Managed dedicated IPs
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 2 seats.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal transactional email service in Node.js (Express) + Postgres deployed to a single Heroku/DigitalOcean droplet, using AWS SES SMTP for delivery. In scope: (1) REST API /v1/send that accepts from/to/subject/template/variables and validates input, (2) template rendering using server-side React/email or a simple HTML templating layer and CSS inlining, (3) SMTP/SES integration with retry/backoff and bounce/complaint parsing, (4) webhook receiver to accept and persist delivery events, (5) Postgres schema for messages and events and a small React admin UI to view logs and retry sends, (6) tests for API, template rendering and webhook handling, and error handling for provider failures. Out of scope: managed dedicated IP provisioning, multi-region routing, SOC 2 compliance, advanced deliverability tooling and a full-featured broadcast editor. Provide automated deployment scripts, basic monitoring (uptime + error alerts), and documentation on domain DNS records (SPF/DKIM) required to run.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 5 cited sources+3
- Price verified on pricing page+3
- 3/3 assessment runs agreed+4
- Hard moats found in the evidence-6
- Evidence score61
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 5
Every page the run actually retrieved.
- official productResend — official product
- official pricingResend Pricing
- official docsResend Docs — Introduction
- open sourceNotifuse/notifuse
- open sourcedittofeed/dittofeed
Integrity checks
What held up, and what did not.
