MailPace

What Is MailPace?

Most transactional email providers track every open and every click by default, whether or not the sender asked for it. MailPace doesn't. That single design decision, more than any feature list, defines what the product is trying to be. It's a transactional email API built by a small UK team that treats recipient privacy as the default rather than an opt-out buried in settings.

MailPace launched in 2021 under OhMySMTP Ltd, a small software company registered in London (Companies House number 13200428). The product is deliberately narrow in scope — it sends password resets, one-time codes, receipts, and other application-triggered emails, and explicitly does not do marketing campaigns or bulk newsletters. That focus lets a small team compete on reliability and delivery speed rather than trying to match Postmark or SendGrid feature-for-feature across both transactional and marketing use cases.

The company states its infrastructure runs 100% within the European Union, on carbon-neutral, renewable-powered servers from smaller local providers rather than the big three US hyperscale clouds. For developers building applications that need to send system emails without routing recipient data through US infrastructure, that's a specific and verifiable claim, not vague marketing language about being "privacy-focused."

The company reports having delivered over 200 million emails since its 2021 launch, serving more than 2,000 active senders, with an average delivery time to Gmail of around 1.19 seconds. Those are useful reference points for evaluating reliability, though they come from MailPace itself rather than an independent audit.

Key Features

No Tracking by Default

Open tracking and click tracking are the norm across the transactional email industry — a tracking pixel embedded in every email, a redirect wrapped around every link. MailPace ships without either by default. For applications sending password-reset links or one-time codes, that removes an entire category of unnecessary personal-data processing, which simplifies both privacy posture and GDPR data-mapping exercises.

HTTP API and SMTP

Developers can integrate via a REST API with JSON payloads or a standard SMTP endpoint on port 587 with TLS. Both paths support the same core sending logic, so teams can start with SMTP for a quick integration and move to the API later without re-architecting how emails get sent.

Inbound Email to Webhooks

MailPace can receive inbound email and convert it into a JSON webhook payload, useful for applications that need to process replies — a support ticketing system parsing customer responses, for example. This is a feature that's often bolted on awkwardly by competitors; MailPace treats it as a first-class capability alongside outbound sending.

Framework Integrations

Native support exists for Laravel via a Symfony Mailer bridge and for Ruby on Rails through an ActionMailer plugin, alongside general HTTP API access for Node.js, PHP, and anything else that can make a REST call. These aren't the deepest SDK ecosystems in the category, but they cover the frameworks most commonly used by the small-to-mid-size teams MailPace targets.

Deliverability Tooling

MailPace handles DKIM, SPF, and DMARC configuration and automates bounce and blocklist management, so a bounced address doesn't need manual clean-up before the next send. Idempotent request handling prevents duplicate sends if a client application retries a request after a network timeout, a subtle but useful protection for anything sending time-sensitive codes or receipts.

Unlimited Everything, No Tiered Gating

Every plan — including the smallest paid tier — includes unlimited sending domains, unlimited team members, and unlimited webhooks. There's no artificial feature wall pushing customers toward a more expensive plan just to add a colleague or a second domain; the only variable that changes price is email volume.

Pricing

MailPace's boldest pricing claim is transparency, and it mostly delivers: cost scales directly with the number of emails sent or received, with no hidden per-seat or per-domain charges layered on top. Paid usage starts around $10/month, which covers the first 10,000 emails before the per-email rate applies to additional volume. Higher-volume senders — 100,000 emails a month and beyond — get a custom rate through an interactive pricing calculator on the site rather than a fixed published table.

There's also a genuinely free option, described on the pricing page as a "secret free plan": up to 100 emails/month, activated by contacting support. This works for genuinely small projects or early-stage testing, but anyone expecting a self-serve free-tier signup flow will need to reach out directly instead.

Annual billing is also available and tends to work out cheaper than paying month to month at the lowest volumes. Because every plan includes unlimited domains and team members, a growing team doesn't face a forced upgrade just to add a colleague or a new sending domain — only rising email volume moves the bill.

