whats-best.ai
Search Sign in

Transactional Email

Brevo Transactional Email

EU-Made Report an error

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 Brevo SAS · www.brevo.com

Compare with Mailjet Email API → Report an error on this page Is this your product? →

Link to this page

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

Brevo Transactional Email at a glance

Vendor
Brevo SAS
Headquarters
Not stated on the vendor’s pages as of 1 Nov 2026
Data hosting
Default not stated; pages mention France and Germany source, captured 1 Nov 2026
Free plan
Yes, per the vendor’s own page source, captured 1 Nov 2026
Starting price
“Starter Best for single users starting with email and multi-channel marketing. €7 -10% €6 .33 per month” (vendor’s words) source, captured 1 Nov 2026
Panel verdict
The AI panel rates Brevo Transactional Email 3/5, the mean of 6 judges. Brevo's transactional email service earns its best marks for its sending API, scored 7-8: a documented REST endpoint and SMTP relay, seven official SDKs, batch sending up to 1,000 emails per request, a sandbox mode, and idempotency keys with a 30-minute window. how scores are made
As of
Vendor pages captured 1 Nov 2026; evaluated by the panel 1 Nov 2026. all sources

Brevo Transactional Email alternatives, European ones first →

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

The Agency Lead

Weighted verdict

Technical lead at a web agency in Cologne that builds and runs thirty client applications, from a booking portal to a membership site, each sending its own mail from the client's domain. Wants one account with a sub-account, keys and limits per client, domains verified by API, roles so a client can see their own logs and nothing else, and a price per client that can be written into a maintenance contract.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Agency Lead

Panel median The Agency Lead This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The Agency Lead
Sending API, SMTP & developer experience 3.5 of 5 4 of 5
Deliverability & sender reputation 3 of 5 3.5 of 5
Message logs, events & webhooks 3 of 5 3.5 of 5
Message data, retention & security 3 of 5 3 of 5
Reliability, accounts & support 3 of 5 2.5 of 5
European sovereignty 3 of 5 3.5 of 5
Pricing transparency 2.5 of 5 2.5 of 5

Sending API, SMTP & developer experience

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 Agency Lead

A documented REST API and SMTP relay with official SDKs for all seven named languages, batch sending up to 1,000 messages per request, attachments, templates with variables and API template creation, idempotency keys, scheduled sending, a sandbox mode, inbound parsing, stated rate limits, and domain verification and validation by API — which is exactly how I would onboard thirty client domains. 1 4 11 12 14

Report an error

Deliverability & sender reputation

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 Agency Lead

SPF, DKIM and DMARC are set up through published DNS records with three verification routes, transactional and marketing mail are split by stream and IP, dedicated IPs come with automated warming on Professional and Enterprise, hard bounces and complaints are suppressed automatically, and a Deliverability Center shows a score with six months of history alongside published delivery-speed figures and access to deliverability specialists. We found no public information on feedback loops, blocklist monitoring, DMARC reports, custom return paths, or a stated position on the Gmail and Yahoo bulk-sender requirements. 1 3 11 13 14

Report an error

Message logs, events & webhooks

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 Agency Lead

Every message is searchable by message ID, recipient or subject with the technical history from API request to delivery, and the webhook payloads carry the full event set with bounce reasons, device and link fields plus a mirror link into the dashboard logs; webhooks can be created and updated via the API, with failure alerts and event export. The captured pages give different figures for log retention — the product pages describe indefinite transactional logs while the terms state deletion at least every 24 months — and we found no public information on webhook signatures and retry schedules, raw SMTP responses, read-only roles for support staff, or bounce and complaint spike alerts. 1 3 4 8 11 15 16

Report an error

Message data, retention & security

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 Agency Lead

ISO 27001:2022, multi-factor authentication and IP allow-listing down to CIDR ranges — with unknown IPs blocked even when the key is valid — sit beside per-message tracking-pixel removal, published and configurable retention periods, GDPR deletion tools and a data processing agreement. We found no public information on scoped API keys, an audit log, or an option to enforce TLS per domain, and the terms state Brevo may use content and usage data to enrich and train its AI features, which I would have to clear with clients before routing their transactional mail here. 1 4 7 8 10 17 18

Report an error

Reliability, accounts & support

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 Agency Lead

