Resend vs Wraps

Resend is a managed email API built on top of AWS SES. Beautiful DX, fast onboarding, everything runs on their infrastructure.

Wraps deploys email infrastructure directly to your AWS account. Same modern DX, but you own the infrastructure and pay AWS directly.

Both platforms use AWS SES to send email. The difference is whose account it runs in -- and who pays the bill.

TL;DR

Sound familiar?

Real quotes from Resend users on Trustpilot, G2, Hacker News, and developer blogs.

With Wraps, your infrastructure runs in your AWS account. No third party can suspend your sending, and your logs live in your DynamoDB with configurable retention.

The architectural difference

Resend and Wraps both use AWS SES to deliver email. The difference is where the infrastructure lives and who controls it.

In January 2024, Resend suffered a security incident where a database API key was exposed in client-side code, exposing customer email metadata, domain info, and contacts. With Wraps, your sending infrastructure and email events are isolated in your own AWS account.

Pricing at real volumes

Resend bundles sending cost into their platform fee with $0.90/1K overage. Wraps charges a platform fee separately -- you pay AWS directly at $0.10/1K emails.

Feature comparison

When to choose Resend

Resend is a good product. Here's when it makes more sense.

When to choose Wraps

Wraps is built for teams that want modern DX with infrastructure ownership.

Switching from Resend

Both Resend and Wraps use SES underneath. React Email templates work unchanged. The migration is an SDK swap and DNS update.

import { Resend } from "resend";const resend = new Resend("re_123456");await resend.emails.send({  from: "hello@example.com",  to: "user@example.com",  subject: "Welcome",  react: <WelcomeEmail />,});

import { Wraps } from "@wraps.dev/email";const wraps = new Wraps();await wraps.emails.send({  from: "hello@example.com",  to: "user@example.com",  subject: "Welcome",  react: <WelcomeEmail />,});

Also Compare