Past Brevo (ex-Sendinblue)?
The all-in-one trade-offs.

Brevo's commercial trajectory is the strongest evidence that the European alternative-to-US-SaaS thesis works at scale. The company started as a French email-marketing tool competing primarily with Mailchimp on price, built a 600,000+ customer base across 180 countries, and progressively expanded the product surface to include SMS (acquired Sumotraffic in 2017), conversational messaging, CRM, marketing automation, and most recently AI-powered campaign generation. The €200M ARR milestone in 2025 places Brevo among the largest European SaaS companies by revenue, and the December 2025 funding round signals strategic-capital availability through 2030.

The product itself is what most customers experience day-to-day. The email marketing builder is competent: drag-and-drop editor, 40+ pre-built templates, basic A/B testing, segmentation by demographic and engagement attributes, marketing automation workflows that compete with mid-tier ActiveCampaign or HubSpot. The transactional email side is functional: REST API, SMTP relay, outbound webhooks, unlimited log retention on paid tiers. The all-in-one breadth means small senders can centralise email plus SMS plus CRM plus landing pages plus basic chat under one vendor relationship, which is the platform's clearest operational advantage.

Pricing is the second clearest advantage. Brevo charges per email sent rather than per contact stored. For a sender with a 50,000-contact list emailing monthly, Brevo costs $19 per month at the Starter tier (20,000 monthly emails). The same workload on Mailchimp would cost roughly $385 per month at the equivalent feature level, because Mailchimp charges per stored contact regardless of send frequency. The cost differential is real and not marketing exaggeration; we have seen migration cases where a customer's monthly bill dropped 85-90% by switching from Mailchimp to Brevo without losing meaningful functionality at the marketing-tool layer.

The free tier is genuinely usable for small senders: 300 emails per day (approximately 9,000 monthly) with unlimited contacts, full marketing automation, the CRM and most platform features. This is significantly more generous than Mailchimp's free tier (500 contacts maximum), Postmark's free tier (100 emails per month), or any of the other ESPs we compare against. For early-stage SaaS validating product-market fit, the Brevo free tier is often the right starting point.

The strategic positioning around EU data residency is clear and well-executed. Brevo's primary data centres are in France with secondary capacity in Germany and Belgium. The company is a French S.A. subject to French data protection law and CNIL oversight. The DPA is straightforward, the sub-processor list is shorter than US-origin alternatives, and the procurement-cleared posture for EU customers is one of the strongest in the all-in-one ESP category. For European procurement teams that need to demonstrate vendor sovereignty to a supervisory authority, Brevo is one of the few ESP options that does not require contractual gymnastics to clear.

Profile one: marketing-led SMB or mid-market businesses needing a single platform for email plus SMS plus light CRM plus marketing automation. A French B2C e-commerce business at €1M-€20M revenue, 5-15 person marketing team, sending weekly newsletters plus segmented campaigns plus transactional order confirmations, plus occasional SMS notifications for shipping. The team wants one platform, one vendor relationship, one set of credentials. Brevo's all-in-one architecture matches this requirement directly and the pricing is competitive enough that the operational consolidation justifies the deliverability trade-off. The Starter tier at $9/month or Business tier at $18/month covers most of this profile. The Mailchimp alternative would cost 4-5x more for equivalent functionality.

Profile two: pre-revenue and early-stage startups validating product-market fit. The Brevo free tier (300 emails/day, unlimited contacts, full marketing automation, CRM) is the most generous in the all-in-one ESP category. A founding team can validate their email marketing thesis, A/B test signup flows, and build the first 1,000-10,000 customer relationship without any ESP cost. The migration to a paid Brevo tier when volume justifies it is straightforward. The migration to a different vendor — if the team decides Brevo's deliverability ceiling is a constraint — is also straightforward because Brevo's data export is competent and the sender's domain reputation is portable.

