# MailerQ — Transactional Email

MailerQ by MailerQ (Copernica, Netherlands) holds a panel rating of 2/5 from 6 AI judges (category median 2.5/5), as of 2026-11-18. Provenance: provenance unknown; sovereignty: not determined.

- Vendor: MailerQ (Copernica, Netherlands) (https://www.mailerq.com)
- Category: [Transactional Email](https://whats-best.ai/software/transactional-email.md)
- Provenance (editorial classification): provenance unknown
- Canonical page: https://whats-best.ai/software/transactional-email/mailerq
- Alternatives: https://whats-best.ai/software/transactional-email/mailerq/alternatives ([markdown](https://whats-best.ai/software/transactional-email/mailerq/alternatives.md))
- Data as of: 2026-11-21 · evaluated 2026-11-18 · oldest source captured 2026-11-17

**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: MailerQ (Copernica, Netherlands)
- Headquarters: Not stated on the vendor’s pages as of 17 Nov 2026
- Data hosting: Default not stated; pages mention the Netherlands [S2]
- Free plan: Not stated on the vendor’s pages as of 17 Nov 2026

## The panel's verdict

No written verdict: the summary did not survive our own contradiction check, twice. The scores and sources below are unaffected.

## 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 | 1.5/5 | 1.5/5 | 1.5/5 | 1.5/5 | 1.5/5 | 1.5/5 |
| Deliverability & sender reputation | 2/5 | 2/5 | 2/5 | 2/5 | 2.5/5 | 2.5/5 |
| Message logs, events & webhooks | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 |
| Message data, retention & security | 1.5/5 | 1.5/5 | 1.5/5 | 2/5 | 2/5 | 1.5/5 |
| Reliability, accounts & support | 1.5/5 | 1.5/5 | 1.5/5 | 1.5/5 | 2/5 | 1.5/5 |
| European sovereignty | 3/5 | 3.5/5 | 3/5 | 3/5 | 3.5/5 | 3/5 |
| Pricing transparency | n/r | n/r | n/r | n/r | n/r | n/r |
| **Weighted verdict** | **2/5** | **2/5** | **2/5** | **2/5** | **2/5** | **2/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**
- Data request scope: no [S2]
- Employee access: yes [S2]
- EU access travel: yes [S2]
- Leadinfo tracking: Rotterdam · Leadinfo [S2]

**Data**
- Backup schedule: daily · Haarlem · Amsterdam · 7 [S2]
- Customer separation: yes [S2]
- Retention: no · yes [S2]
- Shared user database: yes · copernica.com · smtpeter.com · mailerq.com [S2]

**Hosting**
- Backup location: euNetworks datacenter, Amsterdam · True BV · yes [S2]
- Location: Netherlands · Copernica own · Leaseweb Netherlands BV · Iron Mountain, Haarlem [S2]

**Integrations**
- API: yes [S2]
- API tokens: Marketing Suite dashboard · OAuth handshake [S2]
- Google services: Google Analytics · Google Tag Manager · Google reCAPTCHA [S2]
- Meta: yes [S2]
- Openai email editor: yes [S2]
- Social login: LinkedIn · Facebook · Google [S2]

**Legal**
- Company address: De Ruijterkade 112, 1011 AB Amsterdam [S1]
- Entity: Copernica BV [S2]
- Language: Dutch [S2]

**Pricing**
- Trial: yes [S1]

**Product**
- Authentication: yes [S1]
- Console features: yes [S1]
- Feedback processing: yes [S1]
- Interference: yes [S1]
- Ip warmup: yes [S1]
- Mailerq type: MailerQ is an MTA application [S2]
- Management console: yes [S1]
- Newsletters: yes [S2]
- Notification channels: in-app · browser push · email [S2]
- Partner model: yes [S2]
- Real time monitoring: yes [S1]
- Take identity: yes [S2]
- Type: on-premise Mail Transfer Agent (MTA) for large email volumes [S1]
- Volume control: yes [S1]

**Subprocessors**
- 8x8: 8x8 · telephone system [S2]
- Pipedrive: Pipedrive · sales process [S2]
- Recruitee: Recruitee · applicant tracking · 180 [S2]
- Statuspage: statuspage.io · emergency status notifications [S2]
- Webinargeek: WebinarGeek · webinars [S2]

**Support**
- Experience years: 15 [S1]

## Questions

### Is MailerQ European?

Not determined: the vendor’s pages as captured do not say where MailerQ is based.

### Where does MailerQ store data?

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

### Does MailerQ have a free plan?

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

### What are the best alternatives to MailerQ?

As of 19 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 22 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, Netherlands). 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: [MailerQ alternatives](https://whats-best.ai/software/transactional-email/mailerq/alternatives).

## What this page leaves out

- 1 subprocessors 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.
- The panel’s written verdict is withheld: our own re-read found claims in it that the evidence does not carry, and a second synthesis did not fix them. The scores and the material below are unaffected.

## Sources

- [S1] Vendor page: https://www.mailerq.com (checked 2026-11-17)
- [S2] Privacy policy — found from the homepage: https://www.mailerq.com/privacy-policy (checked 2026-11-17)

---

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

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