Brevo (Automation)
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 3 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Sendinblue SAS · www.brevo.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.
Brevo (Automation) at a glance
- Vendor
- Sendinblue SAS
- Headquarters
- Incorporated in France source, captured 16 Nov 2026
- Data hosting
- In the EU source, captured 16 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 16 Nov 2026
- Panel verdict
- The AI panel rates Brevo (Automation) 2.5/5, the mean of 6 judges. Brevo is a marketing automation platform from Brevo GmbH of Berlin. how scores are made
- As of
- Vendor pages captured 16 Sep 2026 to 16 Nov 2026; evaluated by the panel 17 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Brevo is a marketing automation platform from Brevo GmbH of Berlin. The bench scores it strongest on channel coverage and sovereignty, each 6-7, and weakest on lead management at 4 and pricing transparency at 4-5. Channel strength is documented breadth — email, SMS, WhatsApp, web and mobile push from one platform with behaviour-triggered sequences — while sovereignty rests on servers stated in the EU on Google Cloud, an Article 28 agreement inside the terms of service, and named transfers to the USA and India. Lead management is held down by a predictive scoring claim in a single line, with no public information on the model, routing or score history. Pricing shows a free plan for up to 2,000 contacts and volume floors such as 'Ab 5.000 E-Mails/Monat', but no per-tier prices are published and Enterprise is 'Auf Anfrage'. The splits are consent and profiling and CRM and data, each 4-6, where judges weighing undocumented consent proof or the Pro-and-Enterprise gating of the Salesforce connector and consent groups scored below those crediting 30-day erasure and the documented bidirectional sync.
Speaks for it
- Free plan includes marketing automation for up to 2,000 contacts with no credit card needed
- Email, SMS, WhatsApp, web and mobile push run from one platform, with behaviour-triggered journeys and re-entry control per contact and object
- Servers stated in the EU on Google Cloud, with an Article 28 processing agreement inside the terms of service and a TÜV Rheinland report on the technical measures
- Erasure of a contact's data is documented within 30 days, including removal from other Brevo accounts on a direct request
- Bidirectional, real-time Salesforce sync is documented with full control over field mapping and sync preferences
Held against it
- Predictive lead scoring is a single marketing line, with no public information on the model, routing rules or per-contact score history
- We found no public information on per-tier prices, paid-plan contact limits, overage rates or VAT treatment; Enterprise is 'Auf Anfrage'
- We found no public information on cross-channel frequency capping or shared unsubscribe handling across channels
- We found no public information on duplicate handling, per-field conflict resolution, sync error logs or documented API rate limits
- Subprocessors are stated to be listed in the agreement, with locations not published and OpenAI, Chatbase and Karumi named in the website AI chain
Best for
- You need email, SMS, WhatsApp and web and mobile push coordinated from one platform, with journeys that escalate email to SMS to WhatsApp on non-opens
- You want to start at no cost — the free plan carries marketing automation for up to 2,000 contacts, with no credit card needed
- Your procurement asks for a German contracting entity, EU server location stated on Google Cloud, and a self-serve Article 28 agreement folded into the terms
- You want a built-in CRM with customisable deal stages where CRM events like deal-stage changes can trigger automated journeys
Avoid if
- You must compute your full annual invoice from published prices before committing — the pages show volume floors and Enterprise 'Auf Anfrage' rather than per-tier figures
- Your sales process depends on a lead score the team can explain — the predictive scoring claim is a single line with no public documentation of the model or its signals
- You need the Salesforce sync, consent groups or mobile push outside the top tiers — the Salesforce connector is available only for Brevo Pro & Enterprise accounts, consent groups are listed for Enterprise and Pro, and mobile push for Pro and Enterprise
- You rely on advertising-audience sync to the major networks — Facebook advertising appears only as an optional third-party feature in the privacy policy
The scores
| Criterion | Panel median |
|---|---|
| Journeys & orchestration | 3 of 5 |
| Lead scoring, routing & lifecycle | 2 of 5 |
| Channels & personalisation | 3 of 5 |
| Consent, tracking & profiling | 2.5 of 5 |
| CRM integration & data model | 3 of 5 |
| European sovereignty | 3.5 of 5 |
| Pricing transparency | 2 of 5 |
Journeys & orchestration
Show reasoningHide reasoning
How this is scored
Multi-step automation: triggers, branching, waits, goals — and what happens when a contact qualifies for several journeys at once.
0 — No automation; the product sends one-off campaigns only.
3 — Autoresponders or linear sequences started by a trigger such as a sign-up or a tag, with waits between steps.
5 — A visual workflow builder with triggers on behaviour and attributes, if/else branching and waits, and goals or exit conditions that take a contact out of the flow.
8 — Event-driven entry from external systems through an API, frequency capping and suppression across journeys, priority when a contact qualifies for several, per-contact journey state and reporting per step, versioning or safe editing of a live journey, and testing against real records.
10 — Orchestration is coherent across the whole programme: one decision layer deciding what a person receives next regardless of which journey wants to send it, holdout groups for measurement, and journeys documented and readable months later.
The Demand Gen Lead
The drag-and-drop workflow editor with behavioural triggers, sequences that escalate email to SMS to WhatsApp on non-opens, and re-entry control evaluated per contact and object is genuine orchestration, and release notes promise live automations keep their current behavior when things change. But I found no public information on frequency capping, on arbitration when a contact qualifies for several journeys at once, or on reporting per step — the pieces that make attribution survive a quarterly review. 7 8 10 13 14
The Sales Ops Manager
The drag-and-drop workflow editor triggers on behaviour — sign-ups, purchases, abandoned carts, even CRM deal-stage changes and contact updates — and the documented cross-channel sequence of email first, SMS if unopened, then WhatsApp is real conditional orchestration, with re-entry control on contact-plus-object pairs and configurable re-entry delays giving me journey-state discipline. We found no public information on frequency capping, suppression across journeys, priority when a contact qualifies for several at once, per-step reporting, or safe editing and versioning of a live journey. 7 8 10 13 14
The Data Protection Officer
A drag-and-drop workflow editor is documented with behavioural triggers (sign-ups, purchases, abandoned carts) and CRM-event triggers such as deal-stage changes, coordinated multichannel sequences with conditional follow-up, and per-contact re-entry control including delays, with release notes stating live automations are not disrupted by updates. We found no public information on frequency capping, suppression or priority when a contact qualifies for several journeys, versioning, or reporting per step. 7 10 8 14 13
The Lifecycle Marketer
A drag-and-drop workflow builder with behavioural triggers (sign-ups, purchases, abandoned carts, CRM deal-stage changes), coordinated email-then-SMS-then-WhatsApp sequences, and unusually well-documented re-entry control per contact and object with configurable delays gets well past a basic builder. But I found no public information on frequency capping or suppression across journeys, priority when a contact qualifies for several, holdout groups for measurement, or reporting per step — and without those I cannot treat orchestration as programme-level. 7 8 10 13 14
The Solution Architect
The drag-and-drop workflow editor runs behaviour-triggered, cross-channel sequences — email first, then SMS if unopened, then WhatsApp — and object-based automations now carry re-entry control and re-entry delays, with CRM events such as deal stage changes able to start flows. I found no public information on frequency capping and suppression across journeys, per-step reporting, safe editing of a live journey, or testing against real records, so I place this just above the visual-builder level. 7 8 10 14
The Skeptic
The pages show a drag-and-drop workflow editor with behavioural triggers (sign-ups, purchases, abandoned carts, CRM deal-stage changes), a branching sequence that sends SMS only if the email goes unopened, and re-entry control with settable delays per contact-plus-object pair. We found no public information on goals or exit conditions, per-step reporting, frequency capping, suppression across journeys, or priority when a contact qualifies for several at once. A capable builder, documented short of programme-level orchestration. 7 8 10 13 14
Lead scoring, routing & lifecycle
Show reasoningHide reasoning
How this is scored
Scoring, qualification and handover to sales — including whether the customer can explain to a lead why the system decided what it decided.
0 — No scoring, lifecycle or lead handling at all; the product is a sending tool for lists.
3 — A rule-based lead score from attributes or engagement, or lifecycle stages set by tags or fields.
5 — Configurable lead scoring on attributes and behaviour, lifecycle or pipeline stages, and qualified leads assigned or notified to sales.
8 — Multiple scoring models per product or region, negative scoring and score decay, account-level scoring alongside contact-level, routing rules to owners or teams with follow-up SLAs, and score history visible per contact.
10 — Scoring is explainable and accountable: the contribution of each signal visible per record, model changes versioned with their effect on the funnel, routing rules auditable, and predictive scoring — where offered — documented well enough for a DPO to assess it as automated decision-making.
The Demand Gen Lead
A built-in CRM with customisable deal stages and predictive lead scoring created from CRM data is on the table, plus automated sales sequences. I found no public information on routing rules to owners or teams, follow-up SLAs, score history per contact, or how the predictive model reaches its number — sales will not trust a score they cannot explain. 13 14
The Sales Ops Manager
A built-in CRM with customizable attributes, list views and deal stages covers lifecycle, and predictive lead scoring is claimed on the integration pages. That scoring claim is a single line, though: we found no public information on configurable scoring rules, routing to owners or teams with follow-up service levels, score history per contact, or how the predictive model reaches its decision — as the owner of the handover to sales I cannot defend a score nobody can explain. 14
The Data Protection Officer
Predictive lead scoring and automated sales sequences are claimed in a single line built on CRM data, with customizable deal stages and a built-in CRM around them, but the model is not documented: no per-record signal contributions, no score history, nothing a DPO could assess as automated decision-making under Art. 22. We found no public information on routing rules, negative scoring, score decay, or handover with follow-up SLAs. 14 13
The Lifecycle Marketer
A built-in CRM with customisable attributes and deal stages is documented, and predictive lead scoring with automated sales sequences is named once on an integration page. I found no public information on how the score is configured, whether it decays or handles negatives, routing rules to owners or teams with follow-up commitments, or score history visible per contact — a named feature is not an accountable one. 13 14
The Solution Architect
Predictive lead scoring and automated sales sequences over customisable deal stages are claimed, with leads and engagement syncing to Salesforce in real time. But the scoring is a single marketing sentence — I found no public information on configurable models, negative scoring, decay, routing to owners with follow-up SLAs, or per-contact score history, and nothing a DPO could use to explain a score to the individual it ranked. 13 14
The Skeptic
A built-in CRM with customisable deal stages and attributes, plus a single marketing line promising predictive lead scoring, is the whole of the evidence. We found no public information on routing to owners, score history per contact, negative scoring or decay, or any documentation that would let a customer explain a score to the lead it concerns. That sits between tag-driven stages and a configurable, accountable scoring setup. 13 14
Channels & personalisation
Show reasoningHide reasoning
How this is scored
What the platform can send and personalise — email, SMS, push, on-site content, ad audiences — judged on what shares one profile and one suppression list.
0 — Not a sending platform; the product cannot deliver messages on any channel.
3 — Email with merge-field personalisation, plus sign-up forms or landing pages.
5 — Email plus at least one further channel (SMS, push, or ad-audience sync) driven from the same contact profile, and dynamic content blocks based on contact data.
8 — Email, SMS and push from one profile with shared unsubscribe handling, on-site personalisation, ad-audience sync to the major networks, cross-channel frequency capping, and content personalised on behaviour rather than only on stored fields.
10 — Channel is a delivery detail: one profile and one consent state across every channel, next-best-channel selection, and personalisation that draws on the full behavioural record without the marketer assembling it by hand.
The Demand Gen Lead
Email, SMS, WhatsApp, web and mobile push and live chat all run from one platform with replies landing in one Conversations inbox, and workflows coordinate channels based on behavior like an unopened email. I found no public information on ad-audience sync to the major networks, cross-channel frequency capping, or on-site personalisation. 9 10 14
The Sales Ops Manager
Email, SMS, WhatsApp, web and mobile push, pop-ups and a unified Conversations inbox all run off one platform with the contact record kept in sync, and abandoned-cart emails plus behaviour-triggered SMS with web-tracking segmentation show personalisation driven by what people do, not only stored fields. We found no public information on cross-channel frequency capping or shared unsubscribe handling across channels, and advertising audiences appear only as optional third-party features named in the privacy policy. 7 9 10 14 3
The Data Protection Officer
Email, SMS, WhatsApp, web and mobile push and pop-ups are documented as one platform, with behavioural segmentation including web tracking, AI-assisted copy, and a self-serve preference centre letting contacts opt in or out of specific topics. We found no public information on cross-channel frequency capping or shared unsubscribe handling across channels; Facebook advertising appears only as an optional external feature in the privacy policy, and we found no public information on ad-audience sync or on-site personalisation beyond pop-ups. 10 9 11 3
The Lifecycle Marketer
Email, SMS, WhatsApp, web and mobile push, live chat, pop-ups and optional Facebook advertising are all documented as driven from one platform with customer data kept in sync, plus a unified Conversations inbox for replies. But I found no public information on cross-channel frequency capping or shared unsubscribe handling across channels, and the personalisation evidence is template greetings and AI-generated copy rather than content drawn from the behavioural record — segmentation with web tracking is targeting, not personalised content. 9 10 11 14 3
The Solution Architect
Email, SMS, WhatsApp, web and mobile push, live chat and pop-ups all run from one platform with customer data kept in sync, a unified Conversations inbox, and behaviour-triggered multichannel sequencing on segmentation that includes web tracking. For a programme-level buyer I found no public information on cross-channel frequency capping, one suppression list shared across channels, or ad-audience sync beyond Facebook ads appearing as an optional third-party feature. 9 10 14
The Skeptic
Email, SMS, WhatsApp and web and mobile push are documented from one platform with customer data kept in sync, behavioural branching across channels, web tracking feeding segmentation, and a unified inbox — breadth well past a single extra channel. Ad audiences appear only as an optional third-party feature named as Facebook advertising, and we found no public information on cross-channel frequency capping or shared unsubscribe handling. Strong on what it can send, quiet on the guardrails. 3 9 10 11
Consent, tracking & profiling
Show reasoningHide reasoning
How this is scored
The platform builds behavioural profiles of named people. Consent capture and proof, tracking that can be limited, retention, and whether automated decisions about individuals are documented and contestable.
0 — The vendor states a practice that defeats consent, such as importing purchased lists or tracking named contacts with no opt-in mechanism at all.
3 — Double opt-in available and unsubscribe handled per contact.
5 — Double opt-in with the consent timestamp and source stored per contact, consent or subscription status per channel, and a documented way to answer access and erasure requests.
8 — Consent reproducible as evidence with the wording versioned, tracking switchable per contact or a cookieless or first-party tracking mode, profiling suppressible per person, retention for inactive records stated and executed per data category, and erasure covering derived scores.
10 — Built for the accountability principle: a per-contact history of what was tracked, scored and decided, automated decision-making documented well enough to support an Art. 22 DSGVO assessment, profiling off by default for anyone who has not consented to it, and deletion that removes derived scores as well as raw events.
The Demand Gen Lead
An opt-in-only posture, topic-level consent groups with a self-serve preference centre, erasure within 30 days including removal from other Brevo accounts, and the full set of GDPR rights documented put this solidly mid-scale. But web tracking is offered for segmentation while we found no public information on the consent timestamp and source stored per contact, on limiting tracking per person, or on suppressing profiling for an individual. 11 12 3 10
The Sales Ops Manager
Consent groups with a self-serve preference centre let contacts opt in and out per topic, erasure is documented within 30 days with cross-account removal when a contact asks directly, and retention periods are published per data category with API control over how long data stays stored. We found no public information on double opt-in, consent timestamp and source stored per contact, per-contact tracking switches or cookieless tracking, versioned consent wording, or suppressing profiling for an individual. 9 11 12 3
The Data Protection Officer
Opt-in and opt-out management is automatic, consent groups with a self-serve preference centre give topic-level consent (on Pro and Enterprise plans), erasure is documented with a 30-day deadline, DPO postal and email channels, and removal of a requesting contact's data from all Brevo accounts, and retention periods are stated per data category with the API described as giving full control over storage duration. We found no public information on double opt-in with the consent timestamp and source stored per contact, a per-contact switch for web tracking, suppressible profiling, or erasure that covers derived scores. 11 12 3 9 3
The Lifecycle Marketer
Consent groups with a self-serve preference centre, campaign assignment and automatic opt-in/opt-out management are documented, and the rights side is concrete: erasure within 30 days, cross-account removal on a valid direct request, and stated retention per data category with API control over storage duration. I found no public information on consent timestamps and source stored per contact, consent status per channel, per-contact limits on web tracking, or the ability to suppress profiling for an individual. 9 11 12 3
The Solution Architect
Consent groups and a self-serve preference centre replace blanket subscribe/unsubscribe with per-topic choice, erasure is documented to complete within 30 days including cross-account removal on a contact's direct request, and API control over retention is stated. The model is topic-based rather than per channel, and I found no public information on double opt-in, stored consent timestamps and source, tracking limits per person, or whether deletion removes derived scores — while the predictive scoring that ranks individuals is undocumented as automated decision-making. Consent groups also ship only on Pro and Enterprise. 9 11 12 14 3
The Skeptic
Consent groups and a self-serve preference centre let contacts opt in and out per topic, opt-ins and opt-outs are managed automatically, and erasure is documented with a 30-day commitment reaching across Brevo accounts, alongside the full rights catalogue, a DPO address and retention periods per data category. We found no public information on a double opt-in, the consent timestamp and source kept per contact, or any way to switch tracking or profiling off per person. Requests are well handled; proof of consent is not on show. 9 11 12 3
CRM integration & data model
Show reasoningHide reasoning
How this is scored
The join that decides the implementation: how the platform and the CRM stay in agreement about who a person is, and what happens when they disagree.
0 — No way to get contact data in or out beyond typing it in.
3 — CSV import and export, and a sync or connector to a named CRM.
5 — Two-way sync with at least one major CRM (or a built-in CRM) with field mapping, duplicate handling, and a documented API.
8 — Configurable conflict resolution per field, account and contact objects both modelled, custom objects supported, near-real-time sync with retry and an error log, and API rate limits documented.
10 — One record, two systems, no ambiguity: identity resolution across anonymous and known states, field-level ownership defined per system, replay of failed syncs, and a data model the customer can extend without vendor services.
The Demand Gen Lead
Bidirectional, real-time Salesforce sync with full control over field mapping and sync preferences, a built-in CRM with customisable deal stages, CDP-style 360-degree profiles, and open-source SDKs and an API cover the join a real implementation needs. Duplicate handling, per-field conflict resolution, retry and error logs, and documented rate limits are not shown on the captured pages. 13 14 10 9
The Sales Ops Manager
Bidirectional, real-time Salesforce sync with flexible field mapping and stated full control over field mapping and sync preferences, plus a built-in CRM whose attributes, list views and deal stages I can customize, is the right skeleton — though the Salesforce connector sits behind Pro and Enterprise. The join mechanics are what stay silent: we found no public information on duplicate handling, per-field conflict resolution, sync retry and an error log somebody can act on before the pipeline report is wrong, or documented API rate limits, and the Zoho path moves contacts one way through Apix-Drive or Zapier. 10 13 14
The Data Protection Officer
Bidirectional, real-time sync with Salesforce Sales Cloud is documented with full control over field mapping and sync preferences, alongside a built-in CRM with customizable deal stages, Zoho contacts imported into the customer data platform via no-code connectors, a documented API, and native integrations including HubSpot. We found no public information on duplicate handling, per-field conflict resolution, retry with error logs, or documented API rate limits. 13 14 10 12
The Lifecycle Marketer
Two-way, real-time sync with Salesforce with full field-mapping control, a built-in CRM with customisable attributes and deal stages, and connection via native integrations, Zapier, Make or API make the join credible and the objects match a lifecycle view. I found no public information on duplicate handling, configurable conflict resolution per field, sync retry and error logs, or documented API rate limits — the operational evidence a migration planner needs is thin. 10 13 14
The Solution Architect
Bidirectional, real-time Salesforce sync with full field-mapping control, a built-in CRM with customisable attributes, list views and deal stages, object+contact automation pairs, and open-source SDKs put this comfortably above a plain connector. The join I would probe in an implementation — conflict resolution per field, custom objects, sync error logs and retries, published API rate limits, and the path from anonymous visitor to known contact — gets no public documentation; the Customer Data Platform is named for Zoho sync but its identity resolution is not described. 8 9 13 14
The Skeptic
Bidirectional, real-time sync with Salesforce with full field-mapping control is stated, the built-in CRM allows customised attributes and deal stages, Zoho arrives one-way through no-code connectors, and contacts export to CSV. We found no public information on duplicate handling, per-field conflict resolution, custom objects, retry and error logs, or documented API rate limits. A real connector, an undefined data model. 10 12 13 14
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where behavioural profiles of named EU residents are processed, who the contracting entity is, and which subprocessors see them. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it — which given the profiling is heavily. Dimensions the sources do not establish are unknown, not non-EU.
0 — Proven non-EU: a non-EU vendor and contracting entity with hosting and tracking stated outside the EU.
3 — One European element proven — an EU contracting entity or EU data residency stated — with the rest of the chain undocumented.
5 — An EU contracting entity and EU hosting both stated, and a data processing agreement offered.
8 — EU hosting on named infrastructure, EU contracting entity, a subprocessor list published with locations, and any non-EU processing (tracking, AI scoring, support access) named with its legal basis.
10 — Sovereign end to end and evidenced: every profile, event and derived score processed in the EU by European subprocessors, certification published, and no transfer requiring a Schrems II argument to survive.
The Demand Gen Lead
Brevo GmbH in Berlin under German law with parent Brevo SAS in Paris, EU hosting stated on Google Cloud, an Article 28 processing agreement folded into the terms with a TÜV Rheinland-checked TOMs report, and subprocessors listed in the agreement with US and India transfers named on Data Privacy Framework or standard contractual clauses. Per-subprocessor locations are not published and the residency claim rests on a single marketing line naming no provider, and with India transfers riding on standard clauses a Schrems II assessment is still part of the chain — which, given the profiling, I weigh heavily. 5 9 4 3 3 6
The Sales Ops Manager
A German contracting entity under a French parent, EU hosting stated with Google Cloud named for European data, a self-serve Article 28 agreement folded into the terms of service, and a TÜV Rheinland report on the technical and organisational measures — that carries real weight where I sit. Transfers to the USA and India are named with their legal basis, and subprocessors including the AI providers OpenAI, Chatbase and Karumi are listed in the agreement, but we found no public information on subprocessor locations, so the chain falls short of provable end-to-end EU processing. 3 4 6 9 3 5
The Data Protection Officer
Brevo GmbH in Berlin is the named provider under German law with parent Brevo SAS in Paris, servers are stated to be in the EU on Google Cloud with European data hosted in Europe, an Art. 28 data processing agreement is integral to the terms with a TÜV Rheinland report on the technical measures, and all subprocessors are stated to be listed in the agreement. Transfers to the USA and India are named with the EU-U.S. Data Privacy Framework or standard contractual clauses as basis, but subprocessor locations are not published and the named AI services (OpenAI, Chatbase, Karumi) leave a transfer analysis the customer must still perform. 5 9 6 4 3 3
The Lifecycle Marketer
A German contracting entity (Brevo GmbH, Berlin, with the French parent named), EU server location on named Google Cloud infrastructure, an Art. 28 processing agreement included in the terms of service, and third-country transfers to the USA and India named with their legal basis — that is a chain I can mostly verify. It stops short of the higher level because subprocessors are published only as categories rather than a list with locations, and the EU-residency statement does not address the third-party services named in the privacy policy. 3 4 6 9 3 5
The Solution Architect
A German contracting entity in Berlin under a French parent, hosting stated in the EU on named Google Cloud infrastructure, an Art. 28 processing agreement folded into the terms with a TÜV Rheinland audit of the technical measures, and transfers to the USA and India named with the Data Privacy Framework or standard contractual clauses as basis. The subprocessor list lives inside the agreement rather than a public page with locations, and the residency statement is one line that does not address third-party services such as reCAPTCHA — so end-to-end European processing of every profile and event is not established. 4 6 9 3 5
The Skeptic
Brevo GmbH of Berlin contracts under German law under a French parent, servers are stated in the EU on named Google Cloud infrastructure, an Art. 28 processing agreement ships inside the terms of service, and TÜV Rheinland has reported on the technical measures. Transfers to the USA and India are named with their safeguards, but subprocessors are said to be listed in the agreement with no locations on the pages we read, and OpenAI, Chatbase and Karumi sit in the website AI chain. European at the core, undocumented at the tail. 3 4 6 9 3 5
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual invoice for their contact base and send volume — including the tier where automation actually begins, overage, and mandatory onboarding — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price or a single tier with its contact limit.
5 — Prices per tier public with the billing period and contact limits stated, and which tier includes automation visible.
8 — Every tier priced publicly with contact and volume limits, feature boundaries, overage rates, onboarding costs, minimum term and VAT treatment stated.
10 — Complete price computability: annual invoice derivable for a given contact count, send volume and feature set, including overage, additional users and any implementation fee stated outright.
The Demand Gen Lead
The free plan with up to 2,000 contacts including marketing automation and no credit card is stated outright, tier email volumes begin at stated figures (from 5,000 E-Mails/Monat, from 150,000 E-Mails/Monat), SMS credits are priced per country with a worked example (100 SMS to Germany at 9 credits per message €9.00), and there are no monthly minimums. But Enterprise is 'Auf Anfrage', and we found no per-tier contact-limit ladder, overage rates, or VAT treatment — I cannot compute the real annual invoice from these pages. 2 7 10 9
The Sales Ops Manager
The free plan carries 2,000 contacts including marketing automation, paid tiers are published as email volumes from 5,000 per month and from 150,000 per month, and SMS credits are priced publicly with a worked example, so the tier where automation begins is visible. But we found no public information on the per-tier currency prices with billing period and paid-tier contact limits, overage rates, onboarding costs or VAT treatment, and Enterprise is priced only on request — I cannot compute the real annual invoice from these pages. 2 7 9 10
The Data Protection Officer
The free plan's 2,000-contact limit with marketing automation included is public, tier email volumes are stated ("Ab 5.000 E-Mails/Monat", "Ab 150.000 E-Mails/Monat"), the SMS rate is public ("Prices start at $0.0109 per message credit in the US and vary by country"), and no monthly minimums or contracts are stated — but the pages give only an aggregate range of 0.00 to 5388.96 USD across nine offers rather than each tier's price, and Enterprise is "Auf Anfrage". We found no public information on VAT treatment or onboarding costs. 2 7 10 9 11 13
The Lifecycle Marketer
The free plan with 2,000 contacts including marketing automation is public, tier email volumes and a published price range across nine offers are visible, and SMS is priced per message credit ("$0.0109 per message credit in the US"), with no monthly minimums or contracts. But I found no public information on per-tier prices with billing periods and contact limits, overage rates, onboarding costs or VAT treatment, and Enterprise pricing is on request — a buyer still cannot compute their real annual invoice. 2 7 10
The Solution Architect
Public facts cover the free plan with 2,000 contacts including automation, tier volumes of "Ab 5.000 E-Mails/Monat" and "Ab 150.000 E-Mails/Monat", a worked SMS example of "100 SMS messages to Germany at 9 credits per message €9.00", prices starting at "$0.0109" per message credit in the US, no monthly minimums or contracts, and clear feature boundaries by tier. I could not compute a real annual invoice from the published pages, though: per-tier prices with contact limits and billing period are not shown, Enterprise is "Auf Anfrage", and onboarding and VAT treatment are not stated. 2 7 10 13
The Skeptic
Automation is stated on the free plan for up to 2,000 contacts with no credit card — the entry tier is unusually visible — and plan-gated features (Salesforce integration, mobile push, consent groups, phone support) are each marked with their plan. But the pricing page offers volume floors ("Ab 5.000 E-Mails/Monat", "Ab 150.000 E-Mails/Monat") and Enterprise "Auf Anfrage" rather than per-tier prices — an aggregate range of 0.00 to 5388.96 USD appears in page markup with no tier figures — and we found no public information on contact limits per paid tier, overage rates, VAT treatment, or a price for the Enterprise onboarding that is described but never costed. You can see where automation begins; you cannot compute the annual invoice. 2 7 9 10 11 13
European sovereignty — proven facts
3 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 | Incorporated in FR | 2/2 pts | 5 Report an error |
|---|---|---|---|
| Hosting location |
EU only
unverified
Why unverified?Single marketing-style line on the security page naming no country or hosting provider, and it does not address the third-party services (e.g. Google reCAPTCHA, Cloudflare Turnstile) named in the privacy policy. |
4/4 pts | 6 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Published, self-serve
unverified
Why unverified?The agreement text itself sits in Annex 3 of the terms of service; this page offers only a preview link ("Zur Vorschau des AV-Vertrags"). |
1/1 pts | 4 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Brevo (Automation)
Is Brevo (Automation) European?
Yes. whats-best.ai classifies Brevo (Automation) as EU-Made. Its vendor, Sendinblue SAS, is incorporated in France, per the vendor’s page captured 16 Nov 2026.
Where does Brevo (Automation) store data?
Brevo (Automation) stores customer data in the EU, per the vendor’s page captured 16 Nov 2026.
Does Brevo (Automation) have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to Brevo (Automation)?
As of 18 Nov 2026, the panel rates Braze (3/5), HubSpot Marketing Hub (3/5) and ActiveCampaign (Automation) (3/5) highest among the other 20 Marketing Automation 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 CleverReach (Automation) (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Brevo (Automation) alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 16 Sep 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. The agreement text itself sits in Annex 3 of the terms of service; this page offers only a preview link ("Zur Vorschau des AV-Vertrags").
- Weak sourcing — Hosting location. Single marketing-style line on the security page naming no country or hosting provider, and it does not address the third-party services (e.g. Google reCAPTCHA, Cloudflare Turnstile) named in the privacy policy.
- 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.
- 30 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
- 13 integrations 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
- 12 data 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
- 10 legal 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
- 4 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 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
- 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 subprocessors 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 (15)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Product page www.brevo.com Checked 16 Nov 2026 Details →
- 2 Pricing www.brevo.com Checked 16 Nov 2026 Details →
- 3 Privacy policy www.brevo.com Checked 16 Nov 2026 +2 earlier captures: 19 Oct 2026, 16 Sep 2026 Details →
- 4 Privacy policy www.brevo.com Checked 16 Nov 2026 Details →
- 5 Imprint www.brevo.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 6 Security / trust page — found from the homepage www.brevo.com Checked 16 Nov 2026 Details →
- 7 Journeys & orchestration — found from sitemap www.brevo.com Checked 16 Nov 2026 Details →
- 8 Journeys & orchestration — found from sitemap www.brevo.com Checked 16 Nov 2026 Details →
- 9 Channels & personalisation — found from sitemap www.brevo.com Checked 16 Nov 2026 Details →
- 10 Channels & personalisation — found from sitemap www.brevo.com Checked 16 Nov 2026 Details →
- 11 Consent, tracking & profiling — found from sitemap www.brevo.com Checked 16 Nov 2026 Details →
- 12 Consent, tracking & profiling — found from sitemap www.brevo.com Checked 16 Nov 2026 Details →
- 13 CRM integration & data model — found from sitemap www.brevo.com Checked 16 Nov 2026 Details →
- 14 CRM integration & data model — found from sitemap www.brevo.com Checked 16 Nov 2026 Details →
- 15 Structured-data backfill: markup only, no text or screenshot www.brevo.com Checked 8 Nov 2026 Details →