Werkmail vs EU transactional APIs

Reviewed August 2026. A wave of EU-incorporated transactional APIs now sell the same pitch: REST + SMTP, GDPR because the company is European, Resend-like DX, a free tier, and “we are not a US ESP.” Named pages cover AhaSend, EUSend, and Lettermint. This page is the category.

Werkmail is not trying to win that race on time-to-first-send or unit price.

At a glance

	Typical EU transactional API	Werkmail
Headline	EU company + send API	Enforced isolation, consent, practice kinds
SMTP	Usually yes	No
Marketing	Often none, or a footer on bulk	Separate `broadcast` stream
Consent evidence	You build it	Ledger with wording, IP, time
Isolation	Shared pool or DIY subaccounts	One sending tenant per workspace
Healthcare	Template ID	`termin` / `recall` / `doi` + check API
Moat they optimize	DX and price	Gates that fire even when you are in a hurry

They win

Speed. Verify a domain, paste a key, send. Official SDKs and SMTP mean an existing app moves this week.
Price for pure transactional. Free tiers of a few hundred to a thousand messages, then cheap PAYG. Werkmail has no free tier: Starter is 19 EUR for 10,000 emails per month, and every workspace starts in a sandbox until a person approves production access. It is built for regulated senders, not for a volume war.
Honesty about focus. Many of these products say they are not a marketing cloud. That is a feature.
Residency as a procurement checkbox. An EU company and EU data centres satisfy a lot of RFPs that only ask “is it in Europe?”

Werkmail wins

Residency is not compliance. A Dutch or German GmbH with SMTP does not give you a consent ledger, Impressum gate, or channel-level DOI. We ship those as product, and we block sends that skip them.
Isolation you cannot turn off. One noisy neighbour or one mixed stream is how domains burn. outgoing and broadcast never share reputation.
Regulated transactional. Practice kinds, tracking off, ICS on appointments, audit CSV, DSAR export/erase — the work a clinic’s DPO actually asks for.
Same gate on GUI and API. Cheap EU APIs optimize the curl. We optimize “the intern cannot send a discount in a Termin subject.”

Honest gaps on our side

We will lose bake-offs that score SDKs, SMTP, and cents per thousand.
We will not clone every EU transactional dashboard. If all you need is “send this receipt from Europe,” a thin API is rational.
Higher Werkmail volume (Growth 50k up to Compliance 1M) is arranged with sales, or paid by card in the dashboard where checkout is enabled for the plan. Every workspace still starts in the sandbox.

Stay on a thin EU API if

Your app is transactional-only, legal is satisfied by an EU vendor + DPA, and you already store consent in your own product.

Switch to Werkmail if

Someone will ask for evidence (who consented, which wording, which channel), or appointment mail must not share a pool with a newsletter — and you do not want to staff that platform yourself.

If you migrate

Treat this as a product change, not an SMTP host swap. You will set message_kind and routes, complete DOI for broadcast, and accept an inbox-risk block. That friction is the point.