An EU-hosted transactional email API, evaluating Resend?
Same request shapes, a migration path that's mostly automated, and EU data residency, price stability, and long log retention as the default, not an enterprise add-on.
EU-hosted by default
API, database, logs, and backups run in the EU. A signed DPA ships on every plan, including free, no sales call required.
24-month price lock
Your tier price is fixed at signup. Any change after that gets 6 months' notice and a grandfathering option, published, not buried in a contract.
90-day log retention
Debug a bounce from three months ago, not three weeks ago. Free tier gets 7 days, Pro gets 90, Scale is configurable up to 365.
What actually moves, and what doesn't
How similar is the API?+
Deliberately close: from, to, subject, html, text, cc, bcc, attachments, and batch sending all map the same way. A codemod (npx @envello/migrate) rewrites imports and client instantiation automatically for the common cases.
Does the migration handle everything automatically?+
The codemod handles imports and client setup. Application logic, webhook endpoint URLs, and any code inspecting a provider-specific response shape still need a manual look. See the full migration guide on this blog for the exact steps.
What about React Email support?+
Render your component to an HTML string with @react-email/render and pass it as the html field. That's the whole integration, no adapter needed.
Full walkthrough: Migrating from Resend to Envello