There is a public status page, a service level agreement appendix in the terms with 99.9% uptime, ten seats and phone support on Professional, backups across three geographically separate servers, and plugins for WordPress, Shopify, WooCommerce and Magento plus a Supabase integration. Sub-account management is an Enterprise feature at a custom price, which pushes my per-client separation out of any contract I could price on paper, and we found no public information on incident history, service credits, queueing during outages, granular roles, or per-plan response times. 1 3 8 11 19

Report an error

European sovereignty

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 Agency Lead

The contracting entity is Brevo SAS in Paris, data hosting is stated as France and Germany on EU-based servers with backups across three geographically separate servers, the data processing agreement is published as an appendix, subprocessors are listed in it, and ISO 27001:2022 is stated. The privacy policy itself says personal data may be transferred to the United States and India, the legal notice names hosts in California, and subprocessor locations along the sending chain are not shown on the captured pages — for my Cologne clients I would want that list before signing. 1 6 7 8 10 18

Report an error

Pricing transparency

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 Agency Lead

The free tier (300 emails per day, forever, no credit card) and paid tiers from €7 per month for 5,000 emails up to €499 per month for 150,000 are public, with a 10% yearly discount, pay-as-you-go credits that do not expire, and VAT treatment plus notice periods stated in the terms. The pieces I need to compute a per-client cost in a maintenance contract are the gaps: we found no public information on the price per additional thousand emails, a dedicated IP, longer log retention, SSO or sub-accounts, with Enterprise at a custom price. 1 3 5 8 11

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 ⚠ 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 Brevo Transactional Email

Is Brevo Transactional Email European?

Yes. whats-best.ai classifies Brevo Transactional Email as EU-Made.

Where does Brevo Transactional Email 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 France and Germany as hosting locations, per the vendor’s page captured 1 Nov 2026.

Does Brevo Transactional Email have a free plan?

Yes. Brevo Transactional Email has a free plan, per the vendor’s page captured 1 Nov 2026.

What are the best alternatives to Brevo Transactional Email?

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: Brevo Transactional Email 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.

Do you know more about Brevo Transactional Email? Tell us Report an error on this page

Sources (20)

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

  1. 1 Vendor homepage (transactional email) www.brevo.com Checked 1 Nov 2026 Details →
  2. 2 Features page (transactional email, German) www.brevo.com Checked 1 Nov 2026 Details →
  3. 3 Features page (SMTP relay) www.brevo.com Checked 1 Nov 2026 Details →
  4. 4 API documentation (transactional email) developers.brevo.com Checked 1 Nov 2026 Details →
  5. 5 Pricing page www.brevo.com Checked 1 Nov 2026 Details →
  6. 6 Legal notice www.brevo.com Checked 1 Nov 2026 Details →
  7. 7 Privacy policy www.brevo.com Checked 1 Nov 2026 Details →
  8. 8 Terms of service www.brevo.com Checked 1 Nov 2026 Details →
  9. 9 Security / trust page (GDPR) www.brevo.com Checked 1 Nov 2026 Details →
  10. 10 Security / trust page (data security) www.brevo.com Checked 1 Nov 2026 Details →
  11. 11 Sending API, SMTP & developer experience — found from sitemap www.brevo.com Checked 1 Nov 2026 Details →
  12. 12 Sending API, SMTP & developer experience — found from sitemap developers.brevo.com Checked 1 Nov 2026 Details →
  13. 13 Deliverability & sender reputation — found from sitemap www.brevo.com Checked 1 Nov 2026 Details →
  14. 14 Deliverability & sender reputation — found from sitemap developers.brevo.com Checked 1 Nov 2026 Details →
  15. 15 Message logs, events & webhooks — found from sitemap www.brevo.com Checked 1 Nov 2026 Details →
  16. 16 Message logs, events & webhooks — found from sitemap developers.brevo.com Checked 1 Nov 2026 Details →
  17. 17 Message data, retention & security — found from sitemap developers.brevo.com Checked 1 Nov 2026 Details →
  18. 18 Message data, retention & security — found from sitemap www.brevo.com Checked 1 Nov 2026 Details →
  19. 19 Reliability, accounts & support — found from sitemap www.brevo.com Checked 1 Nov 2026 Details →
  20. 20 Reliability, accounts & support — found from sitemap www.brevo.com Checked 1 Nov 2026 Details →