Migrate from Resend to a European transactional stack — when the developer experience that brought you in starts conflicting with sovereignty, dedicated IP economics, or VC-pace pricing changes

Yes, completely. React Email is an open-source library that renders JSX to HTML at build time — it has no runtime tie to Resend's infrastructure. The render() call that produces HTML for Resend's API produces the same HTML we accept via our REST API or SMTP relay. Teams that chose Resend specifically for the React Email experience keep the entire authoring stack: JSX components, the local preview server, the email-specific CSS reset, table-based layout helpers, dark-mode media queries, the lot.

Our migration tooling walks your existing template directory, renders each template against the same React Email runtime, and validates the output against our delivery pipeline before any production traffic flows. The one piece you do not get post-migration is Resend's dashboard preview — the in-product visualization of rendered templates. Teams typically replace that with the React Email local development server, which is what they were using during template authoring anyway. Net experience after week 1 is the same JSX authoring loop with a different delivery target underneath.

We are not in the business of predicting other providers' pricing decisions. What we will say is that the October 2024 doubling of the 200K Scale tier from $80 to $160 — without a public announcement, without grandfathering for new signups, without product changes that justified the increase — is the kind of event that VC-backed infrastructure companies do at predictable points in their growth curve. Resend has raised institutional capital; the growth math eventually meets the burn math; that pressure tends to surface as repricing rather than feature cuts. We are owner-operated since 2003 and our EUR pricing has been stable for the duration of the company. That is the difference; readers can draw their own conclusions about which model fits their operational planning horizon.

For many use cases, yes. Resend's DPF certification (announced March 13, 2025) makes lawful EU-to-US transfer straightforward at the contractual level; the Ireland sending region addresses send-time data residency and reduces API latency from European clients. For most SaaS using transactional email, that combination is adequate. The friction starts when an enterprise customer with a German DPO or French CNIL-aware procurement function asks where the account data, the dashboard analytics, the bounce logs, and the historical delivery records are physically located. Resend's architecture, per their own documentation, keeps that data US-hosted. That is a different question from "where does the email send from."

The legal-policy backdrop matters too. In December 2025, NOYB issued a public advisory that the DPF is under serious legal pressure, citing the SCOTUS Trump v. Slaughter case challenging FTC independence — the FTC being a key pillar of the enforcement architecture the European Commission required when approving the DPF. A SCOTUS ruling is expected in June or July 2026. If the framework is materially weakened, every DPF-certified US provider — including Resend, Mailchimp, SendGrid, and many others — falls back to SCC-with-TIA compliance, which is the same difficult demonstration we covered on the Mandrill page. We are EU-incorporated in Sweden; the question does not arise on our side.

Honestly, usually no. At sub-500/day volumes, Resend's shared IP pool placement is good, the Pro plan is well-priced, the React Email authoring experience is excellent, and the dedicated IP question does not arise. The teams in this volume range that we do help typically have one of three drivers: a sovereignty requirement that the DPF certification does not satisfy (regulated industries, public sector, German DPO concerns), a procurement requirement that mandates non-US providers, or an architectural preference for named-operator engagement over self-service signup. None of those are universal at this volume.

If your driver is just "we want better deliverability," we are honest that at sub-500/day shared pool placement is hard to beat with dedicated IPs — the warmup math does not favor low-volume dedicated IPs, and a well-managed shared pool (which Resend ships) gives you the engagement-aggregated reputation of many senders rather than the thinly-warmed reputation of one. Where dedicated IPs win is at the volume where you generate enough engagement to sustain your own reputation, which is typically 5K-10K daily minimum.

Both transfer cleanly. Resend's inbound webhook delivers parsed JSON with the email's headers, body, attachments base64-encoded; our inbound webhook does the same with a slightly different field structure. The MX record swap happens during week 1 alongside the SPF and DKIM updates. Webhook signature verification needs to be updated to use our HMAC scheme instead of Resend's, which is a 10-line code change typically.

For event webhooks (delivered, bounce, complaint, opened, clicked), the same pattern applies — same event taxonomy, slightly different JSON field names. The migration script we run produces a webhook-handler diff showing exactly what fields need to be remapped; most teams complete this work in week 1 alongside the DNS changes.

We ship a lightweight campaign builder that handles audience segmentation, broadcast sending, and basic A/B testing, but it is deliberately less full-featured than Resend Marketing Email. For teams whose marketing email program is substantial — multi-step automations, behavioral triggers, deep segmentation, integration with CRM systems — we typically recommend pairing us with a dedicated marketing platform (Customer.io, Brevo, Klaviyo) rather than asking us to be a full marketing tool. The transactional layer moves to us; the marketing layer keeps its current home or moves to a specialist.

Audiences and Broadcasts exports cleanly: Resend's contact API supports CSV export with custom fields, and the broadcast history is exportable through their API. The migration of marketing email runs on its own track in weeks 4-6 typically, after the transactional cutover is stable. Most teams find the split simpler than the combined Resend setup once they have lived with it for a few months.

Month-to-month on standard plans with 30-day notice for cancellation. Annual contracts get a 10-15% discount, but the annual is always optional. During the migration project, the first 60 days are structured so you can route back to Resend at any time. We do not lock anyone in during validation — the abstraction wrapper your team introduces in week 1 makes provider switching a one-line config change.