Mandrill
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Mailchimp (The Rocket Science Group, part of Intuit) · mandrill.com
Report an error on this page Is this your product? →
Link to this page
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.
Mandrill at a glance
- Vendor
- Mailchimp (The Rocket Science Group, part of Intuit)
- Headquarters
- Not stated on the vendor’s pages as of 11 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 11 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 11 Nov 2026
- Panel verdict
- The AI panel rates Mandrill 1.5/5, the mean of 6 judges. Mandrill, renamed Mailchimp Transactional and run by Mailchimp (The Rocket Science Group, part of Intuit), earns its highest marks for pricing transparency: tiers are public, from a Free plan at €0 with a 250-contact limit, Essentials from €11.73 per month and Standard from €18.05 per month after a fourteen-day trial, to a transactional add-on at 20 USD per block of 25,000 emails up to 20 blocks. how scores are made
- As of
- Vendor pages captured 11 Nov 2026; evaluated by the panel 11 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Mandrill, renamed Mailchimp Transactional and run by Mailchimp (The Rocket Science Group, part of Intuit), earns its highest marks for pricing transparency: tiers are public, from a Free plan at €0 with a 250-contact limit, Essentials from €11.73 per month and Standard from €18.05 per month after a fourteen-day trial, to a transactional add-on at 20 USD per block of 25,000 emails up to 20 blocks. Sending API (4) and reliability and accounts (4) follow, covering a transactional API, SMTP integration, a delivery and monitoring API, inbound email, multi-domain sending, per-plan support channels and a stated 99.99% uptime. Weakest is sovereignty: we found no public information on where messages and recipient data are processed, on an EU region, on subprocessors or on a data processing agreement, and two judges recorded the criterion as not rated for lack of public information. Data and security and observability (3) sit low, with only a GDPR compliance link and API-key access visible, and deliverability credits published figures (99% average delivery, 2.69% average bounce) while noting no stated method behind them.
Speaks for it
- Sending API scores sit at 4 throughout, covering a transactional API, an SMTP integration, a delivery and monitoring API, inbound email handling and multi-domain sending from one account.
- Pricing transparency scores 4–5, with a Free plan at €0 and a 250-contact limit, Essentials from €11.73 per month, Standard from €18.05 per month after a fourteen-day trial, and 20 USD per 25,000-email block up to 20 blocks.
- Support channels are published per plan, from email for the first 30 days on Free to phone and priority support on Premium, alongside a stated 99.99% uptime for transactional email.
- New users can send up to 500 free test emails to their own verified domain.
- The vendor publishes aggregate delivery figures: a 99% average delivery rate, a 2.69% average bounce rate since 2018 and median delivery under one second.
Held against it
- Sovereignty scores 0–2, and we found no public information on where messages, logs and recipient data are processed, on an EU region, on subprocessors or on a data processing agreement.
- Data and security scores 2–3, with only a GDPR compliance link and API-key access visible and no public information on storage, retention, encryption, two-factor authentication or certifications.
- Observability sits at 3, with no public information on a searchable per-message log, event webhooks or log retention periods.
- Deliverability rests on aggregate figures published without a stated method, and we found no public information on SPF, DKIM or DMARC guidance, dedicated IPs or automatic suppressions.
- Overage fees are named without a rate and the Premium plan price is not stated, so a full annual cost cannot be computed from public pages.
Best for
- You already pay for a Mailchimp Legacy, Standard or Premium plan and want transactional email added at publicly priced blocks.
- You send from multiple domains and subdomains and one account is enough.
- You need inbound email handling alongside transactional sending.
- Your procurement starts from published tier prices and a 15% discount from 10,000 contacts.
Avoid if
- You must document the processing chain before signing, covering residency, subprocessors and a data processing agreement; sovereignty scored 0–2 on the record.
- You run client accounts and need per-client isolation; multi-domain sending from a single account is not sub-account separation.
- Your support team must answer whether a specific message arrived without opening a ticket; we found no public information on per-message logs or webhooks.
- You need a contractual SLA with service credits or a status page with incident history rather than a stated 99.99% uptime.
The scores
| Criterion | Panel median |
|---|---|
| Sending API, SMTP & developer experience | 2 of 5 |
| Deliverability & sender reputation | 1.5 of 5 |
| Message logs, events & webhooks | 1.5 of 5 |
| Message data, retention & security | 1 of 5 |
| Reliability, accounts & support | 2 of 5 |
| European sovereignty | 1 of 5 |
| Pricing transparency | 2.5 of 5 |
Sending API, SMTP & developer experience
Show reasoningHide 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.
The SaaS Developer
The captured page documents a transactional API, an SMTP integration and a delivery and monitoring API, plus inbound email management, multi-domain sending and Mailchimp template import. What I need day to day is thin: the capture names no SDK or framework driver for PHP or Laravel, states no rate limits, and the 500 free test emails go to my own verified domain rather than a sandbox that never delivers; templates appear only as an import, with variables and versions unmentioned. 1
The Platform Engineer
The captured pages show an application can send through a transactional API, an SMTP integration, and a delivery/monitoring API, with inbound email handling and template import from Mailchimp alongside multi-domain sending. We found no public information on official SDKs for named languages, rate limits, a sandbox or test mode, attachments or batch sending, so the developer experience stays just above the basic level. 1
The Shop Operator
The captured page documents sending through a transactional API and an SMTP integration, plus a delivery/monitoring API, inbound email handling, and template import from Mailchimp. We found no public information on SDKs for named languages, rate limits, attachments, batch sending or a sandbox mode, so my developer would be building against the API with the basics only. 1
The Data Protection Officer
Sending works through a transactional API and an SMTP integration, with a separate delivery and monitoring API, inbound email handling, and template import from Mailchimp described. We found no public information on official SDKs for named languages, rate limits, attachments, batch sending or a sandbox mode, so the documented developer experience stays basic. 1
The Agency Lead
The captured page confirms a transactional API, an SMTP integration and a separate delivery and monitoring API, plus inbound email handling, template import from Mailchimp and sending from multiple domains and subdomains on one account. Beyond 500 free test emails to your own verified domain for new users, we found no public information on official SDKs, rate limits, attachments, batch sending, scheduled sending or a sandbox mode. For thirty client codebases that leaves the integration work and the risk squarely with my developers. 1
The Skeptic
A transactional API, an SMTP integration and a delivery-monitoring API are on record, inbound email is offered, and new accounts get up to 500 free test emails to their own verified domain. We found no public information on official SDKs for named languages, rate limits, batch sending, attachments or a template language, so the API surface is announced rather than documented on the captured page. 1
Deliverability & sender reputation
Show reasoningHide 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.
The SaaS Developer
A set-up flow covers generating an API key, registering a sender domain and configuring DNS, and the vendor publishes platform-wide figures — 99 percent average delivery, a 2.69 percent average bounce rate and median delivery under a second — without a stated measurement method. Dedicated IPs with warm-up, shared-pool vetting, automatic suppressions and DMARC guidance are not described in the capture. 1
The Platform Engineer
A set-up flow for an API key, sender domain and DNS is described, and aggregate figures are published: an average delivery rate of 99%, an average bounce rate of 2.69%, and a median delivery speed under 1 second. We found no public information on guided SPF, DKIM and DMARC set-up, dedicated IPs or pool vetting, automatic suppressions, or how transactional and bulk mail are separated, and the delivery figures are aggregates without a method or per-mailbox-provider breakdown. 1
The Shop Operator
Set-up is described only as generating an API key, naming a sender domain and configuring your DNS — no guided SPF, DKIM or DMARC flow that a non-specialist on my team could follow. The page publishes a 99% average delivery rate and a 2.69% average bounce rate since 2018, but we found no public information on IP pools, dedicated IPs, automatic suppressions, or how transactional mail is kept separate from the newsletter stream. 1
The Data Protection Officer
The set-up flow covers an API key, a sender domain and DNS configuration, and the vendor publishes an average delivery rate of 99%, an average bounce rate of 2.69% and a median delivery speed of under one second. We found no public information on DMARC guidance, return-path or tracking domains, shared or dedicated IP pools, automatic suppressions, or compliance with the Gmail and Yahoo bulk-sender rules. 1
The Agency Lead
The page documents a set-up flow that issues an API key and configures the DNS of your sender domain, and publishes aggregate figures — a 99% average delivery rate, a 2.69% average bounce rate since 2018, and a median delivery speed under one second — without stating the method. We found no public information on SPF, DKIM and DMARC guidance, dedicated or shared IP policy, automatic suppressions, or compliance with the Gmail and Yahoo bulk-sender rules. Before I route a client's booking confirmations and password resets through it, that is the gap I would need closed. 1
The Skeptic
The vendor publishes aggregate figures — 99 % average delivery rate, a 2.69 % bounce rate across 300 billion emails since 2018, median delivery under a second — and the captured page gives no method behind them; set-up includes a DNS-configuration step. We found no public information on SPF, DKIM or DMARC guidance, dedicated or shared IP policy, automatic suppressions, or the Gmail and Yahoo bulk-sender rules. 1
Message logs, events & webhooks
Show reasoningHide 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.
The SaaS Developer
The capture names a delivery and monitoring API for overseeing sends and publishes aggregate delivery and bounce rates, but nothing describes a per-message log searchable by recipient, webhook events and signatures, retention or dashboards per tag or domain. From these pages alone I cannot tell whether "did this user get the reset mail" is answerable without opening a ticket. 1
The Platform Engineer
A delivery/monitoring API is described for watching and managing your sends, plus aggregate delivery and bounce statistics, which is enough to see totals. We found no public information on a searchable per-message log with the receiving server's answer, event webhooks and their retry schedule, log retention, or alerts on bounce spikes — the visibility I would need during an incident is not described on these pages. 1
The Shop Operator
The page names a delivery API for monitoring and managing sends and publishes aggregate figures such as the 2.69% average bounce rate and median delivery speed under 1 second. We found no public information on a searchable per-message log, per-message events with the receiving server's answer, webhooks, or how long messages and events are kept. 1
The Data Protection Officer
A delivery and monitoring API is described for watching and managing sendings, alongside published aggregate figures for delivered and bounced messages. We found no public information on a searchable per-message log, the full event history including the remote server's answer, event webhooks, or how long logs and message content are kept. 1
The Agency Lead
The delivery and monitoring API that lets you watch and manage your sends is the only per-message visibility the captured page shows, alongside the aggregate bounce and delivery figures. We found no public information on a searchable message log, event history, webhooks, retention periods, or read-only access for a client's own staff. My whole agency model rests on each client seeing their mail and only their mail, and nothing here evidences that. 1
The Skeptic
A delivery API for monitoring and managing sends is described, and an average bounce rate is cited, but we found no public information on a searchable per-message log, the full event history, event webhooks, dashboards per domain or tag, or how long messages and logs are kept. 1
Message data, retention & security
Show reasoningHide 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.
The SaaS Developer
The only security-related item on the captured page is a footer link to GDPR compliance. What is stored per message, retention periods, encryption, tracking toggles, API key scopes, two-factor authentication and certifications are not described there, so the documented level stays at the basic end. 1
The Platform Engineer
The pages describe access via generated API keys and link a GDPR compliance page, which places the documented posture at a basic level. We found no public information on what is stored per message, retention periods and how to shorten them, switching off open and click tracking, scoped or rotatable keys, IP allow-listing, two-factor authentication or SSO, an audit log, or certifications and their scope. 1
The Shop Operator
A GDPR compliance page is linked in the footer and set-up involves generating an API key, but we found no public information on what is stored per message, retention periods, encryption, two-factor authentication or key scopes. When a bounce lands in my support inbox with a customer's invoice attached, I would not know from this page what the provider keeps or for how long. 1
The Data Protection Officer
The page links a GDPR compliance page and access runs through API keys; beyond that I could verify nothing on data handling. We found no public information on whether message bodies are stored and for how long, whether open and click tracking can be switched off, TLS enforcement, encryption at rest, two-factor authentication or certifications — the section I read first when reminders carry patient names. 1
The Agency Lead
What the page shows on this front is a GDPR compliance link in the footer and an API key issued during set-up. We found no public information on what is stored per message, retention settings, open and click tracking toggles, TLS, key scopes, two-factor authentication, audit logs or certifications. I could not draft the security annex of a client contract from this. 1
The Skeptic
A GDPR-compliance page is linked in the footer and set-up begins by generating an API key, and that is the whole security story on the captured page. We found no public information on what is stored per message, retention periods and how to shorten them, encryption, API-key scopes, two-factor authentication, or certifications and audits with their scope. 1
Reliability, accounts & support
Show reasoningHide 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.
The SaaS Developer
Support channels are described per plan — email for the first 30 days on Free, email and chat anytime on Standard and Essentials, phone and priority support on Premium — and a 99.99 percent uptime figure is stated for transactional email. A public status page with incident history, an SLA with credits, sub-accounts, team roles and integrations with platforms like WordPress or Shopify are not described in the capture. 1
The Platform Engineer
A 99.99% uptime figure for transactional email is stated, and support channels are published per plan, from email support for the first 30 days on Free to email and chat on Essentials and Standard and phone and priority support on Premium. We found no public information on a public status page with incident history, an SLA with service credits, queueing and retry of mail during outages, or sub-accounts and team roles — the stated uptime is a claim, not a contractual SLA. 1
The Shop Operator
Support channels per plan are documented — email and chat for Standard and Essentials, phone and priority support for Premium, and email support for only the first 30 days on the Free plan — alongside a stated uptime of 99.99% and sending from multiple domains in one account. We found no public information on a status page with incident history, an SLA with credits, sub-accounts, team roles, or a plugin for Shopware or other shop platforms. 1
The Data Protection Officer
Support differs by plan — email and chat anytime on Standard and Essentials, phone and priority support on Premium, and thirty days of email support on the Free plan — and a 99.99% uptime figure is stated for transactional email. We found no public information on a public status page with incident history, an SLA with service credits, queueing during outages, sub-accounts or team roles. 1
The Agency Lead
Support is described per plan — email and chat anytime on Standard and Essentials, phone and priority support on Premium, and email for the first 30 days on Free — and a 99.99% uptime figure is stated for transactional email. We found no public information on a public status page with incident history, an SLA with service credits, or sub-accounts with their own keys, domains and limits. Multi-domain sending from a single account is not per-client isolation, and for us that is the deciding question. 1
The Skeptic
Support channels differ by plan — email for the first 30 days on Free, anytime email and chat on Standard and Essentials, phone and priority support on Premium — and a 99.99 % uptime figure is stated, though as a claim rather than an SLA with service credits. We found no public information on a public status page with incident history, sub-accounts, team roles, or plugins for platforms like WordPress or Shopify. 1
European sovereignty
panel opinion
n/r
n/r
Show reasoningHide 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.
The SaaS Developer not rated — no public information
We found no public information on where messages, logs and recipient data are processed or stored, whether an EU region can be chosen, or which subprocessors run the sending chain; the sovereignty dimensions are recorded as unknown, and the GDPR compliance link states no locations or processors. I read the vendor page captured from mandrill.com and no other pages. 1
The Platform Engineer
The trademark owner is The Rocket Science Group, part of Intuit, and a GDPR compliance page is linked in the footer. We found no public information on where messages, logs and account data are processed or stored, on an EU region, on a data processing agreement, or on the subprocessors in the sending chain, so no European placement can be confirmed from these pages. 1
The Shop Operator
The page names The Rocket Science Group as the trademark owner and links a GDPR compliance page, but we found no public information on where messages, logs and recipient data are processed, on an EU region, or on the subprocessors in the sending chain. For my German and Austrian shops that leaves the data-residency and contracting-entity questions essentially open. 1
The Data Protection Officer not rated — no public information
We found no public information on the contracting entity's seat, where messages, logs and recipient data are processed or stored, an EU region and what it covers, or the subprocessors in the sending chain. A footer link to a GDPR compliance page is the only European reference on the captured page, and it says nothing about the processing chain. 1
The Agency Lead
The trademark owner named is The Rocket Science Group, part of Intuit, and a GDPR compliance page is linked in the footer; we found no public information on where messages, logs and recipient data are processed, on an EU region, on the subprocessors, or on a data processing agreement. With no part of the sending chain located anywhere on the record, I cannot put this in front of a German client's data protection review. 1
The Skeptic
The only facts that bear here are the corporate chain — Mandrill renamed to Mailchimp Transactional, trademark held by The Rocket Science Group, part of Intuit — and a linked GDPR-compliance page. We found no public information on where messages, logs and recipient data are processed and stored, an EU region, the subprocessors in the sending chain, or a data processing agreement. 1
Pricing transparency
Show reasoningHide 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.
The SaaS Developer
Transactional sending is priced in blocks on top of a paid Mailchimp plan: prices start at 20 USD per block of 25,000 emails, up to 20 blocks for 500,000 emails per month, as an add-on on Legacy, Standard and Premium only, with 500 free test emails for new users. The underlying plans are public — Free at €0 with a 250-contact limit, Essentials from €11.73 per month, Standard from €18.05 per month, and a 15 percent discount from 10,000 contacts — but overage fees are only mentioned and not priced, and dedicated IPs, log retention, SSO and support plans carry no price, so a full annual cost cannot be derived from these pages alone. 1
The Platform Engineer
Tiers and volumes are public: the Free plan at €0 with a 250-contact limit, Essentials at €11.73/month and Standard at €18.05/month after a 14-day trial, 15% discount from 10,000 contacts, and the transactional add-on priced at $20 per block of 25,000 emails up to 20 blocks with 500 free test emails. We found no public information on the overage rate beyond "overage fees apply", dedicated IPs, the Premium plan price, minimum term or VAT treatment, so the real annual cost is not computable from these pages alone. 1
The Shop Operator
Tiers are public — a Free plan at € 0 with a 250-contact limit, Essentials from €11.73/Monat, Standard from €18.05/Monat — and transactional sending is priced in blocks from 20 USD per 25,000 emails up to 20 blocks, available only as an add-on to paid plans. The overage rate, dedicated IP price, log-retention add-ons, minimum term and VAT treatment are not stated on the captured page, so I cannot compute my full annual cost for roughly 900 orders a week from this page alone. 1
The Data Protection Officer
Tier prices are public — €0 on the Free plan with a 250-contact limit, Essentials from €11.73 a month and Standard from €18.05 a month after a fourteen-day trial — and the transactional add-on costs 20 USD per block of 25,000 emails, up to twenty blocks, with 500 free test emails for new users. Overage fees are named without a rate, SMS credits are monthly and expire unused, and we found no public information on dedicated IP, longer log retention, SSO or support-plan pricing, so a full annual cost cannot be computed from public pages. 1
The Agency Lead
Tiers and the transactional add-on are priced publicly: Free at €0/Monat with a 250-contact limit, Essentials ab €11.73/Monat and Standard ab €18.05/Monat after a 14-day trial, the add-on starting at 20 USD pro Block covering 25.000 E-Mails up to 20 Blocks, a 15% discount from 10.000 Kontakten, and SMS credits that expire monthly and cannot be carried over. We found no public information on overage rates per thousand messages, dedicated IPs, log retention per plan, VAT treatment or any per-sub-account pricing. That blocks me from computing a fixed per-client line for a maintenance contract. 1
The Skeptic
The transactional add-on is priced in blocks — starting at 20 USD per block of 25,000 emails, up to 20 blocks or 500,000 emails per month, alongside a Free plan at € 0 with 250 contacts, Essentials from €11.73/month and Standard from €18.05/month. Overage fees are mentioned but not priced, tier volumes above Free are not shown, and we found no public information on what dedicated IPs, longer log retention or other add-ons cost, so a real annual figure cannot be computed from the page alone. 1
Questions about Mandrill
Is Mandrill European?
Not determined: the vendor’s pages as captured do not say where Mandrill is based.
Where does Mandrill store data?
Not stated on the vendor’s pages as of 11 Nov 2026.
Does Mandrill have a free plan?
Not stated on the vendor’s pages as of 11 Nov 2026.
What are the best alternatives to Mandrill?
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: Mandrill alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 11 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
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.
- 1 pricing 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. Know more? Tell us
Sources (1)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page mandrill.com Checked 11 Nov 2026 Details →