Profile three: French and European public-sector procurement requiring "sovereign-cloud-equivalent" posture for non-classified workloads. French public-sector entities under the SecNumCloud framework, or German public-sector entities under BSI C5, increasingly prefer EU-origin vendors with documented EU data residency for non-classified marketing and outreach workloads. Brevo's French S.A. status and CNIL-supervised processing make it acceptable for many public-sector procurement processes that would reject US-origin alternatives. For classified or sensitive workloads, public-sector procurement still requires deeper sovereignty guarantees that Brevo's all-in-one platform cannot provide, but for the marketing and outreach layer Brevo clears the bar.

Outside these three profiles, Brevo's fit becomes thinner. Volume above 100K-500K monthly stresses the shared-IP architecture. Transactional-critical workloads sit uncomfortably alongside marketing traffic on shared pools. Sender profiles with strict deliverability requirements find the 88% category-median measurement inadequate. The all-in-one architecture trades depth for breadth in a way that matters more at scale than at SMB volume.

Volume above 150K monthly with deliverability sensitivity. Brevo's shared-IP pools handle volume below 150K reasonably; above that, the shared-pool reputation variance becomes binding. The Brevo upgrade path is the Professional plan (starting $499/month for 150K+) with dedicated IP, which is competitive on absolute price with our infrastructure but trades the all-in-one CRM/automation/SMS features the customer was paying for in the lower tiers. At Professional-tier pricing, the comparison becomes "Brevo Professional with dedicated IP and reduced platform breadth" versus "BIG BOX managed SMTP Relay with dedicated IP and email-focused depth." The deliverability gap at this volume favours us — measured 4-8 percentage point inbox-placement improvement against Brevo Professional in our internal benchmarking — and the architectural focus produces an operational interface that experienced deliverability engineers prefer.

Transactional-critical workloads where each percentage point of inbox placement maps to revenue. Brevo's transactional SMTP relay is documented as "50% delivered within 1 second" on the strongest cases. The strongest cases assume good list hygiene, good sender reputation and good receiver behaviour. The 50th-percentile measurement obscures a long tail: transactional emails that take 30-90 seconds to deliver, or that land in spam folders despite proper authentication, because the shared pool reputation has been temporarily compromised by another sender's campaign. For password resets, 2FA codes, payment confirmations and verification emails, this long-tail variance produces measurable user-experience and revenue impact. Our infrastructure separates transactional traffic onto dedicated pools at the SMTP Relay Standard tier upward; the long-tail variance is materially lower.

Architectural depth requirements (custom MTA tuning, per-receiver traffic shaping, advanced deliverability remediation). Brevo's platform abstracts the underlying email infrastructure from the customer. This is the right choice for the customer profile Brevo targets. It is the wrong choice for senders with internal deliverability expertise who want to interact with the MTA configuration, IP rotation strategy, per-receiver bounce categorisation and traffic-shaping primitives. Our managed PowerMTA and managed KumoMTA expose these primitives to the customer's operations team. We provide the operational layer (uptime, security patching, configuration backup) while the customer makes the deliverability decisions. For senders whose business model depends on email deliverability as a competitive advantage, this depth is non-substitutable.

Regulator-grade processing posture for financial services workloads. The argument extends to healthcare workloads. It extends to public-sector workloads. Brevo's EU residency posture is genuine and adequate for most regulated sectors at the platform level. The gap appears for workloads where the sector regulator audits the sub-processor chain, the data processing geography under operational stress, and the specific contractual commitments at Annex II depth. Brevo, as a 600,000-customer platform, operates with a standardised DPA and sub-processor list that does not accommodate per-customer variation easily. Our DPA is customisable for regulator-driven requirements; we have negotiated custom Annex II provisions for clients under BaFin, ACPR, FINMA plus HDS plus equivalent sector regulators. For workloads where the regulator interaction is binding, custom contractual posture matters.

Scenario A: 30K monthly email, mixed traffic, French SMB. Brevo Business at $18/month with no dedicated IP needed = $216 annual. BIG BOX SMTP Relay Starter at €99/month = €1,188 annual. Brevo wins by approximately €1,000 annual at this volume. The deliverability gap is absorbable for marketing-led SMB workloads. We will not recommend a migration from Brevo to BIG BOX at this band unless the customer's specific use case (transactional-critical traffic, regulator audit pending, sub-processor restriction binding) makes the deliverability or jurisdiction premium worthwhile.

