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 MailerQ (Copernica, Netherlands) · www.mailerq.com

Report an error on this page Is this your product? →

Link to this page

MailerQ: AI-assisted analysis on whats-best.ai MailerQ: 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.

MailerQ 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 source, captured 17 Nov 2026
Free plan
Not stated on the vendor’s pages as of 17 Nov 2026
Panel verdict
The AI panel rates MailerQ 2/5, the mean of 6 judges. how scores are made
As of
Vendor pages captured 17 Nov 2026; evaluated by the panel 18 Nov 2026. all sources

MailerQ alternatives, European ones first →

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

No written verdict for this product

The panel scored MailerQ, but the summary our synthesizer wrote did not survive our own contradiction check — twice. Rather than print a paragraph we cannot stand behind, we print none. Every score, rationale and source below is unaffected; read them and draw the conclusion yourself.

Know this product well? Tell us what the verdict should say

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.

Sending API, SMTP & developer experience

Show reasoning
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 SaaS Developer

MailerQ is an on-premise mail transfer agent with a REST API and management console, so mail can be sent through it, but I found no public information on SDKs, an official Laravel or PHP driver, stored templates with variables, a sandbox mode, batch sending or rate limits. For my stack this reads as infrastructure to operate, not a documented API to integrate in an afternoon. 1 2

Report an error

The Platform Engineer

An application can hand mail to MailerQ as a self-hosted mail transfer agent with a REST API and management console, and tokens are fetched via OAuth. But we found no public information on SDKs for named languages, stored templates, rate limits, a test or sandbox mode, inbound parsing, scheduled sending or idempotency handling — I'd be wiring my one-time-code path into it sight-unseen on the developer ergonomics. 1 2

Report an error

The Shop Operator

MailerQ is documented as an on-premise mail transfer agent that comes with a REST API and a management console, so an application can in principle hand mail to it. But we found no public information on SDKs for PHP or other languages, stored templates, rate limits or a test mode — and nothing on a Shopware plugin, which is how my shop would actually connect. 1 2

Report an error

The Data Protection Officer

MailerQ is documented as a high-performance on-premise mail transfer agent that ships with a management console and a REST API, and Copernica states it offers APIs to link its software to other applications. We found no public information on SDKs, stored templates, rate limits, a test mode or inbound parsing, so the documented level is a basic sending path only. 1 2

Report an error

The Agency Lead

MailerQ is an on-premise MTA with a REST API and a management console, so applications can hand mail to it, but the captured pages describe no SDKs for PHP, Node or the other stacks we run, no stored templates, no batch or scheduled sending, and no stated limits or test mode. For our client stack this reads as bare SMTP-in, API-managed sending with the developer ergonomics undocumented. 1 2

Report an error

The Skeptic

MailerQ is an on-premise mail transfer agent that ships with a management console and REST API, so an application can hand mail to it. But the captured pages stop there: we found no public information on SDKs for named languages, stored templates, rate limits, a sandbox mode, attachments handling or inbound parsing — "intuitive Management Console, REST API, and other functionality" is the whole developer story I was given. 1 2

Report an error

Deliverability & sender reputation

Show reasoning
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 SaaS Developer

Authentication is genuinely covered — DKIM, SPF, DMARC, TLS and even ARC — plus warm-up throttle schedules, bounce classification via response patterns and feedback loop processing, with monitoring per IP and target. I found no public information on automatic suppressions, separate streams for transactional versus bulk mail, or compliance with the Gmail and Yahoo sender rules. 1

Report an error

The Platform Engineer

Authentication is solid on paper — DKIM, SPF, DMARC, TLS and even ARC are supported, bounces are classified through configurable response patterns, feedback loops can be processed, and IP warm-up trajectories are a first-class throttle-schedule feature. We found no public information on guided set-up, pool vetting, automatic suppressions, or stated compliance with the Gmail and Yahoo bulk-sender rules, so inbox reach cannot be verified from these pages. 1

Report an error

The Shop Operator

The pages show DKIM, SPF, DMARC, TLS and ARC support, bounce classification and feedback loop processing, plus throttle schedules for IP warm-up and per-inbox-provider volume control — solid engine-level tooling. What I personally need is absent from the evidence: we found no public information on a guided SPF and DKIM set-up a non-specialist can follow, automatic suppressions, or keeping order mail and newsletters on separate streams. 1

Report an error

The Data Protection Officer

