whats-best.ai
Search Sign in

Transactional Email

Lettermint

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Lettermint B.V. · lettermint.co

Compare with Postmark → Report an error on this page Is this your product? →

Link to this page

Lettermint: AI-assisted analysis on whats-best.ai Lettermint: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

Lettermint at a glance

Vendor
Lettermint B.V.
Headquarters
Not stated on the vendor’s pages as of 1 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 1 Nov 2026
Free plan
Yes, per the vendor’s own page source, captured 1 Nov 2026
Panel verdict
The AI panel rates Lettermint 3.5/5, the mean of 6 judges. Lettermint is a transactional email API and SMTP relay from Lettermint B.V., a founder-owned Dutch company in Zwolle. how scores are made
As of
Vendor pages captured 1 Nov 2026; evaluated by the panel 1 Nov 2026. all sources

Lettermint alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The Shop Operator

Weighted verdict

Runs a Shopware shop for kitchen equipment in Germany and Austria with 900 orders a week. Order confirmations, invoices and shipping notices went out through the hosting provider's mail server until a customer found theirs in spam and the support inbox filled up. Wants guided SPF and DKIM set-up a non-specialist can follow, a plugin for the shop, order mail kept apart from the newsletter, and someone to ask when Gmail starts refusing.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Shop Operator

Panel median The Shop Operator This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The Shop Operator
Sending API, SMTP & developer experience 3.5 of 5 3 of 5
Deliverability & sender reputation 3.5 of 5 3.5 of 5
Message logs, events & webhooks 3.5 of 5 3.5 of 5
Message data, retention & security 3.5 of 5 3.5 of 5
Reliability, accounts & support 3 of 5 3 of 5
European sovereignty 4.5 of 5 4.5 of 5
Pricing transparency 2 of 5 2 of 5

Sending API, SMTP & developer experience

How this is scored

How an application sends mail: a REST API and an SMTP relay with their limits stated, official SDKs and drivers for named languages and frameworks (PHP and Laravel, Node, Python, Ruby and Rails, Java, Go, .NET), stored templates with variables and versions, batch sending, attachments, idempotency keys, scheduled sending, a test or sandbox mode that does not deliver, inbound email parsed into a webhook, and the quality of the API reference and guides.

0 — Not a sending service; an application cannot send email through it by API or SMTP.

3 — An API or SMTP credentials to send a message; SDKs, templates, limits and a test mode are basic or not described.

5 — A documented REST API and SMTP relay, official SDKs for several named languages, stored templates with variables, attachments and batch sending, rate limits stated, a sandbox or test mode, and quick-start guides for named frameworks.

8 — An API reference with every endpoint and error code, idempotency keys, scheduled sending, template versions and a template language documented, inbound email parsed to a webhook, an OpenAPI specification or official CLI, framework drivers maintained by the vendor, and a migration guide from named competitors.

10 — An API a team builds its product on: versioning and deprecation policy published, backward compatibility stated, full parity between API and SMTP features, local or staging test tooling that mirrors production, and every limit, timeout and retry behaviour documented.

Report an error

The Shop Operator

The SMTP relay is documented down to host, ports and authentication, and there are official SDKs for PHP, Laravel, Symfony, Python, Node, Go, Java,.NET, Rust and Elixir, plus batch sending up to 500 emails per request, a sandbox mode, scheduled sending and an OpenAPI schema to download. We found no public information on stored templates with variables and versions, on idempotency keys for sending, or on a migration guide from named competitors. 2 6 7 13 14

Report an error

Deliverability & sender reputation

How this is scored

What the vendor does so the mail reaches the inbox: guided SPF, DKIM and DMARC set-up with a custom return path and tracking domain, shared IP pools and how senders on them are vetted and policed, dedicated IPs with automatic warm-up, transactional and bulk mail kept on separate streams or IP pools, bounces, complaints and unsubscribes turned into suppressions automatically, feedback loops with mailbox providers, blocklist and DMARC monitoring, compliance with the Gmail and Yahoo bulk-sender rules, and published delivery times or inbox placement with their method.

0 — No sender authentication and no bounce handling; mail goes out from shared addresses with no reputation management at all.

3 — SPF and DKIM can be set up and bounces are recorded; IP policy, stream separation and suppressions are basic or not described.

