# MailPace — Transactional Email

MailPace by OhMySMTP Ltd holds a panel rating of 2.5/5 from 6 AI judges (category median 3/5), as of 2026-11-01. Provenance: UK / wider Europe; sovereignty: not determined.

- Vendor: OhMySMTP Ltd (https://mailpace.com)
- Category: [Transactional Email](https://whats-best.ai/software/transactional-email.md)
- Provenance (editorial classification): UK / wider Europe
- Canonical page: https://whats-best.ai/software/transactional-email/mailpace
- Alternatives: https://whats-best.ai/software/transactional-email/mailpace/alternatives ([markdown](https://whats-best.ai/software/transactional-email/mailpace/alternatives.md))
- Data as of: 2026-11-06 · evaluated 2026-11-01 · oldest source captured 2026-11-01

**AI-generated.** Every score, rationale and verdict here is written by a panel of AI judges from public evidence — an analysis, not a hands-on test. Every fact quotes the vendor page it was read from. No score can be bought. How scores are made: https://whats-best.ai/methodology

## At a glance

- Vendor: OhMySMTP Ltd
- Headquarters: Not stated on the vendor’s pages as of 1 Nov 2026
- Data hosting: Default not stated; pages mention France and the EU [S10]
- Free plan: Not stated on the vendor’s pages as of 1 Nov 2026
- Starting price: “💰 Starting Price Under $4/month 1000 emails/month for under $4/month. Scaling plans from $10/month (10,000+ emails).” (vendor’s words) [S1]

## The panel's verdict

MailPace is a transactional-only email API and SMTP relay from OhMySMTP Ltd, a company of England and Wales, with stored data hosted in France on Clever Cloud. It is strongest on deliverability at 6 to 7: DKIM verification is enforced before any send, shared IPs are warmed, and a Gmail average delivery time of 1.19 seconds is published. Data and security at 5 to 6 and sovereignty at 5 to 6 also hold, resting on a public data processing agreement, subprocessors named with their locations, fixed retention of 30 days in the dashboard and 37 days at most, and no open or click tracking. Observability is the weakest area at a flat 4, with no public information on a searchable message log, an events API, or webhook signatures. Pricing transparency scores 4 to 5: higher-tier prices, overage rates, minimum term and VAT treatment are not shown, and the captured pages give different figures on a free tier. Judges stayed close — the widest spread, sending API at 4 to 6, produced no flagged disagreement.

**Speaks for it:**
- Deliverability scored 6 to 7 on the strength of enforced DKIM verification, warmed shared IPs and a published Gmail average delivery time of 1.19 seconds
- A public data processing agreement names subprocessors with their locations and Standard Contractual Clauses signed with each vendor
- Retention is fixed and stated — 30 days in the dashboard, 37 days maximum including backups — and opens and clicks are never tracked
- Idempotency keys make retries safe, and inbound email arrives as JSON webhooks on every account
- A 99% monthly uptime guarantee carries credits of 5% of the monthly fee per 30 minutes of unavailability

**Held against it:**
- Observability scored a flat 4, with no public information on a searchable message log, an events API, statistics per domain, or webhook signatures
- Prices for tiers above the starting points, overage rates, minimum term and VAT treatment are not shown, the captured pages give different figures on a free tier, and the terms carry a $100 reinstatement fee
- Batch sending is not supported beyond 50 comma-separated recipients in the To field
- Sending runs through SMTP servers based in the UK and the contracting entity is OhMySMTP Ltd of England and Wales, so the chain is not end-to-end EU
- We found no public information on two-factor authentication, SSO, audit logs, certifications such as ISO 27001 or SOC 2, or a public status page

**Best for:**
- You send transactional email only — password resets, OTP and 2FA codes, order confirmations — where enforced DKIM and warmed shared IPs fit the job
- You need retry-safe one-time codes, with idempotency keys and automatic retries on 4xx errors for up to three days
- You want short, fixed retention and no open or click tracking, backed by a public data processing agreement naming its subprocessors
- You run per-client sending and need domains with their own API tokens provisionable over HTTP

**Avoid if:**
- You send marketing emails or bulk newsletters — the terms strictly prohibit them
- You need batch sending or dedicated IP addresses — batch is unsupported beyond 50 comma-separated recipients and the vendor states it offers no dedicated IPs
- You need an end-to-end EU chain or an EU contracting entity — sending runs through UK-based SMTP servers and claims are governed by UK law
- Your use is safety-critical — the terms prohibit use where failure could lead to death or serious bodily injury

## Scores by judge and criterion

Scores out of 5, each judge scoring independently against the published rubric (v1). "n/r" = not rated: the vendor publishes no price, or the judge found no public information on that criterion.

| Criterion | The SaaS Developer | The Platform Engineer | The Shop Operator | The Data Protection Officer | The Agency Lead | The Skeptic |
| --- | --- | --- | --- | --- | --- | --- |
| Sending API, SMTP & developer experience | 3/5 | 3/5 | 2.5/5 | 2/5 | 3/5 | 3/5 |
| Deliverability & sender reputation | 3/5 | 3/5 | 3/5 | 3/5 | 3/5 | 3.5/5 |
| Message logs, events & webhooks | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 |
| Message data, retention & security | 2.5/5 | 3/5 | 2.5/5 | 3/5 | 3/5 | 3/5 |
| Reliability, accounts & support | 2.5/5 | 2.5/5 | 2/5 | 2.5/5 | 2.5/5 | 2.5/5 |
| European sovereignty | 2.5/5 | 2.5/5 | 2.5/5 | 3/5 | 3/5 | 3/5 |
| Pricing transparency | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 | 2.5/5 |
| **Weighted verdict** | **2.5/5** | **2.5/5** | **2.5/5** | **2.5/5** | **2.5/5** | **3/5** |

### The judges

- **The SaaS Developer** (v1.0): Backend developer at a twelve-person B2B SaaS in Hamburg, built on Laravel, that sends sign-up confirmations, password resets, invoices and weekly digests to 40,000 users. Has replaced the mail driver once already and does not want to again. Wants an official driver for the framework, templates with variables, a test mode that never reaches a real inbox, signed webhooks for bounces, and a log that answers "did this user get the reset mail?" without opening a ticket.
- **The Platform Engineer** (v1.0): Platform engineer at a fintech in Frankfurt whose customers sign in with a one-time code sent by email, so a delay of three minutes is an outage. Is on call for it. Reads the status page history before the feature list, wants the SLA in writing with credits, mail queued and retried during an incident, delivery latency per mailbox provider, alerts on bounce spikes, and scoped API keys that can be rotated without a deploy.
- **The Shop Operator** (v1.0): 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.
- **The Data Protection Officer** (v1.0): In-house data protection officer at a health software company whose appointment reminders and lab-result notices carry patients' names. Treats the sending service as a processor like any other. Reads the DPA, the subprocessor list and the retention section first: whether message bodies are stored and for how long, whether open tracking can be turned off, which entity signs, and whether the EU region covers the logs as well as the mail.
- **The Agency Lead** (v1.0): Technical lead at a web agency in Cologne that builds and runs thirty client applications, from a booking portal to a membership site, each sending its own mail from the client's domain. Wants one account with a sub-account, keys and limits per client, domains verified by API, roles so a client can see their own logs and nothing else, and a price per client that can be written into a maintenance contract.
- **The Skeptic** (v1.0): Has seen "99% deliverability" with no method behind it, "dedicated IPs" that shared a pool with bulk senders, "EU hosting" that covered the API endpoint but not the logs, and seven days of log retention discovered during an incident on day eight. Reads that a vendor is "trusted by thousands of developers" and asks how bounces are suppressed, what is stored per message, which entity signs the DPA — and what moving away would cost.

## European sovereignty — proven facts

Built only from facts on the vendor's own pages; a dimension we could not prove is left open, never scored as zero. Headline: not determined.

| Dimension | Finding | Points | Source |
|---|---|---|---|
| Legal entity | Not determined | — | — |
| Hosting location | Not determined | — | — |
| Hosting options | Not determined | — | — |
| Open source | Not determined | — | — |
| Data processing agreement | Not determined | — | — |
| Transfer impact assessment | Not determined | — | — |

## Key facts

Each fact is the vendor's own statement, cited to the source page it was read from ([S*n*] → Sources).

**Compliance**
- Article28 info: yes [S10]
- Data encryption: yes · offsite with replication, bcrypt passwords · https [S10]
- Dpia assistance: yes · yes [S10]
- Encryption: yes [S9]
- Staff training: for support and maintenance · yes [S10]
- Tls support: 1.2 [S5]

**Data**
- Collected: email address · IP address and browser version · site usage via HTTP logs and necessary session cookies [S9]
- Deletion: yes · no · yes [S10]
- No sale: yes · yes [S9]
- Retention: 37 · 7 · 30 [S10]

**Hosting**
- Data location: yes [S1]
- Data location: EU · France [S10]
- Data residency: France/EU only · sending via UK SMTP servers [S10]

**Integrations**
- API endpoint: POST · https://app.mailpace.com/api/v1/send · MailPace-Server-Token [S2]
- API endpoint: MailPace-Server-Token header · POST · https://app.mailpace.com/api/v1/send [S12]
- Languages: cURL · Node.js · Ruby · PHP · Go · Python · Rails · Symfony · Elixir [S2]
- Languages: cURL · Node.js · Ruby · PHP · Go · Python · Rails · Symfony · Elixir [S11]
- Languages: cURL · Node.js · Ruby · PHP · Go · Python · Elixir · Rails · Symfony [S12]
- Listed: SMTP, Ruby on Rails, JavaScript, PHP, Erlang, Go, Rust [S6]

**Legal**
- Controller processor roles: customer=controller, MailPace=processor · MailPace=sub-processor [S10]
- DPA status: DPA is an addendum to Terms of Service [S10]
- Effective date: 2022-10-11 [S10]
- Entity: OhMySMTP Ltd · England and Wales · 13200428 [S8]
- Entity: OhMySMTP Ltd · England and Wales · 13200428 [S9]
- Governing law: United Kingdom [S8]
- Last updated: 2026-08-30 [S9]
- Last updated: 2026-10-08 [S10]
- Liability: yes [S10]
- No notification required: no [S10]
- Publicly available: yes [S10]
- Rebrand: 2022-01-28 · MailPace · OhMySMTP [S8]
- Signature required: automatic via use · no [S10]
- Terms change notice: yes [S8]
- Terms last updated: 2026-01-09 [S8]

**Pricing**
- Free tier: 100 [S1]
- Reinstatement fee: 100 [S8]
- Starting price: month · 4 · 1000 · 10 [S1]
- Volume tiers: 10000 · 100000 · 300000 · 600000 · 1000000 [S7]

**Product**
- Allowed use: yes · no · no [S8]
- Any from address: Any from address for verified domains via DNS update [S6]
- API: server token · RESTful HTTP API with JSON payloads [S1]
- API send endpoint: POST · https://app.mailpace.com/api/v1/send · MailPace-Server-Token [S4]
- Attachment whitelist: yes · yes · yes [S5]
- Bounce reports: yes [S5]
- Data categories: contents and related metadata of transactional emails [S10]
- Data ownership: yes [S10]
- Delivery time: 1.19 [S1]
- Dkim required: yes [S5]
- Dkim required: yes [S6]
- Dkim signing: yes [S6]
- Dmarc support: Advanced Verification · yes [S5]
- Domain API: Domain API: automate domain provisioning, create domains, generate domain API tokens with organization token [S2]
- Domain authorization: Sending domain must be owned or authorized by the account holder [S8]
- Domain ownership required: yes [S5]
- Feature guides: idempotent_requests · block_lists · verification · webhooks · inbound_emails [S6]
- Feedback loops: yes [S5]
- Greylisting handled: yes [S5]
- Https API: HTTPS API for sending transactional emails [S2]
- Https only: yes [S6]
- Idempotency support: yes · Idempotency-Key header in API request [S11]
- Inbound email: yes [S1]
- Inbound setup: domain + webhook endpoint · 1 [S12]
- Inbound unlimited catchall: every account · unlimited · yes [S12]
- Languages: yes · Node.js · Ruby · Python · PHP · Go · Elixir · curl [S1]
- Manual account review: yes [S5]
- Monitoring: yes · yes [S5]
- No batch emails: no · 50 [S6]
- No dedicated ips: no [S5]
- No delivery guarantee: no [S8]
- No free plan: no [S5]
- No header spoofing: no [S5]
- No static ips: yes · no [S6]
- Privacy tracking: yes · no [S1]
- Protocols: yes · 587 · 25 · yes [S1]
- Sdks: yes [S2]
- Send API endpoint: https://app.mailpace.com/api/v1/send · MailPace-Server-Token [S11]
- Sending support: yes [S5]
- SLA credit: 100% of monthly fees · 5% of monthly fee · 30 [S8]
- SLA uptime: maintenance · monthly · 99 [S8]
- Smtp endpoint: api token as username and password · smtp.mailpace.com · 587 [S3]
- Smtp framework examples: Rails · Node · Laravel · Django · Java · Wordpress · Magento [S3]
- Smtp retry handling: yes · 3 [S5]
- Spam filter: Rspamd · all outgoing emails [S5]
- Special category data: customer · yes [S10]
- Spf dmarc optional: yes · yes [S6]
- Spf passed: yes [S5]
- Supported languages: cURL · Node.js · Ruby · PHP · Go · Python · Rails · Symfony · Elixir [S4]
- Time to inbox published: yes [S5]
- Transactional only: yes · yes [S6]
- Use cases: password resets · OTP & 2FA codes · welcome emails · order confirmations · system alerts · email verification [S1]
- Warmed ips: yes [S5]
- Webhook events: queued · delivered · bounced · spam · POST [S4]
- Webhook setup: enable per-domain webhooks and set one or more endpoints [S4]
- Webhooks: delivery status · bounces · complaints [S1]

**Subprocessors**
- Appsignal: AppSignal · Error & Performance Monitoring · Amsterdam [S9]
- Clevercloud: Clever Cloud · Infrastructure Hosting · EU [S9]
- Freethought: Freethought · Infrastructure Hosting · UK [S9]
- Hetzner: Hetzner · Off-site backups · Germany · 7 [S9]
- Objection right: email · privacy policy page · blog · yes [S10]
- Paddle: Paddle · Merchant of Record · UK [S9]
- Scc and notification: yes · yes [S10]
- Tutanota: Tutanota · Support email · Germany [S9]

**Support**
- Credit claim: email · 30 [S8]
- Docs: yes [S12]
- Documentation: Public documentation to get started in minutes [S3]
- Documentation: yes [S4]

## Questions

### Is MailPace European?

Yes, though not from the EU. whats-best.ai classifies MailPace as UK / wider Europe.

### Where does MailPace store data?

The default storage location for customer data is not stated on the vendor’s pages as of 1 Nov 2026. The vendor’s pages mention France and the EU as hosting locations, per [the vendor’s page captured 1 Nov 2026](https://whats-best.ai/evidence/14319).

### Does MailPace have a free plan?

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

### What are the best alternatives to MailPace?

As of 2 Nov 2026, the panel rates [Lettermint (3.5/5)](https://whats-best.ai/software/transactional-email/lettermint), [Bird Email API (formerly SparkPost) (3/5)](https://whats-best.ai/software/transactional-email/bird-email-api) and [Postmark (3/5)](https://whats-best.ai/software/transactional-email/postmark) 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 [Lettermint](https://whats-best.ai/software/transactional-email/lettermint) (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: [how scores are made](https://whats-best.ai/methodology#ordering). The full list, with European products first: [MailPace alternatives](https://whats-best.ai/software/transactional-email/mailpace/alternatives).

## What this page leaves out

- 49 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 10 hosting facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 8 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 6 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 5 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 3 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 1 data fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material.
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown.
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement.

## Sources

- [S1] Vendor homepage: https://mailpace.com/ (checked 2026-11-01)
- [S2] Features page (email API): https://mailpace.com/features/transactional-email-api (checked 2026-11-01)
- [S3] Features page (SMTP relay): https://mailpace.com/features/transactional-smtp-service (checked 2026-11-01)
- [S4] Features page (webhooks): https://mailpace.com/features/webhooks (checked 2026-11-01)
- [S5] Features page (deliverability): https://mailpace.com/how-we-keep-delivery-rates-high (checked 2026-11-01)
- [S6] API documentation: https://docs.mailpace.com/ (checked 2026-11-01)
- [S7] Pricing page: https://mailpace.com/pricing (checked 2026-11-01)
- [S8] Terms of service: https://mailpace.com/terms (checked 2026-11-01)
- [S9] Privacy policy: https://mailpace.com/privacy (checked 2026-11-01)
- [S10] Data processing agreement (dpa): https://mailpace.com/dpa (checked 2026-11-01)
- [S11] Sending API, SMTP & developer experience — found from sitemap: https://mailpace.com/features/idempotent-email-api (checked 2026-11-01)
- [S12] Sending API, SMTP & developer experience — found from sitemap: https://mailpace.com/features/inbound-email (checked 2026-11-01)
- [S13] Code repository (open-source licence) — found from the homepage: https://github.com/mailpace/templates (checked 2026-11-01)

---

Cite as: whats-best.ai, "MailPace — Transactional Email", AI panel analysis, as of 2026-11-06. https://whats-best.ai/software/transactional-email/mailpace

Corrections: https://whats-best.ai/correct/1274?target=page