DKIM, SPF, DMARC, TLS and even ARC are supported, response patterns classify bounces and process feedback loops, and throttle schedules define warm-up trajectories — more than bare authentication. We found no public information on sender vetting, suppression policies, custom return paths, or the separation of transactional and marketing streams, which keeps this below the guided set-up level. 1

Report an error

The Agency Lead

The tooling is genuinely there: DKIM, SPF, DMARC and ARC support, response patterns to classify bounces and process feedback loops, throttle schedules for IP warm-up, and volume control per inbox provider, which as an operator I can work with. I found no public information on automatic suppressions, shared-pool vetting, Gmail and Yahoo sender-rule compliance or published delivery times, so I cannot go higher. 1

Report an error

The Skeptic

DKIM, SPF, DMARC and even ARC are stated as supported, response patterns classify bounces and process feedback loops, and throttle schedules define IP warm-up trajectories with sending speeds set per inbox provider. That is a real toolkit. But we found no public information on custom return paths, automatic suppression of hard bounces and complaints, blocklist or DMARC monitoring, or any statement on the Gmail and Yahoo sender requirements — and delivery performance is shown to the customer, never published with a method. 1

Report an error

Message logs, events & webhooks

Show reasoning
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 SaaS Developer

Real-time insights into delivery attempts, queues, error logs and results per IP, target, customer and message type go well beyond sent-and-bounced totals. But I found no public information on webhooks (signed or otherwise), a searchable per-recipient message log, an events API or log retention — so the question 'did this user get the reset mail?' stays unanswered on the captured pages. 1

Report an error

The Platform Engineer

The console gives real-time insight into delivery attempts, results, queues and error logs per IP, target, customer, campaign and message type, and you can pause deliveries or throw errors per target — genuine MTA-level visibility. We found no public information on event webhooks, an events API, log retention, bounce-spike alerts or read-only roles for support staff, which is the tooling I need at three in the morning. 1

Report an error

The Shop Operator

The management console promises real-time insight into delivery attempts, queues and error logs per MTA, IP, target, customer, campaign and message type, and lets me pause deliveries or throw errors for specific targets — more than bare totals. We found no public information on searchable per-message history, event webhooks, or how long logs are kept. 1

Report an error

The Data Protection Officer

The console gives real-time insight into delivery attempts, results, queues and error logs per IP, target, customer, campaign or message type, and SMTP connections can be monitored while deliveries are paused or rerouted. We found no public information on event webhooks, an events API, or how long logs and message content are kept, which limits what a team can audit after handing a message over. 1

Report an error

The Agency Lead

Real-time insight into delivery attempts, results, queues and error logs per IP, target, customer, campaign or message type is exactly the per-client view my team would want, and deliveries can be paused per target or message type. Event webhooks, log retention and an events API are not described on the captured pages, which caps this for a support workflow. 1 2

Report an error

The Skeptic

Real-time insight into delivery attempts and results, queues, and error logs per IP, target, customer, campaign or message type is documented — that is more than sent-and-bounced totals. But we found no public information on webhooks with retries, an events API, alerts on bounce or complaint spikes, or how long logs are kept; retention silence is exactly how a day-eight discovery happens. 1

Report an error

Message data, retention & security

Show reasoning
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 SaaS Developer

The privacy policy documents case-by-case deletion, daily backups kept a maximum of seven days across Haarlem and Amsterdam, strict separation of customer data and access restricted to employees on Dutch contracts; TLS is supported for delivery. I found no public information on encryption at rest, two-factor authentication, API key scopes, audit logs or security certifications. 1 2

Report an error

The Platform Engineer

TLS is supported for delivery, and the privacy policy documents strict separation of customer data, access limited to employees on Dutch contracts with confidentiality clauses, daily backups kept up to seven days in Haarlem and Amsterdam, and case-by-case deletion. We found no public information on two-factor authentication, key scopes and rotation, IP allow-listing, encryption at rest, an audit log or certifications — and retention cannot be set by the customer to a fixed period. 1 2

Report an error

The Shop Operator

The privacy policy states customer data is strictly separated and never used for Copernica's own purposes, backups run daily and are kept at most seven days, and only employees under Dutch contracts with a confidentiality clause may access data — though data requests cover only Copernica's own records, not what I store. Beyond TLS for delivery we found no public information on encryption at rest, two-factor authentication, scoped API keys, or security certifications. 2 1

Report an error

The Data Protection Officer