Scenario B: 250K monthly mixed traffic, EU mid-market B2B SaaS with deliverability sensitivity. Brevo Professional at $499/month for 150K base plus 100K overage at approximately $1.50/1K = $499 + $150 = $649 monthly = $7,788 annual. Includes dedicated IP and access to Brevo's deliverability team. BIG BOX SMTP Relay Standard at €399/month for equivalent volume with dedicated IP included = €4,788 annual. BIG BOX wins by approximately €3,000 annual and on deliverability. The all-in-one platform features the customer was paying for at lower Brevo tiers — CRM, automation, SMS — are largely de-emphasised in Brevo's Professional tier, so the consolidation argument that justified Brevo at SMB volume weakens.

Scenario C: 5M monthly email, e-commerce platform, EU-only with sector regulator compliance. Brevo Enterprise at custom pricing, typically $8,000-15,000 monthly for 5M volume with multi-year commit and multiple dedicated IPs. BIG BOX managed KumoMTA dedicated at €1,299-€2,499/month depending on resource requirements = €15,588-€29,988 annual. BIG BOX wins decisively on cost (typically 50-70% below Brevo at this band) and on architectural fit. At enterprise volume, the customer typically has internal deliverability expertise and wants the operational control that Brevo's abstracted platform does not provide. The all-in-one features become liabilities rather than assets at this scale.

The 88.3% inbox-placement figure comes from EmailToolTester's January 2024 quarterly seedlist study. The methodology seeds known accounts on Gmail, Outlook, Yahoo, AOL plus several European webmail providers and a regional mix, then measures placement. The 88.3% places Brevo near the category median for shared-pool ESPs and meaningfully below dedicated-infrastructure providers. Subsequent quarterly measurements through 2024-2025 have varied between 84% and 91% depending on which receiver mix dominates the measurement and which Brevo IP pool the test traffic landed on.

The variance is the more interesting number than the absolute level. Brevo, like every shared-pool ESP, exhibits temporal reputation variance: pool placement degrades when one or more senders in the pool experience an engagement crash, then recovers as the offending sender is rotated out. For senders whose business model can absorb a 3-8 percentage point inbox-placement drop for hours-to-days at unpredictable intervals, the variance is acceptable. For senders whose business model maps each percentage point of inbox placement to revenue, the variance is unacceptable regardless of the average level.

Two operational examples from our 2025 customer notes. A French B2B SaaS migrated 80K monthly transactional traffic from Brevo's shared infrastructure to our dedicated SMTP Relay Standard. The migration produced a measured 6.4 percentage point inbox-placement improvement on transactional traffic, which translated to a 12% reduction in support tickets categorised as "verification email not received." A second customer, an EU-based fintech sending 200K monthly mixed traffic, migrated from Brevo Professional to our SMTP Relay Standard. The migration produced a 5.1 percentage point inbox improvement on transactional plus a 3.8 percentage point improvement on marketing, with the marketing improvement converting to approximately 0.4 percentage points of email-driven revenue uplift attributable to the higher inbox rate.

These specific numbers will not generalise to every customer. The pattern — inbox placement of dedicated-IP managed infrastructure tracks 4-8 percentage points above shared-pool platforms at equivalent sender hygiene — is consistent across our customer base. The question for each evaluation is whether the percentage-point improvement is worth the cost differential, which depends on the customer's specific revenue model and traffic mix.

Brevo is a French S.A. headquartered in Paris, subject to French data protection law and CNIL supervision. Production infrastructure runs across EU data centres in France plus Germany plus Belgium. The sub-processor list is shorter than US-origin alternatives. The DPA is straightforward and standardised. For the majority of EU procurement processes, Brevo's jurisdictional posture clears the bar without requiring custom contractual work.

