Transactional Email
MailerSend
Rest of world Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by MailerSend, Inc. · www.mailersend.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.
MailerSend at a glance
- Vendor
- MailerSend, Inc.
- Headquarters
- Not stated on the vendor’s pages as of 1 Nov 2026
- Data hosting
- Default not stated; pages mention Belgium source, captured 1 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 1 Nov 2026
- Starting price
- “upgrade for as little as $7 when you need more emails and features.” (vendor’s words) source, captured 1 Nov 2026
- Panel verdict
- The AI panel rates MailerSend 2.5/5, the mean of 6 judges. MailerSend's evidence is strongest for developers: sending API and observability scores cluster at 7, on seven official SDKs, a published OpenAPI spec, a CLI, an SMTP relay with documented limits, a searchable per-message log with HTML, plain-text and raw views, and signed webhooks retried twice on a published schedule. how scores are made
- As of
- Vendor pages captured 1 Nov 2026; evaluated by the panel 1 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
MailerSend's evidence is strongest for developers: sending API and observability scores cluster at 7, on seven official SDKs, a published OpenAPI spec, a CLI, an SMTP relay with documented limits, a searchable per-message log with HTML, plain-text and raw views, and signed webhooks retried twice on a published schedule. Pricing transparency clusters at 7, the shop operator's 6 reflecting an annual cost they cannot compute because the Starter overage rate and SSO pricing are not public; the captured pages give different figures for the entry price, "as little as $7" on the SMTP page against $6.30 on the pricing page. Deliverability, data and security, and reliability and accounts cluster at 6, held back by the SLA's exclusion of delivery time and deliverability rate from its credits. Sovereignty is weakest at 5, the skeptic at 6: storage runs on Google Cloud EMEA in Belgium with Standard Contractual Clauses and Data Privacy Framework certification, while the contracting entity is MailerSend, Inc. of New York under Delaware law and the DPA permits transfers "to the United States and anywhere else in the world".
Speaks for it
- Both sending paths are documented — a REST Email API with bulk sending and inbound routing, and an SMTP relay whose limits (five messages per connection, TLS on port 587 only) are spelled out.
- Every message is traceable in a searchable log with HTML, plain-text and raw views, a JSON download and CSV export.
- Webhooks for delivery, bounces, opens, clicks, complaints and reputation changes are signed with a per-account secret and retried twice on a documented 10- and 100-second schedule.
- Pricing is public to the tier, from a free 500 emails a month through Hobby at $6.30, Starter at $31.50 and Professional at $99.00, with overages of $1.50 and $1.30 per 1,000 emails and add-ons priced individually.
- Auto DNS set-up configures SPF, DKIM and DMARC, bounces and complaints are suppressed automatically, and a domain's sending is limited or paused when its bounce or complaint rate climbs.
Held against it
- The SLA's service credits exclude delivery time and deliverability rate, and we found no public information on delivery or inbox-placement figures.
- Dedicated IPs are available only to Enterprise accounts sending over 100K emails a week and are priced by contacting support.
- The DPA permits transfer and processing of customer data "to the United States and anywhere else in the world", and we found no public information on subprocessor locations.
- The privacy policy reserves a right to monitor emails, content and response data for terms compliance, and message content is retained in activity data with no metadata-only option evidenced.
- The captured pages give different figures for the entry price — "as little as $7" on the SMTP page against $6.30 on the pricing page.
Best for
- You need transactional email wired into an application quickly, with SDKs in seven languages, an OpenAPI spec, and a 14-day Professional trial with a sandbox domain and no credit card.
- Your on-call or support staff must answer whether a specific message was delivered, using the searchable log, per-message views and signed webhooks.
- You want the year's cost visible before signup — published tiers, overage rates, add-on prices, VAT treatment and a 10% yearly discount.
- You run several brands or clients as domains and sender identities in one account, shaping access with the five user types and a custom role.
Avoid if
- You need more than EU storage — the contracting entity is MailerSend, Inc. of New York under Delaware law and the DPA permits transfer and processing of customer data "to the United States and anywhere else in the world".
- You require a committed delivery time or deliverability rate — the SLA's service credits exclude both, and dedicated IPs are Enterprise-only.
- You object to a provider reserving a right to monitor email content for terms compliance, or need message content kept out of retained activity data.
- Your use case sits on the ineligible list — high-risk financial services, gambling, cryptocurrency, firearms, pornography, affiliate marketing and weight-loss material are named as ineligible.
The scores
| Criterion | Panel median |
|---|---|
| Sending API, SMTP & developer experience | 3.5 of 5 |
| Deliverability & sender reputation | 3 of 5 |
| Message logs, events & webhooks | 3.5 of 5 |
| Message data, retention & security | 3 of 5 |
| Reliability, accounts & support | 3 of 5 |
| European sovereignty | 2.5 of 5 |
| Pricing transparency | 3.5 of 5 |
Sending API, SMTP & developer experience
panel disagrees
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
Sending mail is genuinely easy here: a REST API and an SMTP relay with their limits documented (five messages per SMTP connection, TLS on port 587 only, IP-based rate limits lower than the API), seven official SDKs including a vendor-maintained Laravel package, stored templates with personalisation variables, a bulk endpoint, inbound routing, an OpenAPI collection, a CLI, and a sandbox mode with its own domain for testing. We found no public information on idempotency keys, template versioning or a migration guide from named competitors, and the SMTP relay explicitly supports neither templates nor advanced personalisation. 2 5 6 7 13 14 21
The Platform Engineer
A RESTful API and an SMTP relay are both documented with real limits — the SMTP pages state a five-transaction connection limit, TLS-only on port 587, per-IP rate limits lower than the API, and dropped custom headers — and seven official SDKs, an OpenAPI collection, a CI-friendly CLI and a sandbox-domain trial give my team a genuine integration path. The docs are candid that templates and advanced personalization are API-only, so SMTP stays a legacy fallback for us. We found no public information on idempotency keys, template versioning, or a migration guide from named competitors. 2 6 7 13 14
The Shop Operator
Both sending paths are documented — a RESTful Email API with a bulk endpoint, and an SMTP relay whose limits are spelled out (5 messages per connection, TLS-only port 587, IP-based rate limits lower than the API, templates and advanced personalization API-only) — alongside official SDKs for PHP, Laravel, Node.js, Python, Go, Ruby and Java, an OpenAPI collection on SwaggerHub, a CLI, inbound routing and a sandbox trial with a sandbox domain and no credit card. As a PHP shop that is exactly the shape I need; we found no public information on idempotency keys, template versioning or migration guides from named competitors, which keeps this a step below the top level. 2 6 13 14
The Data Protection Officer
The developer story is well documented: a RESTful API with a published OpenAPI specification on SwaggerHub, an official CLI, and official SDKs for PHP, Laravel, Node.js, Python, Go, Ruby and Java; SMTP relay limits are unusually explicit (five messages per connection, IP-based rate limits below the API's, TLS on port 587 only, custom headers dropped), inbound routing delivers parsed mail to webhooks, and a sandbox domain with a 14-day Professional trial needs no credit card. We found no public information on idempotency keys, template versioning or migration guides from named competitors. 2 6 13 14
The Agency Lead
Seven official SDKs covering PHP, Laravel, Node.js, Python, Ruby, Java and Go, an OpenAPI collection on SwaggerHub, a CI-friendly CLI and a documented SMTP relay with its limits (5 messages per connection, TLS on port 587, rate limits per IP) cover exactly how my thirty client apps would send. Templates with personalisation variables, a bulk-email endpoint, scheduled sending, a sandbox trial domain and inbound routing with custom headers are all documented. We found no public information on idempotency keys, template versioning or a.NET SDK, and the SMTP relay explicitly drops custom headers and advanced personalisation that the API supports. 6 14 2 13 7
The Skeptic
A REST API with a published OpenAPI spec on SwaggerHub, official SDKs for PHP, Laravel, Node, Python, Ruby, Java and Go, a CLI, inbound routing, and an SMTP relay whose limits are unusually well documented — five transactions per connection, IP-based rate limits, custom headers dropped, TLS on port 587 only, with templates and advanced personalization reserved for the API rather than SMTP. Daily API request quotas per plan are stated. We found no public information on idempotency keys, template versioning or a migration guide from named competitors, so I stop short of the top band. 2 6 13 14
Deliverability & sender reputation
panel disagrees
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
Auto DNS set-up for SPF, DKIM and DMARC, instant suppressions for bounces, unsubscribes and spam complaints, blocklist and DMARC monitors per plan, per-domain reputation statuses with webhooks and automatic pausing when bounce or complaint rates climb, and deliverability consultation on the higher plans cover most of what keeps my password resets landing. We found no public information on shared-pool vetting, dedicated-IP warm-up (dedicated IPs are Enterprise-only, priced by contacting support), separation of transactional and marketing streams, feedback loops, Gmail and Yahoo sender rules, or published delivery times — and the SLA explicitly excludes delivery time and deliverability rate from its credits. 2 4 7 12 15 16
The Platform Engineer
Auto-DNS configuration of SPF, DKIM and DMARC, automatic suppressions from bounces and complaints, DMARC and blocklist monitoring by plan, per-domain reputation with pausing, and deliverability consultation on the upper tiers cover what my one-time-code traffic needs day to day. What I cannot put in front of my on-call rota is a number: we found no public information on delivery times or inbox placement, and the SLA explicitly excludes both the deliverability rate and the delivery time from the service credit commitment. We also found no public information on dedicated-IP warm-up, shared-pool vetting, feedback loops or a custom tracking domain, and dedicated IPs are restricted to Enterprise accounts at a contact-support price. 2 4 7 12 15 16
The Shop Operator
Auto DNS configuration that detects the provider and automatically sets SPF, DKIM and DMARC records is exactly the guided set-up a non-specialist on my team can follow, bounces, unsubscribes and spam complaints are instantly suppressed, DMARC and blocklist monitoring come with the plans, and per-domain reputation is watched with pausing and a support review when bounce rates climb. Dedicated IPs exist only for Enterprise accounts sending over 100,000 emails a week — far above my roughly 12,000 order mails a month — and we found no public information on IP warm-up, shared-pool vetting, Gmail/Yahoo bulk-sender compliance or published delivery times. 2 3 4 7 16
The Data Protection Officer
Authentication set-up is guided with automatic DNS for SPF, DKIM and DMARC, bounces, unsubscribes and complaints go onto the suppressions list automatically, DMARC and blocklist monitoring ship by plan, per-domain reputation statuses with pause-on-high-bounce behaviour are visible, and expert consultation is included on Professional plans. We found no public information on dedicated-IP warm-up, shared-pool vetting, feedback loops or stated compliance with the Gmail and Yahoo sender requirements; dedicated IPs are Enterprise-only and quoted by contacting support, and the SLA explicitly excludes deliverability rate and delivery time. 2 4 7 15 16
The Agency Lead
Auto DNS configures SPF, DKIM and DMARC, bounces, unsubscribes and spam complaints land on the suppressions list automatically, and DMARC plus blocklist monitoring are built in, with per-domain reputation from the Starter plan that limits or pauses sending domain by domain. Deliverability consultation and a team with 13 years of experience are on record, but dedicated IPs exist only for Enterprise accounts over 100K emails/week and are priced on request. We found no public information on IP warm-up, shared-pool vetting, feedback loops, Gmail and Yahoo bulk-sender compliance or published delivery times, which the SLA explicitly excludes from its commitment. 2 4 7 16 12 15
The Skeptic
Auto DNS set-up for SPF, DKIM and DMARC, automatic suppressions on bounces, complaints and unsubscribes, DMARC and blocklist monitoring tiered by plan, and a per-domain reputation system that limits or pauses a domain when bounce or complaint rates climb. Dedicated IPs exist but only for Enterprise accounts sending over 100K emails a week with pricing by support contact, and we found no public information on shared-pool vetting, IP warm-up, feedback loops, stream separation between transactional and bulk mail, or Gmail and Yahoo bulk-sender compliance. No delivery times or inbox placement figures with a method are published anywhere in what I read. 2 4 7 15 16
Message logs, events & webhooks
panel disagrees
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 question I actually ask — did this user get the reset mail — is answerable from the captured pages: the email log is searchable by recipient, subject, tag and message ID, per-message statuses and interactions are recorded, each message is viewable as HTML, plain text and raw, activity exports to CSV, and webhooks for delivery, soft and hard bounces, opens, clicks and spam complaints are signed with a unique secret key and retried twice on a documented schedule with a three-second timeout. Activity retention is seven days on Starter and thirty on Professional with a paid extension to 365 days; we found no public information on native alerts for bounce or complaint spikes, or on streaming events to a log platform. 3 5 7 17 18
The Platform Engineer
The Emails page is what I need at 3am: searchable by recipient, subject, tag and message ID, with queued, sent, delivered and rejected statuses, per-message HTML, plain text and raw views, a full JSON download, and CSV export. Webhooks are signed with a secret key, retried twice at documented delays, testable in the app, and cover delivery, soft and hard bounce, open, click, complaint and reputation changes, so my own alerting can react to bounce spikes. Retention is the weak point — activity data runs one to thirty days by plan with an extension to 365 days from $5.00 — and we found no public information on streaming events to an external log tool. 1 4 7 17 18 21
The Shop Operator
Every message lands in the activity log with search by recipient, subject, tag or message ID, queued-to-delivered statuses, HTML, plain-text and raw views, a JSON download and CSV export, and retention is stated per plan (1 to 30 days) and extendable to 365 days for an extra fee. Webhooks cover delivery, soft and hard bounces, opens, clicks, complaints and reputation changes, are signed, retried twice on a documented schedule with a seven-day attempt history and a test button, and the five user types include a custom role I could shape for a support colleague who should see mail but touch nothing else. 5 7 17 18 21
The Data Protection Officer
Every message is traceable: the Emails page is searchable by recipient, subject, message ID, template ID and tag with statuses through queued, sent, delivered and rejected, the HTML, plain-text and raw message are viewable, and the full JSON of a message can be downloaded; webhooks cover delivery, soft and hard bounce, open, click, unsubscribe and complaint, are signed with a per-account secret, and retries follow a published schedule of ten and one hundred seconds. Retention is stated per plan (one to thirty days of activity, seven days of API logs) and extendable to 365 days from $5.00. We found no public information on configurable bounce or complaint alerts, streaming to external log tools beyond CSV export, or a read-only seat for support staff. 5 7 17 18
The Agency Lead
The Emails page logs every send with search by recipient, subject, tag or message ID, statuses from queued to delivered plus opens, clicks and complaints, and HTML, plain-text and raw views per message with a downloadable JSON. Webhooks are signed with a unique secret key, retried on a documented schedule (10 and 100 seconds), testable, and viewable with seven days of attempts, covering delivery, bounces, opens, clicks, complaints and reputation changes. Retention is stated per plan and extendable to 365 days as a paid add-on, and custom user roles can be limited to activity and analytics; we found no public information on automatic bounce or complaint alerts or on streaming events to a named log tool. 18 17 5 7 21
The Skeptic
A searchable per-message log by subject, recipient, message ID, template ID or tag, with queued-sent-delivered-rejected statuses, HTML, plain-text and raw message views, recipient profiles with full history, CSV export, and webhooks that are signed, retried twice on a documented 10-second and 100-second schedule with a three-second timeout and a seven-day attempt log. Retention is stated honestly — one to thirty days by plan, extendable to 365 — but we found no public information on bounce-spike alerts, streaming events to a log tool, or a genuine read-only role for support staff; the closest is a designer restricted to templates. 5 7 17 18
Message data, retention & security
panel disagrees
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
Encryption at rest (AES256) and in transit, a TLS-only SMTP relay on port 587, IP allow-listing, two-factor authentication with recovery codes and bulk enforcement, SSO, five user types with granular permissions, open and click tracking behind a domain setting, per-recipient deletion with GDPR tools for data subject requests, plus a DPA and ISO 27001 on the storage centre. We found no public information on scoped API keys, an audit log, a vulnerability disclosure programme, or any way to retain no message content — activity retention simply follows the plan. 1 7 10 13 18 20 21
The Platform Engineer
Encryption at rest and in transit are stated, SMTP is TLS-only on port 587, and IP allow-listing, two-factor authentication with bulk enforcement, five granular user roles, SSO in the team features, a DPA folded into the terms, and ISO 27001 scoped to the EU data storage centre give me a defensible baseline. I fall short of comfortable on the API side: we found no public information on API token scopes or rotation, audit logs, or a vulnerability disclosure programme, while the terms reserve use of email routing data for the vendor's business purposes. Recipient deletion from the activity view and GDPR request tooling are documented, and opens tracking is switchable at the domain level. 1 8 10 13 18 19 20
The Shop Operator
Encryption at rest and in transit with AES256, TLS-only SMTP on port 587, two-factor authentication with bulk enforcement and recovery codes, IP allow-listing, five user types plus SSO, a DPA that is automatically agreed with the terms, and an ISO 27001-certified storage center give me most of the controls a shop like mine needs. The privacy policy's inactive-account terms show message content itself is retained, and we found no public information on shortening content retention, scoped API keys, a dashboard audit log or a vulnerability disclosure programme. 1 9 10 13 19 20 21
The Data Protection Officer
The DPA names the customer controller and MailerSend processor, data is mirrored in two EU locations with AES-256 at rest and TLS in transit, two-factor authentication with single-use recovery codes, IP allow-listing and per-domain open and click tracking switches exist, recipients can be deleted from the activity view, and the vendor assists with data-subject requests and DPIAs with breach notice within 48 hours. Two things give me pause for mail carrying patient names: the privacy policy reserves a right to monitor emails, content and response data for terms compliance (with AI and manual content checks), and message content sits in activity data whose retention extends up to 365 days rather than down to none. We found no public information on an audit log, scoped API keys, or an ISO 27001 or SOC 2 certificate covering MailerSend itself rather than its hosting provider. 7 9 10 18 19 20
The Agency Lead
Two-factor authentication with recovery codes, IP allow-listing, AES-256 encryption at rest, TLS and an automatic DPA are documented, recipients can be deleted from the activity view, and personal data is deleted within 30 days of a request. What is kept is listed — templates, activity records, suppressions, recipient addresses and message content — with retention stated per plan, and open tracking is switched in the domain settings. We found no public information on scoped API tokens, an audit log or a vulnerability disclosure programme, the ISO 27001 certificate is stated for the Google storage center rather than the vendor itself, and the vendor reserves the right to monitor email content for terms compliance. 9 18 19 20 10 11 1
The Skeptic
AES-256 at rest, TLS-only SMTP on port 587, IP allow-listing, two-factor authentication with recovery codes and bulk enforcement, granular custom roles, deletion of personal data within thirty days on request, and recipient deletion straight from the log view. But the ISO 27001 certificate belongs to Google's storage centre rather than to MailerSend's own operation — the DPA's own phrase is audit reports 'if any' — and we found no public information on scoped API tokens, an audit log, a vulnerability disclosure programme, or SSO beyond one homepage mention. Message content is retained by default for as long as the business needs it, with no metadata-only option evidenced. 9 10 13 19 20
Reliability, accounts & support
panel disagrees
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
There is a published SLA with tiered service credits for both API and SMTP uptime, 24/7 support with per-plan channels, granular roles, a sandbox environment, and a WordPress plugin plus guides for Supabase, Laravel and Symfony. We found no public information on incident history or post-mortems, queueing of mail during outages, or per-plan response times; redundancy is documented only as data mirrored in two locations, creating multiple accounts is forbidden, and client separation runs through domains and sender identities — a help page on creating sub-accounts is among the captured pages, but we found no confirmed details from it. 1 3 5 7 8 9 12 19 21 22
The Platform Engineer
The SLA is in writing with my name on it: 99.5% monthly uptime with tiered service credits of 5, 10 and 15 percent, a defined five-minute availability calculation, maintenance notice windows, and separate SMTP uptime tiers — though the credit commitment explicitly excludes delivery time, which is exactly the metric my one-time-code flow lives or dies by. Roles are granular across five user types with unlimited seats on Professional, a sandbox trial gives a staging environment, 24/7 support is claimed, and WordPress, Laravel, Symfony, Supabase and Firebase connectors cover the platforms I inherit. We found no public information on queueing and retry of mail during incidents, on status-page incident history, or on per-plan support response times. 3 5 7 9 12 19 21
The Shop Operator
A 99.5% uptime SLA with published service-credit tiers of 5 to 15 percent, defined maintenance-notice windows, data mirrored in two locations, 24/7 support with live chat on higher plans, five user roles including an accountant, and plugins or guides for WordPress, Laravel, Symfony, Supabase, Firebase and Zapier, plus a help page on creating sub-accounts, cover most of running this as a team. 1 3 5 8 12 19 21 22
The Data Protection Officer
The SLA commits to 99.5% monthly uptime for API and SMTP with service credits of 5, 10 and 15 percent, data is mirrored across two locations, five user types including a granular custom role and an accountant-only seat are supported, support is 24/7 by email with live chat on higher plans, and plugins or connectors exist for WordPress, Supabase, Laravel, Symfony and Firebase. A help-centre guide covers creating sub-accounts, but we found no public information on multi-year uptime history with post-mortems, mail queueing and retry behaviour during incidents, or support response times per plan. 3 5 12 19 21 22
The Agency Lead
A 99.5% uptime SLA with 5-15% service credits, 24/7 support, five user types with custom granular permissions and connectors for WordPress, Laravel, Symfony and Supabase give me a workable base, and the Professional plan positions itself for agencies with unlimited seats and domains plus per-domain reputation. Data is mirrored in two locations, but we found no public information on mail queueing during incidents, published incident history, response-time commitments per plan or migration help. Beyond a captured help page about creating sub-accounts, we found no public information on sub-accounts with their own keys, domains and limits manageable by API — the documented model is multiple clients via domains and sender identities in a single account, with up to 5 SMTP users per domain. 12 21 7 5 3 1 19 9 22
The Skeptic
A 99.5 percent uptime SLA with service credits of 5, 10 and 15 percent — a credit that explicitly excludes delivery time and deliverability rate — plus data mirrored in two locations, five user types with per-area permissions, 24/7 support, and plugins or guides for WordPress, Supabase, Laravel, Symfony, Firebase, Zapier and Slack. A status page exists since incident.io sends its notifications, but we found no public information on incident history, support response times per plan, or what happens to queued mail during an outage. Multiple accounts are forbidden and the captured facts describe multi-client management by domain rather than any sub-account mechanism. 5 7 12 21
European sovereignty
panel opinion
panel disagrees
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
Data storage is documented as EU — a Google Cloud EMEA centre in Belgium — with MailerLite Limited of Dublin as the EU GDPR representative, a DPA folded into the terms of use with Standard Contractual Clauses, and a subprocessor list in the DPA annex naming Stripe, PayPal, Braintree, Meta, Bandwidth, PostHog and others. The contracting entity is MailerSend, Inc. of New York under Delaware law, and the DPA permits processing customer data in the United States and anywhere else in the world where subprocessors operate; subprocessor locations are not published. 8 9 10 11
The Platform Engineer
The captured pages put message and account data on Google infrastructure in Belgium with mirroring in two locations, backed by Standard Contractual Clauses, a UK Addendum, Data Privacy Framework certification and an EU representative in Dublin as safeguards. The contracting entity is MailerSend, Inc. of New York under Delaware law, and the DPA permits transfers to the United States and anywhere else in the world where it or its subprocessors operate — for a German fintech that means a DPIA conversation before customer one-time codes flow through it. Subprocessors including Stripe, Braintree, Bandwidth, Meta and PostHog are named with a list in DPA Annex 4, but we found no public information on their processing locations. 9 10 11 19
The Shop Operator
The contracting entity is MailerSend, Inc. of New York under Delaware law, with MailerLite Limited in Dublin as GDPR representative, while the vendor states its data storage centers are in the European Union (Google Cloud EMEA, Belgium), the DPA is part of the terms with SCCs and Data Privacy Framework certification, and subprocessors are listed in DPA Annex 4 and named in the privacy policy. The DPA still allows transfer and processing 'to the United States and anywhere else in the world', the named subprocessors (Stripe, PayPal, Bandwidth, Meta, PostHog and others) come without stated locations, and we found no public information on where the sending infrastructure or the logs actually run. 8 9 10 11 19
The Data Protection Officer
The contracting party is MailerSend, Inc. of New York under Delaware law with the US Federal Trade Commission as regulator, and MailerLite Limited in Dublin serves only as GDPR representative; hosting is named as Google Cloud EMEA in Belgium, and the DPA — integral to the terms of use — lists sub-processors in Annex 4, applies standard contractual clauses and claims Data Privacy Framework certification. However, the DPA permits transfers of customer data "to the United States and anywhere else in the world", named sub-processors such as Meta, Bandwidth, PostHog, Stripe and PayPal are disclosed without their locations, and the ISO 27001 certificates cited cover the storage centres rather than MailerSend. For a health sender this is workable but not sovereign: EU storage with an EU representative, an American contracting entity, and a transfer clause that reaches worldwide. 8 9 10 11 19
The Agency Lead
The contracting entity is MailerSend, Inc. of New York under Delaware law, with MailerLite Limited in Dublin as EU GDPR representative, and storage runs on Google Cloud EMEA in Belgium with data mirrored in two locations. A published DPA applies automatically with Standard Contractual Clauses, a UK Addendum and Data Privacy Framework certification, and subprocessors are named — Google, Stripe, PayPal, Braintree, Bandwidth, Meta, PostHog and others — in Annex 4 of the DPA. The DPA nevertheless permits transfer and processing of customer data in the United States and anywhere in the world, and we found no public information on where the sending infrastructure itself runs. 10 11 19 9
The Skeptic
The contracting entity is MailerSend, Inc. of New York under Delaware law and FTC authority, with EU data storage on Google Cloud EMEA in Belgium, mirroring in two unnamed locations, an Irish GDPR representative (MailerLite Limited, Dublin), a published DPA with Standard Contractual Clauses and Data Privacy Framework certification, and subprocessors disclosed in DPA Annex 4. The same DPA permits transfer and processing of customer data 'anywhere else in the world', payment runs through Stripe, PayPal and Braintree and SMS through Bandwidth, and we found no public information on where the sending infrastructure itself runs. The EU claim covers storage; the whole chain is not evidenced as European. 9 10 11 19
Pricing transparency
panel disagrees
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
Tiers, volumes and overage rates are public — $6.30 for Hobby at 5,000 emails a month, $31.50 for Starter and $99 for Professional at 50,000, extra usage at $1.50 and $1.30 per thousand emails, a free tier of 500 emails a month, activity retention per plan with a paid extension to 365 days from $5.00, DMARC monitors at $2 per domain and domain spaces at $4 — plus VAT treatment, monthly or yearly terms with a 10% yearly discount and cancellation without penalty. Dedicated IPs are "Contact our support team", we found no public information on the Starter plan's overage rate or SSO pricing, and the captured pages give different figures for the entry price — "as little as $7" on the SMTP page against $6.30 on the pricing page. 3 7 8
The Platform Engineer
I can almost compute my annual bill from the pricing page alone: Hobby at $6.30 per month for 5,000 emails, Starter at $31.50, Professional at $99.00, each with a stated overage per 1,000 emails, per-plan log retention, priced add-ons for extra domains, DMARC monitors and retention extension, VAT treatment, three currencies and a 10% yearly discount. The gap is the dedicated IP, which is priced only on contacting support and restricted to Enterprise accounts sending over 100K emails a week. Cancellation is without penalty, refunds only if the vendor terminates without cause, and fees may be changed at the vendor's discretion. 1 7 8
The Shop Operator
Tiers, volumes and overage rates are public — Free with 500 emails a month, Hobby $6.30 with 5,000 emails and $1.50 per extra thousand, Starter $31.50 and Professional $99.00 with 50,000 emails and $1.30 per extra thousand — plus priced add-ons (DMARC monitor $2.00 per domain, domain space $4.00, activity retention up to 365 days from $5.00), a stated 10% yearly discount, VAT treatment and penalty-free cancellation. Dedicated IPs are 'Contact our support team', and we found no public information on the Starter overage rate, SSO or support-plan pricing, so I cannot compute a complete annual cost from public pages alone. 7 8
The Data Protection Officer
Hobby at $6.30, Starter at $31.50 and Professional at $99.00 per month each publish volume, overage ($1.50 or $1.30 per 1,000 emails), activity-retention days and seat counts; add-ons carry exact prices (DMARC monitor $2.00 per domain, domain space $4.00, phone number $2.00, extended retention from $5.00), a free tier of 500 emails a month exists, and VAT treatment with exemption conditions plus monthly and yearly billing are stated. Dedicated IPs are Enterprise-only and priced by contacting support, and we found no public information on SSO or support-plan pricing or whether unused volume carries over. 7 8
The Agency Lead
Every tier is public with its volume and price — Free with 500 emails/month, Hobby at $6.30 per month for 5,000, Starter and Professional at 50,000 emails for $31.50 and $99.00 monthly with 10% off yearly billing — and overage rates are quoted for Hobby ($1.50 per 1,000 emails) and Professional ($1.30 per 1,000 emails). Add-ons carry numbers: DMARC monitors at $2.00 per domain, domain spaces at $4.00, activity retention extension from $5.00, and VAT treatment, billing periods, refunds and cancellation terms are all stated, so I can compute a per-client maintenance price. Dedicated IPs are 'Contact our support team', and we found no public information on Starter overage, SSO pricing or whether unused volume carries over. 7 8 1
The Skeptic
A free tier of 500 emails a month, Hobby at $6.30, Starter at $31.50 and Professional at $99.00 monthly with per-thousand overages of $1.50 and $1.30 published, retention stated per plan, add-ons priced in dollars (domain space $4.00, DMARC monitor $2.00, retention extension from $5.00), VAT treatment stated, a 10 percent yearly discount and a fourteen-day trial that does not auto-subscribe. Dedicated IPs are 'contact our support team', we found no public information on support-plan or SSO pricing, and the terms reserve the right to modify fees 'at any time' — a buyer can nearly compute the year, but not quite. 1 7 8
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined ⚠ unverified | — | 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 ⚠ unverified | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about MailerSend
Is MailerSend European?
No. whats-best.ai classifies MailerSend as Rest of world.
Where does MailerSend 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 Belgium as hosting location, per the vendor’s page captured 1 Nov 2026.
Does MailerSend have a free plan?
Yes. MailerSend has a free plan, per the vendor’s page captured 1 Nov 2026.
What are the best alternatives to MailerSend?
As of 2 Nov 2026, the panel rates Lettermint (3.5/5), Bird Email API (formerly SparkPost) (3/5) and Postmark (3/5) 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 (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: MailerSend alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 1 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement, Hosting location. Not confirmed on the vendor’s own pages as captured.
- 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.
- 28 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. Know more? Tell us
- 24 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. Know more? Tell us
- 8 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. Know more? Tell us
- 2 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. Know more? Tell us
- 1 hosting 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
- 1 integrations 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
- 1 legal 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
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
- 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. Know more? Tell us
Sources (23)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.mailersend.com Checked 1 Nov 2026 Details →
- 2 Features page (email API) www.mailersend.com Checked 1 Nov 2026 Details →
- 3 Features page (SMTP relay) www.mailersend.com Checked 1 Nov 2026 Details →
- 4 Features page (deliverability) www.mailersend.com Checked 1 Nov 2026 Details →
- 5 Features page (webhooks) www.mailersend.com Checked 1 Nov 2026 Details →
- 6 API documentation developers.mailersend.com Checked 1 Nov 2026 Details →
- 7 Pricing page www.mailersend.com Checked 1 Nov 2026 Details →
- 8 Terms of service www.mailersend.com Checked 1 Nov 2026 Details →
- 9 Privacy policy www.mailersend.com Checked 1 Nov 2026 Details →
- 10 Data processing agreement (dpa) www.mailersend.com Checked 1 Nov 2026 Details →
- 11 Security / trust page (GDPR) www.mailersend.com Checked 1 Nov 2026 Details →
- 12 Service level agreement www.mailersend.com Checked 1 Nov 2026 Details →
- 13 Sending API, SMTP & developer experience — found from sitemap developers.mailersend.com Checked 1 Nov 2026 Details →
- 14 Sending API, SMTP & developer experience — found from sitemap developers.mailersend.com Checked 1 Nov 2026 Details →
- 15 Deliverability & sender reputation — found from sitemap www.mailersend.com Checked 1 Nov 2026 Details →
- 16 Deliverability & sender reputation — found from sitemap www.mailersend.com Checked 1 Nov 2026 Details →
- 17 Message logs, events & webhooks — found from sitemap www.mailersend.com Checked 1 Nov 2026 Details →
- 18 Message logs, events & webhooks — found from sitemap www.mailersend.com Checked 1 Nov 2026 Details →
- 19 Message data, retention & security — found from sitemap www.mailersend.com Checked 1 Nov 2026 Details →
- 20 Message data, retention & security — found from sitemap www.mailersend.com Checked 1 Nov 2026 Details →
- 21 Reliability, accounts & support — found from sitemap www.mailersend.com Checked 1 Nov 2026 Details →
- 22 Reliability, accounts & support — found from sitemap www.mailersend.com Checked 1 Nov 2026 Details →
- 23 Code repository (open-source licence) — found from the homepage github.com Checked 1 Nov 2026 Details →