5 — Guided SPF, DKIM and DMARC set-up with a custom return path, shared IPs with a stated sender vetting policy, dedicated IPs available, automatic suppression of hard bounces and complaints, transactional and marketing mail separated by stream or IP pool, and deliverability guidance in the documentation.

8 — Dedicated IPs with automatic warm-up and pool management, a stated acceptable-use and vetting process for shared pools, feedback loops and blocklist monitoring, DMARC reports, BIMI or custom tracking domains, compliance with the Gmail and Yahoo sender requirements stated, delivery times published, and access to deliverability experts.

10 — Deliverability that can be verified: delivery time and bounce rates per mailbox provider published continuously with their method, inbox placement testing included, pool reputation shown to the customer, and a documented escalation path with mailbox providers.

Report an error

The Shop Operator

SPF, DKIM and DMARC are required before you can send, the DKIM key is hosted and rotated for you, a CNAME-based return path needs no manual SPF record, and transactional mail and newsletters go out on separate, already-warmed IP pools — exactly the separation I need between order confirmations and campaigns. Hard bounces are suppressed automatically, spam scores and a live Time to Inbox page per mailbox provider are published, and dedicated IPs exist as an add-on from 300,000 emails a month. We found no public information on vetting of senders on shared pools, feedback loops, DMARC reports or an explicit statement on the Gmail and Yahoo bulk-sender rules. 1 2 7 15 16 17

Report an error

Message logs, events & webhooks

How this is scored