The privacy policy is concrete on points I read first: backups run daily and are kept at most seven days across Haarlem and Amsterdam, customer data is strictly separated and never used for Copernica's own purposes, only employees on Dutch contracts with confidentiality clauses can access it, and TLS is part of the authentication stack. But retention is explicitly case-by-case — the policy states a period cannot be specified beforehand — and we found no public information on a data processing agreement, encryption at rest, two-factor authentication, tracking controls or certifications. 2 1

Report an error

The Agency Lead

The privacy policy describes case-by-case deletion, daily backups kept at most seven days in two Dutch locations, strict separation of customer data, and access limited to staff on Dutch employment contracts with confidentiality clauses, while the product supports TLS. What is stored per message, encryption at rest, two-factor authentication and a data processing agreement are not shown, so the controls I would need to write into client contracts are not visible. 2 1

Report an error

The Skeptic

The privacy policy documents employee access rules (Dutch-law employment contracts with confidentiality clauses, plus a "take identity" feature for staff), strict separation of customer data from the vendor's own, daily backups kept at most seven days in Haarlem and Amsterdam, and TLS among the supported protocols. But we found no public information on encryption at rest, what is stored per message, two-factor authentication, scoped API keys, an audit log or any certification — and retention is "deleted on a case-by-case basis" with no stated period, a phrase I have learned not to enjoy. Data requests also explicitly do not cover information customers store themselves. 2 1

Report an error

Reliability, accounts & support

Show reasoning
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 SaaS Developer

There is a support contact and a partner model with over fifteen years of experience, and statuspage.io is used for emergency notifications when the vendor's own servers are down. I found no public information on an uptime SLA, incident history, sub-accounts, team roles or plugins for platforms like WordPress or Shopify. 1 2

Report an error

The Platform Engineer

Support runs through a partner model with email contact, a free trial, and an emergency notification service for when the vendor's own servers are unavailable; as an on-premise product the sending path's uptime also depends on my own deployment. We found no public information on an uptime SLA with credits, published incident history, sub-accounts with their own keys, team roles or support response times — the first thing I read before any feature list is absent here. 1 2

Report an error

The Shop Operator

There is a contact e-mail, a partner model under which affiliated companies provide services and support, and the claim of a dedicated partner with over 15 years of experience. We found no public information on a public status page with incident history, an SLA, sub-accounts, team roles, or guides and plugins for shop systems like mine. 1 2

Report an error

The Data Protection Officer

Support exists as a contact address, a dedicated partner with over fifteen years of experience, and a partner model for affiliated companies, with emergencies notified through statuspage.io. We found no public information on a public status page with incident history, an uptime SLA, sub-accounts, team roles or response times per plan. 1 2

Report an error

The Agency Lead

There is a support route through a partner model with a dedicated partner of over fifteen years' experience, emergency notifications via a status page service, and API tokens that can reach other accounts through an OAuth handshake. An uptime SLA, incident history, granular roles and per-client sub-account management are not described, which matters since I would run thirty client streams through it. 1 2

Report an error

The Skeptic

There is a contact email, a partner model in which affiliated companies offer services and support, and a statuspage.io subscription the vendor uses for emergency notifications when its own servers are unavailable. We found no public information on a public status page with incident history, an uptime SLA with service credits, support response times per plan, sub-accounts with roles and their own keys, or guides for platforms like WordPress or Shopify. 1 2

Report an error

European sovereignty panel opinion

Show reasoning
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 SaaS Developer

Copernica BV is a Dutch contracting entity in Amsterdam, servers sit in the Iron Mountain data centre in Haarlem on Copernica's own hardware and Leaseweb's, backups go to Amsterdam, and the policy states data entered is only stored in the Netherlands — with a DPO contact published. That falls short of full marks because I found no public information on a published data processing agreement or certifications, and most of the listed subprocessors come without their locations. 1 2

Report an error

The Platform Engineer

Everything Copernica stores sits in the Netherlands — primary servers on Copernica's own hardware and Leaseweb's in the Iron Mountain data center in Haarlem, backups via True BV in Amsterdam — under a Dutch contracting entity with a named Data Protection Officer and the Dutch contract version leading. Subprocessors are listed with their purposes (8x8, Pipedrive, Recruitee, statuspage.io, WebinarGeek, Leadinfo in Rotterdam), but most locations are unstated, and we found no public information on a published data processing agreement or security certifications. 1 2

Report an error

The Shop Operator