The gap appears at the regulator-audit layer. Sector regulators — BaFin for German financial services, ACPR for French financial services, FINMA for Swiss financial services, HDS-supervised authorities for French healthcare, AEPD for Spanish public-sector processing — increasingly require detailed processor disclosures that go beyond standard GDPR Article 28 requirements. The specific questions vary by regulator but typically include: which exact data centre handles which workload, what the chain of custody for personal data is during incident response, what the sub-processor exit-and-replacement procedure looks like, what the contractual mechanism is for ensuring processor commitments survive ownership change.

Brevo, as a 600,000-customer platform with a standardised DPA, accommodates these questions at the standard-response level. Detailed custom responses require enterprise-tier engagement and are negotiated case-by-case. The response timelines for sector-regulator-driven custom questions tend to extend into multi-week windows, which procurement teams under regulatory pressure find frustrating.

Our processor structure operates differently. Single-product business, smaller customer base (single-digit thousands rather than hundreds of thousands), named compliance owners (Mikael for technical compliance, [email protected] for data-protection questions). Custom DPA Annex II provisions are negotiated routinely. Sub-processor chains are documented at per-jurisdiction depth. The response timeline for sector-regulator-driven questions is typically 48-72 hours rather than multi-week. For workloads under active regulator pressure, this responsiveness is the operational difference that matters.

For workloads not under active regulator pressure, Brevo's standardised posture is adequate and arguably preferable — standardisation produces predictability. The choice is regulator-driven rather than ideologically-driven; both vendors clear most EU procurement requirements.

The technical migration follows the standard five-phase parallel-sending pattern. Phase 1 provisions DKIM keys and updates SPF to include both Brevo's spf.brevo.com and our spf.bigboxhosting.com. Phase 2 routes 10% of traffic through BIG BOX. Phase 3 scales to 50%-70%. Phase 4 cuts over fully. Phase 5 decommissions Brevo. Total elapsed time 4-6 weeks, zero application downtime, 4-8 hours of client team effort.

The Brevo-specific advantages for migration: most Brevo customers are on monthly plans rather than annual commitments, so cancellation is straightforward and there is no contract-runout overhead. The Brevo API exports for suppression lists, transactional templates and contact-attribute schemas are well-documented and import cleanly to our infrastructure. The Brevo customer-support team accommodates volume reductions during migration without friction.

The Brevo-specific complications: customers using Brevo's all-in-one features (CRM, marketing automation, SMS, landing pages) cannot migrate those workflows to us because we do not offer equivalent functionality. Customers in this position typically split the migration: keep Brevo for CRM, automation plus SMS plus landing pages; move email infrastructure to BIG BOX. The two-vendor outcome can be operationally adequate or operationally awkward depending on how tightly integrated the all-in-one features were in the original Brevo setup. We are direct with prospects in this situation: if the all-in-one consolidation was a primary reason for choosing Brevo originally, the migration math may not work.

For customers using Brevo primarily for email infrastructure and incidentally for the all-in-one features, the migration is clean. For customers deeply integrated into Brevo's marketing-automation and CRM layers, the migration is a partial split that requires careful workflow audit before commitment.

Question one: do you genuinely need an all-in-one platform that includes email plus SMS plus WhatsApp plus CRM plus marketing automation under one vendor? If yes, Brevo is one of the strongest options in this category and worth strong consideration. The platform breadth is real and the consolidation produces operational simplification.

Question two: is your monthly volume below 100K, marketing-led, with moderate deliverability tolerance? If yes, Brevo's pricing is favourable and the deliverability variability is absorbable. We will not push to compete in this profile unless other factors (regulator audit, transactional criticality) make the deliverability premium worthwhile.

Question three: is your volume above 200K monthly, your traffic transactional-critical, or your sector regulator requires custom Annex II provisions? If yes, BIG BOX. The deliverability gap becomes binding at this volume, the all-in-one features matter less because customer maturity at this band typically means dedicated marketing-ops tools rather than bundled platform features, and the custom compliance posture is operationally important.

The conversation we recommend is a 30-minute scoping call with an engineer who has run Brevo migrations. We will model your traffic and tell you whether the migration math works at your volume. If Brevo is the right answer for your profile, we will say so and refer you back to them.