What the team can see about each message once the application has handed it over: a message log searchable by recipient, subject, tag or message ID, the full event history (processed, delivered, deferred, bounced with the remote server's answer, opened, clicked, complained), how long logs and message content are kept, event webhooks with retries and a signature, an events API, dashboards and statistics per stream, tag or domain, alerts on bounce or complaint spikes, and access for a support team without developer rights.

0 — Nothing can be seen after sending; no logs, no events and no webhooks.

3 — Totals of sent and bounced messages; per-message logs, webhooks and retention are basic or not described.

5 — A searchable message log with per-message event history and the bounce reason, log retention stated, event webhooks for delivery, bounce, open, click and complaint, statistics per tag or domain, and an API to fetch events.

8 — Webhooks signed and retried with their schedule documented, the raw SMTP response and the rendered message viewable per send, log retention configurable or extended by plan, alerts on bounce, complaint or delivery-time thresholds, export or streaming of events to a named log or data tool, and read-only roles for support staff.

10 — Full traceability: every message traceable from API call to the receiving server's final answer, events streamed in real time with ordering and delivery guarantees stated, long retention with search across the whole history, and observability features documented with their limits.

Report an error

The Shop Operator

Email Activity lets me search messages by recipient, subject, status, project, route, tag and date range, open the event timeline plus the source, HTML and plain text of each send, and the Team API serves messages, per-recipient events and content over HTTP. Webhooks cover 22 event types including delivered, hard bounce, soft bounce and spam complaint, are signed with HMAC-SHA256, and retry on a documented schedule of twelve attempts over roughly fourteen hours with manual retry from the dashboard. Retention is a stated 28 days for message history, and we found no public information on alerts for bounce or complaint spikes, on extending or configuring that retention, or on streaming events to a log tool. 5 7 10 17 18

Report an error

Message data, retention & security

How this is scored

What is stored about each message and what the customer controls: whether message bodies are stored or only metadata, retention periods and the setting to shorten them, deletion of a recipient's data on request, open and click tracking that can be switched off per stream or message, TLS for delivery with an option to require it, encryption at rest, API keys with scopes and per-domain restrictions, IP allow-listing, two-factor authentication and SSO for the dashboard, an audit log, a vulnerability disclosure programme, and security certifications or audits with their scope. Where the data is processed and by whom is scored under sovereignty.

0 — Stores every message indefinitely with no controls, and the vendor states it uses message content for its own purposes.

3 — A privacy policy and a statement that data is encrypted; what is stored, retention and access controls are basic or not described.

5 — What is stored per message documented, retention periods stated, open and click tracking switchable, TLS used for delivery, API keys with restricted permissions, two-factor authentication for the dashboard, and a data processing agreement offered.

8 — Message content retention configurable down to none or metadata only, enforced TLS per domain or message, encryption at rest stated, scoped API keys and IP allow-listing, SSO (SAML) and roles, an audit log, deletion of recipient data by API, and ISO 27001 or SOC 2 stated with its scope.

10 — Data minimisation that can be verified: every stored field and its retention listed, content never stored unless the customer opts in, customer-managed encryption keys or equivalent, independent audits published with their scope, and every security control the customer has listed with its effect.

Report an error

The Shop Operator

The data processing agreement states exactly what is kept per message — content, attachments, recipient addresses, metadata and events for 28 days, analytics events for 90 days, logs for no more than 14 days — and email content can be hidden per project or route in the dashboard. Delivery uses TLS 1.2 or higher with an enforced-TLS option per route or for a single email, data is encrypted at rest, project API tokens carry IP allowlists, and an ISO 27001:2022 certificate sits in a public Trust Center. We found no public information on two-factor authentication or single sign-on for the dashboard, on deletion of a recipient's data via the API, or on a vulnerability disclosure programme. 1 2 10 11 14 19

Report an error

Reliability, accounts & support

How this is scored

Whether the platform can be relied on and run by a team: a public status page with incident history, uptime SLA and service credits published, redundancy or failover across data centres described, queueing and retry of mail during outages, sub-accounts or servers per application, client or tenant, team members with roles, separate environments, support channels and response times per plan, named migration help, and integrations with platforms that send mail on the customer's behalf (WordPress, Shopify, Shopware, Supabase, Vercel and similar).

0 — No status page, no support channel and no way to separate users or applications.

3 — A support contact and a single account; status page, SLA, sub-accounts and roles are basic or not described.

5 — A public status page with incident history, an uptime SLA on at least one plan, sub-accounts or separate servers per application, team members with roles, support by email or chat with stated hours, and plugins or guides for several named platforms.

8 — An SLA with service credits published, redundancy across data centres or regions described, mail queued and retried during incidents, sub-accounts with their own keys, domains and limits manageable by API, granular roles, support response times per plan, and migration assistance offered.

10 — Reliability that can be verified: uptime history published for years, post-mortems for incidents, multi-region failover documented, an SLA covering delivery latency as well as API availability, and white-label or reseller tooling for agencies and platforms.

Report an error

The Shop Operator

Projects with their own API tokens separate my shop's order mail from other applications, and the role system is genuinely granular: Owner, Admin and Member plus custom roles, with project access assignable per member. Support runs by ticket, email and Discord from an EU-based team, and enterprise customers on Pro get a written service level agreement with uptime and response-time guarantees. We found no public information on a status page with incident history, on mail queueing during outages, or on a Shopware plugin — WordPress and Symfony Mailer are the named platforms. 3 7 14 21 22

Report an error

European sovereignty

How this is scored

Who the contracting entity and the parent company are, where messages, logs and recipient data are processed and stored, whether an EU region can be chosen and what it covers, and who the subprocessors are (cloud hosting, sending infrastructure, logging, support and payment tools). Independently sourced by the sovereignty pipeline; every message carries personal data, so the whole sending chain counts, not only the dashboard.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.

3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.

5 — An EU region available and an EU contracting entity or EU representative, but parts of the chain (sending infrastructure, logs, support, payment) run through non-EU providers without a stated safeguard, or the EU region does not cover logs and account data.

8 — EU processing of messages, logs and account data on named infrastructure, an EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated.

10 — Sovereign end to end and evidenced: European ownership, entity, hosting, sending infrastructure and every subprocessor, data export and deletion documented, and certifications published with their scope rather than implied.

Report an error

The Shop Operator

A Dutch company in Zwolle, founder-owned with no investors, sends from its own EU network under its own IP addresses with mail processed and stored only in the EU and encrypted backups at a separate provider in Germany. Every subprocessor is listed with its location and whether it touches email — UpCloud in the Netherlands, OVH Cloud in Germany, Postmastery in the Netherlands, with Aikido and Mistral in Europe having no email access — and the Article 28 data processing agreement applies automatically and is countersigned on request. Data export in a machine-readable format is documented, but we found no public information on documented deletion beyond a 30-day retrieval window after termination, which keeps it from the very top. 1 3 7 8 10 11

Report an error

Pricing transparency

How this is scored

Whether a buyer can compute the real annual cost from public pages alone: price per tier by monthly message volume, the price per additional thousand messages, the free tier and its limits, what dedicated IPs, extra log retention, sub-accounts, SSO and support plans cost, minimum term, and whether unused volume carries over.

0 — No public prices at all; every customer is a sales call.

3 — A starting price or a free tier exists, but how cost scales with volume or which features cost extra is unclear.

5 — Tiers are public with their monthly volume and price, but at least one commonly needed piece (overage rate, dedicated IP, longer log retention, SSO, support plan) is unpriced or "on request".

8 — Every tier priced publicly with its volume and overage rate per thousand messages, dedicated IPs and add-ons priced, log retention per tier stated, minimum term and VAT treatment stated.

10 — Complete price computability: annual cost derivable for a given monthly volume, number of domains and sub-accounts and feature set, with every add-on, support and overage fee and the cancellation terms published.

Report an error

The Shop Operator

The free tier's 300 emails a month, the per-plan feature gates, the 28-day message history on every plan and billing in euros excluding VAT are public, with no credit card and cancellation at any time. But the captured pricing page gives no euro amounts for the paid tiers, describes the overage only as a small fee, and names the dedicated IP and bring-your-own IP as add-ons with no figures, so I cannot compute my annual cost for roughly 4,000 transactional mails a month from the public pages. 7 8

Report an error

European sovereignty — proven facts

0 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Not determined ⚠ unverified — uncited Report an error
Hosting options Not determined — uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined ⚠ unverified — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Lettermint

Is Lettermint European?

Yes. whats-best.ai classifies Lettermint as EU-Made.

Where does Lettermint store data?

Not stated on the vendor’s pages as of 1 Nov 2026.

Does Lettermint have a free plan?

Yes. Lettermint has a free plan, per the vendor’s page captured 1 Nov 2026.

What are the best alternatives to Lettermint?

As of 2 Nov 2026, the panel rates Bird Email API (formerly SparkPost) (3/5), Postmark (3/5) and Mailjet Email API (3/5) highest among the other 15 Transactional Email products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Bird Email API (formerly SparkPost) (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Lettermint alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Do you know more about Lettermint? Tell us Report an error on this page

Sources (22)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage lettermint.co Checked 1 Nov 2026 Details →
  2. 2 Features page (transactional email) lettermint.co Checked 1 Nov 2026 Details →
  3. 3 Features page (European email infrastructure) lettermint.co Checked 1 Nov 2026 Details →
  4. 4 API documentation lettermint.co Checked 1 Nov 2026 Details →
  5. 5 Documentation (webhooks) lettermint.co Checked 1 Nov 2026 Details →
  6. 6 Integrations page lettermint.co Checked 1 Nov 2026 Details →
  7. 7 Pricing page lettermint.co Checked 1 Nov 2026 Details →
  8. 8 Terms of service (company details) lettermint.co Checked 1 Nov 2026 Details →
  9. 9 Privacy policy lettermint.co Checked 1 Nov 2026 Details →
  10. 10 Data processing agreement (dpa) lettermint.co Checked 1 Nov 2026 Details →
  11. 11 Subprocessor list lettermint.co Checked 1 Nov 2026 Details →
  12. 12 Security / trust page trust.lettermint.co Checked 1 Nov 2026 Details →
  13. 13 Sending API, SMTP & developer experience — found from sitemap lettermint.co Checked 1 Nov 2026 Details →
  14. 14 Sending API, SMTP & developer experience — found from sitemap lettermint.co Checked 1 Nov 2026 Details →
  15. 15 Deliverability & sender reputation — found from sitemap lettermint.co Checked 1 Nov 2026 Details →
  16. 16 Deliverability & sender reputation — found from sitemap lettermint.co Checked 1 Nov 2026 Details →
  17. 17 Message logs, events & webhooks — found from sitemap lettermint.co Checked 1 Nov 2026 Details →
  18. 18 Message logs, events & webhooks — found from sitemap lettermint.co Checked 1 Nov 2026 Details →
  19. 19 Message data, retention & security — found from sitemap lettermint.co Checked 1 Nov 2026 Details →
  20. 20 Message data, retention & security — found from sitemap lettermint.co Checked 1 Nov 2026 Details →
  21. 21 Reliability, accounts & support — found from sitemap lettermint.co Checked 1 Nov 2026 Details →
  22. 22 Reliability, accounts & support — found from sitemap lettermint.co Checked 1 Nov 2026 Details →