# Werkmail vs AhaSend

Reviewed August 2026. AhaSend is an **EU transactional send API and SMTP relay** (Amsterdam): PAYG volume, official SDKs, inbound routing, and dedicated IPs on higher tiers. Werkmail is an **EU operator platform** for authenticated transactional *and* marketing mail with DSGVO gates and practice kinds.

## At a glance

| | AhaSend | Werkmail |
| --- | --- | --- |
| Primary job | Transactional API + SMTP at scale | Isolated tenants, consent, practice kinds, then send |
| Company geography | Netherlands | Austria (operations in Frankfurt) |
| Volume posture | PAYG (Pro ~25k included, Max ~100k, extras billed) | Termin 5k / Praxis 20k / Gruppe 100k / custom caps |
| SMTP | First-class | Not the product (HTTP send + inbound hook) |
| Marketing | Out of scope | `broadcast` with DOI and Impressum |
| Practice kinds | Generic transactional | `termin` / `recall` / `doi` with compliance checks |
| Partner / white-label | Subaccounts, DNS whitelabel, BYO DKIM | Isolated tenants; no partner SMTP resale |

## They win

- **PAYG scale and SMTP.** If you already speak SMTP and need hundreds of thousands of transactional messages, their unit economics and relay are the shorter path.
- **Developer surface.** Official SDKs, CLI, sandbox, inbound routing, and platform-partner features (subaccounts, per-domain selectors).
- **Dedicated IPs / pools** on higher volume — a real lever once you have a clean domain.
- **Retention knobs** (days of logs/bodies) you can set per plan instead of a single product default.

## Werkmail wins

- **Transactional ≠ broadcast.** AhaSend is transactional-only by design. Werkmail splits streams so a recall campaign cannot inherit appointment reputation.
- **Enforced DSGVO primitives.** Consent ledger (wording, IP, time), channel prefs, DSAR export/erase, Impressum before broadcast — not “GDPR-ready” as residency alone.
- **Practice semantics and inbox-risk gate** on GUI and API. Tracking off by default for clinical kinds.
- **Reputation pause as a product.** Bounce ≥5% / complaint ≥0.1% (min 20) can halt the tenant. Isolation is one workspace, one sending tenant.

## Honest gaps on our side

- We will not match PAYG extra-usage pricing or an SMTP relay.
- We do not ship official language SDKs or a CLI; HTTP + OpenAPI + inbound hooks is the DX.
- If you resell email to many brands, their partner/whitelabel story is broader.

## Stay on AhaSend if

You send transactional mail at volume over SMTP or a thin REST API, you already own consent elsewhere, and you do not need practice kinds or a marketing stream that cannot pollute receipts.

## Switch to Werkmail if

You are an EU practice or regulated sender who must **show** consent, keep appointment mail off the newsletter pool, and give a DPO an audit trail — not only EU-hosted transport.

## If you migrate

Keep SMTP apps talking SMTP until you rewrite them to [Send API](/api/send) (`Idempotency-Key`, `message_kind`, route slug). Recreate domains and suppression lists. Do not expect dedicated IPs on Werkmail. Map receipts to `outgoing` / `transactional`; newsletters need Praxis or Gruppe (Termin blocks broadcast).

See also: [Compare hub](/compare) · [Regulated transactional](/regulated) · [HTTP API](/api)