# Werkmail vs Resend

Reviewed August 2026. Resend is a **developer send API** with excellent DX (React Email, modern webhooks). Werkmail is an **EU compliance and deliverability product** that also exposes HTTP send.

## At a glance

| | Resend | Werkmail |
| --- | --- | --- |
| Primary job | Developer transactional API | EU operator platform with the same gate on GUI and API |
| DX | React Email, framework examples | HTTP JSON, curl, OpenAPI |
| Default region story | US-rooted | Frankfurt / **eu-central-1** |
| Marketing | Not the identity | `broadcast` with DOI and Impressum |
| Consent / DSAR | You build or buy elsewhere | Ledger, export, erase |
| Webhooks | Modern, well-documented | Signed webhooks + inbound send hooks |
| Campaigns | Not the focus | Block editor, A/B, linear journeys |

## They win

- **Developer experience.** React Email, clean APIs, and a dashboard aimed at engineers shipping SaaS notifications.
- **Speed to first send** for a Next.js or Node app that only needs transactional mail.
- **Ecosystem.** Community templates and framework examples move faster than a vertical EU product.
- **Focus.** They do not pretend to be a practice-management or DSGVO suite.

## Werkmail wins

- **EU operations by default.** Frankfurt / **eu-central-1**. Resend is US-rooted; EU-only residency is not the product identity.
- **Productized compliance.** DOI, consent ledger, Impressum before broadcast, List-Unsubscribe on every message, DSAR export/erase.
- **Stream purity.** Transactional and marketing routes never share reputation.
- **Practice kinds** and compliance checks for typical clinic mail — not just `template_id`.
- **Operator cockpit.** Warm-up, bounce-reason rollup, content-score history, reputation pause — not only API logs.

## Honest gaps on our side

- We do not ship a React Email runtime or a comparable “drop this component in” story.
- If your stack is a US SaaS and legal is “we’ll add a DPA later,” Resend is often the faster integrate.
- Campaigns and journeys exist in Werkmail but are narrower than a full marketing cloud.

## Stay on Resend if

You are building a developer product, send mostly transactional notifications, and already handle consent and marketing elsewhere.

## Switch to Werkmail if

You need **one** EU system for authenticated sending, consent evidence, and mixed clinical/marketing traffic — GUI and API on the same gate.

## If you migrate

Keep rendering HTML in your app; Werkmail accepts HTML/text on send. Rework webhook handlers to [Werkmail signatures](/webhooks). Recreate domains and suppression lists — do not assume provider-account suppressions transfer. If you used React Email, keep the renderer; only the transport changes.

See also: [Compare hub](/compare) · [HTTP API](/api) · [Webhooks](/webhooks)