# Werkmail vs Postmark

Reviewed August 2026. Postmark is a strong **transactional** sending product (now under ActiveCampaign). Werkmail is an **EU operator platform**: same send path for GUI and API, plus consent, campaigns, and practice kinds.

## At a glance

| | Postmark | Werkmail |
| --- | --- | --- |
| Primary job | Transactional delivery | Transactional **and** marketing, with practice kinds |
| Default region story | US-rooted product | Frankfurt / **eu-central-1** |
| Stream split | Message streams | `outgoing` vs `broadcast` never share reputation |
| Consent evidence | Not the product | DOI ledger, channel prefs, DSAR |
| Campaigns | Via the parent marketing suite | Block editor, A/B sample → winner, linear journeys |
| Practice kinds | Generic templates | `termin` / `recall` / `doi` with compliance checks |
| Dedicated IPs | Available on higher volume | Not a first-class product surface |

## They win

- **Transactional reputation and simplicity.** Postmark’s job is “this receipt left and arrived.” Message streams, bounce handling, and docs are mature.
- **Developer experience for “just send.”** Templates, servers, and a focused API. Fewer product surfaces than a full SaaS cockpit.
- **Dedicated IP options** on higher volume plans — useful if you already run a clean transactional domain.
- **Support culture** aimed at deliverability tickets, not marketing automation.

## Werkmail wins

- **EU-first residency.** Production sending and data in Frankfurt / **eu-central-1**. Postmark is a US-rooted product; EU data options are not the default story.
- **Transactional ≠ broadcast.** `outgoing` and `broadcast` never share reputation. Marketing cannot ride a receipt stream.
- **DSGVO primitives.** Double opt-in, consent ledger (wording, IP, time), channel prefs, DSAR export/erase, Impressum required before broadcast.
- **Practice semantics.** `termin`, `recall`, `doi` with tracking defaults and compliance checks — not generic “template A.”
- **Inbox-risk gate** on every send path, plus a deliverability cockpit (warm-up, bounce reasons, content-score history).

## Honest gaps on our side

- Postmark’s drag-and-drop and campaign surface (via the parent marketing suite) is broader than Werkmail’s block editor and linear journeys.
- If you only send password resets from a US app and never touch newsletters or clinics, Postmark is often the shorter path.
- Per-message pricing at scale can look similar; Werkmail’s Test/Supporter plans are for EU operators, not a global transactional race.

## Stay on Postmark if

You send high-volume transactional mail, already trust their streams, and do not need a consent ledger, Impressum gate, or healthcare message kinds.

## Switch to Werkmail if

You are an EU practice or operator who sends **both** appointment mail and marketing, must show consent evidence, and wants isolated tenants in Frankfurt.

## If you migrate

You gain a consent ledger, stream isolation, and practice kinds on the same gate as the API. You lose Postmark’s dedicated-IP story and a long-tuned transactional template ecosystem. Plan DNS (SPF, DKIM, MAIL FROM) on the new workspace; do not share a warm domain across both products.

See also: [Compare hub](/compare) · [Practice mail](/practice-mail) · [Sending](/sending)