The one real friction point in MailPace's pricing is visibility: exact costs above the entry tier aren't shown without using the calculator. That makes upfront budgeting slightly harder than with a competitor that publishes a fixed table. For teams with predictable, low-to-moderate volume, the $10/month starting point is easy to plan around regardless.

EU Compliance & Privacy

MailPace's central claim — 100% EU-hosted infrastructure — is the strongest compliance signal a transactional email provider can offer, because it removes the cross-border data-transfer question that dogs any provider running on US hyperscale cloud. Combined with carbon-neutral, renewable-powered data centres from smaller regional providers, the infrastructure story is specific rather than generic.

The no-tracking-by-default design compounds this advantage. Because open and click tracking are off unless explicitly enabled, MailPace processes meaningfully less personal data about recipients than competitors that track everything and let senders opt out. For a company building a GDPR data-processing record, "we don't collect this data in the first place" is a stronger position than "we collect it but delete it on request."

It's worth being precise about scope, though: MailPace is transactional-only. Marketing-email GDPR concerns around consent and unsubscribe management simply don't apply here, because the product refuses to send that category of email at all. Teams running both transactional and marketing email will need a second tool for the latter, with its own separate compliance considerations.

Who It's Best For

Developers building applications that need password resets, OTP codes, or receipts get a purpose-built tool without paying for marketing-email features they'll never use. If transactional is genuinely all you need, MailPace's narrow focus is an advantage, not a limitation.

Privacy-conscious teams and EU-regulated businesses benefit most from the 100% EU-hosted infrastructure and no-tracking-by-default design, particularly if internal policy or client contracts specify EU data residency for anything touching personal data.

Small teams and solo developers on tight, predictable budgets will appreciate the $10/month entry point and the unlimited domains, team members, and webhooks included at every tier, with no upsell pressure for basic account structure.

Larger teams needing enterprise SLAs or deep documentation should weigh MailPace's very small team against alternatives. Providers like Postmark have more staff to resolve DNS or IP-reputation issues quickly, plus more extensive documentation for complex integrations.

The Verdict

MailPace's core pitch — 100% EU-hosted, no tracking by default — is specific and falsifiable rather than marketing vagueness, and that combination is genuinely rare in transactional email. The pricing is transparent in principle, if not always transparent in the exact number until you use the calculator, and the framework integrations cover the common cases well. Honest trade-offs remain around scale and depth. A very small team means support and documentation don't match larger competitors, and the deliberately narrow transactional-only focus means teams needing marketing email will always require a second tool. For privacy-conscious developers who want exactly what MailPace does and nothing more, it's a strong, defensible choice.

Frequently Asked Questions

Is MailPace GDPR compliant?

Yes. MailPace describes its infrastructure as 100% EU-hosted, uses small European providers rather than major US clouds, and disables open/click tracking by default, which reduces the personal data it processes on recipients in the first place.

Does MailPace have a free plan?

There is an unlisted free allowance of up to 100 emails/month, available by contacting MailPace directly rather than appearing on the public pricing page. Paid usage starts at roughly $10/month for the first 10,000 emails and scales from there.

Can MailPace send marketing emails?

No. MailPace is built specifically for transactional email — password resets, OTP codes, receipts, and notifications — and explicitly does not support marketing campaigns or bulk newsletters. Teams needing both would pair it with a separate marketing tool.

How does MailPace compare to Postmark or SendGrid?

MailPace differentiates on EU hosting and privacy: no tracking pixels by default and carbon-neutral EU infrastructure. Postmark and SendGrid have larger teams, deeper documentation, and, in SendGrid's case, marketing-email features that MailPace deliberately omits.

Where is MailPace's data hosted?

MailPace states its infrastructure is 100% hosted within the European Union, using small local providers rather than major US hyperscale clouds. The operating company, OhMySMTP Ltd, is itself registered in the United Kingdom.