The contracting entity is Copernica BV in Amsterdam; its own servers and Leaseweb's sit in the Iron Mountain data center in Haarlem, backups are stored in Amsterdam, and the policy states entered data is only stored in the Netherlands, with a Data Protection Officer reachable by e-mail and access limited to staff under Dutch employment contracts. Subprocessors such as 8x8, Pipedrive, Recruitee, statuspage.io and WebinarGeek are named, but we found no public information on their locations, a published data processing agreement, or ISO 27001/SOC 2 certifications — that last point matters to me under GDPR. 2

Report an error

The Data Protection Officer

Copernica BV is the contracting entity at an Amsterdam address, servers are its own or Leaseweb's in the Iron Mountain datacenter in Haarlem, backups sit with True BV in the euNetworks datacenter in Amsterdam, and the policy states that data entered is only stored in the Netherlands, with the Dutch version of the policy leading. Subprocessors and tooling are listed by name and purpose — 8x8, Pipedrive, Recruitee, statuspage.io, WebinarGeek, Leadinfo, plus Google and Meta services around the website — but locations are given only for Leadinfo, and we found no public information on a published data processing agreement or security certifications, which is what I would need before signing. 2 1

Report an error

The Agency Lead

Copernica BV contracts from the Netherlands, runs its servers at Iron Mountain in Haarlem and Leaseweb Netherlands, keeps backups in Haarlem and Amsterdam, states data is only stored in the Netherlands, and names subprocessors including 8x8, Pipedrive, statuspage.io and Leadinfo in Rotterdam. A published data processing agreement and security certifications do not appear, and most subprocessor locations are unstated, so the evidence stops below the strongest case; since the sending software runs on our own infrastructure, part of the chain is ours to control anyway. 2 1

Report an error

The Skeptic

The contracting entity is Copernica BV at an Amsterdam address, its servers run in the Netherlands on named providers (Leaseweb in the Iron Mountain data center in Haarlem, backups with True BV in the euNetworks data center), and the policy states that data entered by you is only stored in the Netherlands, with a DPO reachable by email and the Dutch version of the policy leading. Subprocessors are named — 8x8, Pipedrive, Recruitee, statuspage.io, WebinarGeek, Leadinfo in Rotterdam, plus Google and Meta services — but almost none with a stated location, and we found no public information on a published data processing agreement or security certifications. Since MailerQ itself is an on-premise application, these commitments describe the vendor's own systems; where your messages travel is on infrastructure you run. 1 2

Report an error

Pricing transparency not rated — the vendor publishes no price

Show reasoning
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 SaaS Developer

The only public pricing information is a 'try out for free' trial; I found no public information on licence tiers, per-volume pricing, add-ons, minimum term or VAT treatment. A buyer cannot compute any annual cost from the captured pages. 1

Report an error

The Platform Engineer

The only public pricing signal is a free trial. We found no public information on tier prices, per-message or per-volume rates, add-on costs such as support or extra capacity, minimum term or VAT treatment, so a buyer cannot compute a real annual cost from what is published. 1

Report an error

The Shop Operator

The only pricing statement we found is 'Try out for free'. We found no public information on tier prices, per-message rates, minimum terms or add-on costs, so I cannot work out what a year of mail for my 900 orders a week would cost. 1

Report an error

The Data Protection Officer

The only public pricing fact is a free trial, quoted exactly as "Try out for free". We found no public information on tier prices, per-message or overage rates, add-ons, minimum terms or VAT treatment; the partner model points to reseller involvement, but no prices appear on the captured pages. 1 2

Report an error

The Agency Lead

Only a free trial is public — no tiers with monthly volumes, no per-thousand overage rates, no dedicated-IP, retention or support-plan prices — so I cannot compute a per-client cost to write into a maintenance contract from the captured pages. 1

Report an error

The Skeptic

The only pricing fact the pages yield is "Try out for free" — a trial, not a price. No tiers, license fees, volume rates, minimum term or cancellation terms appear anywhere, so an annual cost cannot be computed from public pages; we found no public information on what the software or its support costs. 1

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 — 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 — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about MailerQ

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.

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), Bird Email API (formerly SparkPost) (3/5) and Postmark (3/5) 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 (EU-Made, Netherlands). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: MailerQ 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.

Sources (2)

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

  1. 1 Vendor page www.mailerq.com Checked 17 Nov 2026 Details →
  2. 2 Privacy policy — found from the homepage www.mailerq.com Checked 17 Nov 2026 Details →