Model monthly email volume, senior developer setup hours, dedicated IP fees, and maintenance drag to discover the exact month where switching to AWS SES pays off.
At your volume, saving engineering hours is more valuable than SES commodity rates.
| Expense Dimension | Resend Stack | AWS SES Stack |
|---|---|---|
| Monthly Email Invocations | $60.00 | $15.00 |
| Dedicated IP Addon | $0.00 | $0.00 |
| Monthly DevOps Maintenance | $0.00 (Managed) | $180.00 |
| Year 1 Total TCO (incl. setup) | $720.00 | $3,300.00 |
| Year 2 Total Cumulative TCO | $1,440.00 | $5,640.00 |
At 150k emails/month, Resend's $60.00/mo fee is completely justified. Spending $960 in engineering hours plus ongoing maintenance to manage AWS IAM, DKIM, and SNS bounce queues would require 21 months just to break even.
import { SESClient, SendEmailCommand } from "@aws-sdk/client-ses";
import { render } from "@react-email/render";
import { WelcomeEmail } from "./emails/welcome";
const ses = new SESClient({ region: "us-east-1" });
export async function sendWelcome(to: string, name: string) {
const html = await render(WelcomeEmail({ name }));
const cmd = new SendEmailCommand({
Destination: { ToAddresses: [to] },
Message: {
Body: { Html: { Charset: "UTF-8", Data: html } },
Subject: { Charset: "UTF-8", Data: "Welcome to CheckAPICost!" }
},
Source: "[email protected]"
});
return await ses.send(cmd);
}
Resend charges $0.40 per 1,000 emails on overages vs AWS SES at $0.10 per 1,000 — a 4x multiplier on volume. However, Resend eliminates: AWS console navigation, IAM role generation, Route 53 TXT record debugging, SNS bounce notifications, and email suppression database management. For early-stage startups, saving 12 engineering hours ($1,440) outweighs email bill differences for years.
Every new AWS account is confined to the SES Sandbox. You cannot email real customers until AWS human support approves your production access ticket. If your application sends marketing emails with vague double opt-in descriptions, AWS will deny your request, delaying your product launch by days.
To prevent domain blacklisting on AWS SES, you must wire SES event destinations to Amazon SNS, connect SNS to an AWS Lambda function, parse hard bounces (code 5.1.1) and spam complaints, and write them into a DynamoDB suppression table. If your code sends an email to a previously bounced address, AWS penalizes your account standing.
When an engineering team crosses 500,000 emails/month, the optimal pattern is Split-Routing: keep Resend or Postmark for mission-critical authentication (OTP codes, password reset links) where sub-second delivery is paramount, and route heavy bulk product announcements and newsletters through AWS SES to capture wholesale unit pricing.
Use this verified Terraform blueprint to automate your SES domain verification, Route 53 CNAME DKIM tokens, and SNS topic in under 5 minutes without touching the AWS Web Console:
# 1. Verify custom sending domain in AWS SES
resource "aws_ses_domain_identity" "main" {
domain = "checkapicost.com"
}
# 2. Generate Easy-DKIM 2048-bit tokens
resource "aws_ses_domain_dkim" "main" {
domain = aws_ses_domain_identity.main.domain
}
# 3. Create Route 53 DNS records for DKIM authentication
resource "aws_route53_record" "ses_dkim" {
count = 3
zone_id = var.route53_zone_id
name = "${aws_ses_domain_dkim.main.dkim_tokens[count.index]}._domainkey.checkapicost.com"
type = "CNAME"
ttl = 300
records = ["${aws_ses_domain_dkim.main.dkim_tokens[count.index]}.dkim.amazonses.com"]
}
# 4. Create SNS Topic for Bounce and Complaint Webhooks
resource "aws_sns_topic" "ses_bounces" {
name = "ses-bounce-notifications"
}
resource "aws_ses_identity_notification_topic" "bounce" {
topic_arn = aws_sns_topic.ses_bounces.arn
notification_type = "Bounce"
identity = aws_ses_domain_identity.main.domain
include_original_headers = true
}
| Feature / Requirement | Resend Managed Platform | AWS SES Infrastructure | Engineering Impact |
|---|---|---|---|
| Domain Verification | 1-click automated DNS checks | Route 53 CNAME + TXT records | +1.5 hours setup on SES |
| Sandbox Removal | Instant production sending | Requires AWS support ticket | 12-36h launch delay risk |
| Bounce & Complaint Handling | Automated webhooks + suppression lists | Manual SNS → Lambda → DB | +4 hours engineering time |
| Template Authoring | Native React Email components | Requires build step or raw HTML | Neutral with @react-email |
| Cost at 1,000,000 Emails | $400.00 / mo | $100.00 / mo | SES saves $3,600 / year |