Brevo
Brevo is EU-hosted marketing platform with a competent transactional API attached. We compare it in Email APIs. It is top of its roster on Event webhooks (delivered, opened, clicked, bounced, complained, deferred, unsubscribed, inbound). The trade-off is being 12th of 13 on Shared pool quality (2).
What is Brevo?
Brevo — EU-hosted marketing platform with a competent transactional API attached. Brevo, formerly Sendinblue, is a French CRM and marketing suite that also includes a solid transactional email API and SMTP relay. Everything is hosted in the EU, which makes it one of the shorter answers to a GDPR question. The developer experience is clearly secondary to the marketing product, and new accounts routinely go through manual validation before sending is enabled. Built by Brevo (ex-Sendinblue). Founded 2012. Series B+.
We track it in 1 comparison — Email APIs — so every claim below is a cell in a table you can open and check rather than an impression. Across those rosters it sits against 12 other tools, and what follows is where it visibly separates from them.
Where it wins.
- Event webhooks — delivered, opened, clicked, bounced, complained, deferred, unsubscribed, inbound, tied for best across 5 of 13 tools.
- Free tier — 9,000 emails/mo, the best figure of the 10 here.
Each of those is ranked against the whole roster on its category page, not against a hand-picked subset, so a first place here means first of everything we list.
Where it gives ground.
- Shared pool quality — 2, 12th of 13. Postmark records 5.
- Price / 1k emails — $1.8 /1k, the weakest of the 11 here. Amazon SES records $0.1 /1k.
- Data residency — eu, 9th of 12. Amazon SES records us, eu, au, apac, sa, ca.
None of these disqualify it on their own. They are the fields to check against your own requirements before you commit, because they are the ones where a competitor genuinely does better.
Provenance. 23 of 25 tracked fields carry a value for Brevo, and 0 of those cite a document you can open. Nothing here carries a verification date yet, which is itself a reason to check before committing. Every figure keeps its own provenance — measured by us, claimed by the vendor, inferred, or community-reported — and we would rather print a dash than a guess.
Its nearest neighbour in our data is AhaSend. Brevo is ahead on Hosted templates (visual-editor against none) and Free tier (9,000 emails/mo against 1,000 emails/mo). AhaSend takes llms.txt docs (Yes against No) and GA year (2023 against 2012). That pattern repeats across the rest of the roster — see Brevo alternatives for the other rivals, each compared the same way.
At a glance
- Company
- Brevo (ex-Sendinblue)
- Founded
- 2012
- Funding
- Series B+
- Fields we track
- 23 of 25
Brevo in Email APIs
Ranked against 13 tools across 25 sourced fields. Open the full Email APIs table.Buy it for the EU hosting and the marketing suite, not for the transactional API. The free tier is the largest here and the shared pool reflects exactly that. Manual account validation makes it a poor choice if you need to be live today.
Where it lands in this roster
- Time to first send
- 240 min8th of 13 Community-reported
- Event webhooks
- deliveredopenedclickedbounced+41st of 13 Inferred
- Price / 1k emails
- $1.8 /1k11th of 11 Inferred
- Free tier
- 9,000 emails/mo1st of 10 Inferred
- Data residency
- eu9th of 12 Inferred
- Log retention
- 43200 min2nd of 9 Inferred
- Inbound parsing
- Yes1st of 12 Inferred
When to use Brevo
Brevo is the right call in these situations, each one drawn from a field we actually record:
- EU-only data residency without self-hosting.
- One vendor covering CRM, marketing and transactional.
- High free-tier volume during prototyping.
- Event webhooks is your binding constraint. Brevo records delivered, opened, clicked, bounced, complained, deferred, unsubscribed, inbound, the best figure in the Email APIs roster. We define that field as which message events the provider will POST to your endpoint.
- Free tier is your binding constraint. Brevo records 9,000 emails/mo, the best figure in the Email APIs roster. We define that field as emails per month on a permanently free plan.
When not to use Brevo
Reach for something else when any of the following is a requirement rather than a nice-to-have:
- Shared pool quality. Brevo records 2, 12th of 13 in the Email APIs roster. Postmark records 5 on the same field. If that is a hard requirement rather than a preference, start elsewhere.
- Price / 1k emails. Brevo records $1.8 /1k, the weakest of the 11 tools in the Email APIs roster. Amazon SES records $0.1 /1k on the same field. If that is a hard requirement rather than a preference, start elsewhere.
- Data residency. Brevo records eu, 9th of 12 in the Email APIs roster. Amazon SES records us, eu, au, apac, sa, ca on the same field. If that is a hard requirement rather than a preference, start elsewhere.
We publish this block because a comparison that only lists what a tool is good at is marketing. Every figure above sits on the same page as its source, and the field definitions are on the category tables if you want to check how we measured them.
Tools compared alongside Brevo
Everything below shares at least one comparison category with Brevo, ordered by how much overlap there is. For the reasoning on each — which fields it wins, which it loses — see Brevo alternatives.Recent Brevo changes
We have not logged a dated change for Brevo yet. The timeline fills in as pricing moves, features ship and things get deprecated.Sources and gaps
What we don't know. 2 of the 25 fields we track for Brevo are still blank: Throughput ceiling and MCP server. Those render as dashes rather than as zeroes or assumptions, because an empty cell and a bad cell are not the same thing and only one of them is honest. If you know any of these figures and can point at a document, tell us.