Brevo Pricing Guide for 2026

Who this guide is for

This guide is for the budget-minded operator who has to make one subscription cover a broad, shallow email program: the generalist running newsletters, welcome flows, receipts, and the occasional campaign without a specialist on staff. It fits founders comparing a $9 entry step against a $19 one, nonprofits and clubs where every line item is defended, European teams with data-region preferences, and small commerce sellers who want cart recovery without a commerce-platform premium.

It also serves the buyer who needs the caps explained rather than the features listed. Brevo's pricing is unusually forgiving on one axis — stored contacts barely matter — and unusually constraining on others: a daily sending ceiling on free, monthly volume allowances on paid tiers, and feature gates that reserve automation depth for higher steps. Knowing which of those will bind first is the entire decision, and that is what the sections below map with verified figures from September 17, 2026.

Brevo's numbers are presented neutrally so the budget tradeoff can be judged on its own merits. Start from the pricing index if you want the whole field before this single vendor.

Read this guide closely if

• Raw monthly cost is a genuine constraint rather than a negotiating posture.
• One generalist owns campaigns, automation, transactional integration, and list hygiene together.
• Your program is broad but shallow: newsletters plus welcome flows plus receipts, without billing-event orchestration.
• Sending volume — not contact storage — is the number you can actually forecast.
• You want a real free tier to validate on before any card is involved.
• Multi-channel breadth (email, SMS, chat, lightweight CRM) should live under one login and one bill.

Look elsewhere first if

• Failed-payment dunning and plan-change onboarding are the core of your lifecycle program.
• Deep multi-step automation is required from day one rather than at the Standard step.
• Multi-reviewer approval workflows need separate seats below the Professional tier.
• Native MCP or CLI agent operation is a launch requirement rather than a later wish.

Those exclusions describe shape, not quality. Brevo is the right answer for a large class of senders precisely because it refuses to charge them for capabilities they will not use — the trade being that teams who eventually need those capabilities step up or move on.

The billing model in one paragraph

Brevo sells monthly email volume allowances in stepped plans rather than charging per stored contact, which makes it unusually forgiving for teams with large, messy lists. A startup can import ten thousand legacy contacts, keep every dormant trial for analysis, and pay only for the sending tier it actually uses. That volume-based shape is the core reason Brevo appears as the budget pick in our comparison: the bill tracks activity, not database size, so list growth never triggers a pricing ambush.

Two structural details complete the model. First, transactional email features including RESTful APIs, SMTP relay, outbound webhooks, and unlimited log retention are available on all plans, so receipts and notifications never force a second vendor contract. Second, a pay-as-you-go credit plan exists for infrequent senders, where one email sent deducts one credit and unused credits do not expire, which suits seasonal businesses and quarterly newsletters far better than a monthly subscription ticking away between sends.

Pricing geometry explained

Brevo sells stepped monthly volume allowances rather than contact tiers, which places it in a distinct geometric family: the bill moves with what you send, not with what you store, and the steps are coarse enough that forecasting means matching your program to a named plan rather than computing a continuous rate. A large, messy, dormant-laden database is close to free to keep here; the question that actually moves cost is which volume step your monthly sending lands in.

The free tier adds a second geometric feature that paid plans do not share: a daily cap rather than a monthly one. Three hundred emails per day constrains shape as much as size — steady small sending fits comfortably, while one large broadcast can exhaust a day's allowance regardless of how light the rest of the month is. Teams used to monthly pools should relearn the rhythm, because a daily meter punishes lumpiness and rewards cadence.

Paid plans return to monthly logic, and the step boundaries are where the money is. The verified anchors — free at 300 per day, Starter at $9, Standard at $18, Professional at $499 beginning from 150,000 emails per month — span a wide range, and the jumps between them buy both volume and capability rather than volume alone. That bundling is important: crossing a step changes what the platform will let you build, not only how much it will let you send.

For a growing list, the geometry is unusually kind. Contacts are not metered on any published tier, so signups, imports, and dormant trials never trigger a price change on their own. The bill reacts when those contacts are mailed in aggregate — which is the honest version of the deal, since it aligns cost with the activity that actually carries deliverability risk.

What a growing list does to the bill

Because storage is free, list growth is financially inert until sending catches up. A database can triple while the invoice stays on the same step, provided the team does not triple its cadence alongside it. The discipline therefore shifts entirely to send planning: map every program to monthly volume first — onboarding sequences multiplied by trial starts, newsletters multiplied by list size, plus transactional receipts — and let that sum choose the tier.

The trap is capability rather than volume. A team can sit comfortably inside a Starter allowance and still be blocked from the multi-step automation that Standard unlocks, or from the seats, scoring, and specialist support that Professional adds. Growth plans should therefore track two curves — monthly sends and required capability — because the cheaper of the two steps is irrelevant if the program needs the other one.

Read the fourth row carefully, because it is the one most often missed in comparisons: crossing from Starter to Standard is a capability purchase as much as a volume one, and the same is true of the leap to Professional. Budget decisions framed only around sends will mis-price the moment a team needs automation depth, seats, or scoring.

The eighth row marks the edge of self-serve economics. Below a million contacts and above the published volume bands, pricing becomes a conversation; inside them, every figure in this table was verified on the official page on September 17, 2026, and should be re-checked there before it enters a budget.

Plan tiers, verified

The free plan is a genuine evaluation tier, not a demo shell: up to 300 emails per day once the account is approved for sending, with contact storage, forms, templates, basic automation shapes, and transactional API access included. A solo founder can run welcome mail, a small newsletter, and password resets for weeks before paying anything. The daily cap is the binding constraint, so a launch spike or a single large broadcast will hit the ceiling fast, which is exactly the moment the paid steps are designed for.

Starter at $9 per month is the entry paid step for single users beginning with email and multi-channel marketing, raising the monthly email allowance from 5,000 emails per month upward depending on configuration, and adding the drag-and-drop editor, AI content generation, advanced segmentation, forms, and basic reporting without the Brevo logo. Standard at $18 per month is the most popular step, layering everything in Starter plus unlimited multi-step marketing automation workflows, A/B testing, advanced reporting with heatmaps and geography, AI send-time optimization, web and event tracking, and a landing page. Professional at $499 per month targets teams using data and AI across channels, starting from 150,000 emails per month with WhatsApp, push, and popup channels, ten included seats, contact scoring with RFM and lifetime-value models, AI segmentation and a plain-language data analyst, phone support, and three hours per year of deliverability specialist support.

Enterprise pricing is custom for companies with one million-plus contacts, adding multi-account management, custom objects, a custom loyalty engine, dedicated IP, single sign-on, tailored onboarding, and recurring strategic support. Teams choosing between monthly and yearly commitment should note the page shows a yearly billing toggle, so annual prepayment terms are worth confirming at checkout for an additional discount.

Limits, overages, and the fine print

Brevo's limits are volume-shaped, so forecasting means modeling sends rather than contacts. Map every program to monthly sends first: onboarding sequences multiplied by trial starts, newsletters multiplied by list size, plus transactional receipts and notifications. SMS is metered separately with credits sold apart from email allowances, so any program mixing channels must budget two meters, a discipline our discussion scenarios on cost attribution explore in depth.

The pay-as-you-go path deserves attention from irregular senders. Because one email equals one credit deducted and credits do not expire, a business sending quarterly product updates pays only for send months and wastes nothing between them. Cancellation works the same forgiving way: plans can be cancelled at any time from the account, with data stored for a potential return or deleted on request. Payments run by card or PayPal on thirty-day subscription periods, with statements available in-account.

Hidden fees and fine print

Brevo's fine print is concentrated in a handful of gates rather than scattered across overage tables, which makes it unusually easy to audit in one sitting. The items below are the ones that most often reshape an invoice or a roadmap after signing, ordered by how frequently they surprise teams.

The daily cap on free

Three hundred emails per day is a genuine allowance measured monthly — roughly nine thousand sends if every day runs at the ceiling — but a fragile one measured against campaigns. One announcement to a five-hundred-person list, one launch-day signup surge, or one re-send to non-openers can consume a day's budget before the afternoon, after which the platform simply has no more free capacity until the clock resets.

The operational answer is scheduling discipline rather than plan gymnastics: spread broadcasts across days, time launches for early morning inside the cap, and treat any single send expected to exceed a third of the daily allowance as a reason to have already moved to a paid step. Discovering the cap during a launch is the expensive way to learn it.

Automation gated at Standard

Starter at $9 covers single-user sending with the basics, but unlimited multi-step marketing automation workflows, A/B testing, advanced reporting with heatmaps, send-time optimization, web and event tracking, and a landing page arrive with Standard at $18. For a team whose welcome flow is already branching, the effective entry price is therefore the Standard figure rather than the Starter one, and forecasts built on $9 will need correction.

Professional at $499 is the larger gate: contact scoring with RFM and lifetime-value models, AI segmentation and a plain-language data analyst, WhatsApp, push and popup channels, ten included seats, phone support, and three hours per year of deliverability specialist support, starting from 150,000 emails per month. Nothing about that step is incremental — it is a different operating model — and teams should plan for it deliberately or consciously stay below its capability line.

SMS and channels as separate meters

SMS is metered separately with credits sold apart from email allowances, so any program mixing channels is budgeting two meters by definition. Chat, CRM, and popup features fold into the same login but not necessarily the same cost logic, which is why multi-channel forecasts need a per-channel line rather than a single email number with add-ons assumed inside.

The same applies to pay-as-you-go credits, which are elegant for irregular senders — one email deducts one credit, unused credits do not expire — but a poor substitute for a monthly allowance at steady volume. Choose between the two structures deliberately: credits for seasonal rhythm, plans for continuous sending.

Seats, support, and the Enterprise boundary

Ten included seats arrive at Professional, which means multi-reviewer approval workflows on lower tiers depend on shared logins or a thinner separation of duties — an uncomfortable trade for teams running agent-assisted operations where audit attribution matters. Deliverability specialist support likewise begins at Professional, with a stated annual allotment of three hours, and dedicated IP, single sign-on, multi-account management, custom objects, and tailored onboarding sit beyond the Enterprise boundary at custom pricing for companies with one million-plus contacts.

Enterprise terms, annual prepayment discounts behind the page's yearly billing toggle, and any regional tax treatment were not all rendered in our source set; confirm each live. The honest summary is that Brevo's headline steps are exactly as advertised, and the genuine fine print lives in which capability — automation depth, seats, specialist hours, dedicated infrastructure — arrives at which step.

A pre-signing checklist

• Estimate monthly sends per program, then confirm the target tier's allowance on the live page rather than from memory.
• Schedule any launch-sized broadcast against the free daily cap, or move to a paid step first.
• Confirm which tier carries the automation depth your existing welcome and winback flows require.
• Count human approvers separately from senders, and check seat inclusion at each tier.
• Budget SMS credits as a second meter wherever the program mixes channels.
• Compare pay-as-you-go credits against plan allowances using your actual seasonal rhythm.
• Re-verify every figure at Brevo pricing on decision day — all figures here were verified September 17, 2026.

What the free tier really proves

The free 300-per-day allowance is enough to validate the entire loop that matters: connect a domain, import contacts, build a welcome automation, send a newsletter, and fire transactional mail through the API. Two hundred daily trial signups each receiving a short onboarding sequence fit comfortably, leaving headroom for a weekly broadcast to a small list. Because transactional features ship on every plan, developers can integrate the API during the free phase without worrying that sending primitives will vanish behind a paywall later.

The honest boundary is deliverability operations at scale. Dedicated IPs, specialist support hours, and advanced reputation tooling live on Professional and Enterprise, so a team graduating past roughly a hundred thousand monthly sends should budget the Professional step rather than stretching Standard past its comfort zone. Agent-run programs should also note that ten seats arrive only at Professional, so multi-reviewer approval workflows on lower tiers need to share logins or accept thinner separation of duties.

Cost scenarios: three monthly invoices

These three months use only figures verified in this guide and the pricing index: free at 300 emails per day, Starter at $9, Standard at $18, and Professional at $499 beginning from 150,000 emails per month. Contacts appear in every row precisely because they never change the total.

Month two: steady state on free

A small business sends an average of 180 emails daily — a welcome flow, one weekly newsletter, and transactional mail — totaling roughly 5,400 for the month, while holding 4,000 stored contacts of which only a fraction are ever mailed. Daily sending never approaches the 300 cap, and the invoice is zero dollars.

The stored contacts are the point: the same 4,000 records on a per-contact tier would already be a line item, while here they sit free until the day someone decides to mail them. Keep the rhythm steady and this month can last indefinitely — the constraint is shape, not size.

Month six: a campaign breaks the cap

Monthly sending climbs to about 7,200 as a product announcement reaches the full list in one 1,200-recipient broadcast alongside the usual daily flow. The broadcast cannot run on the free daily cap, so the account moves to a paid step: Starter at $9 with an allowance configured above 5,000 emails per month, per the verified tier description.

If the same month introduces a branching welcome flow rather than a linear one, the required step is Standard at $18 instead, because unlimited multi-step automation begins there. The difference between the two invoices is nine dollars; the difference in what the team is permitted to build is the entire automation canvas — which is why capability, not volume, usually decides this month.

Month twelve: professional-scale volume

The program now sends about 160,000 emails monthly across lifecycle, campaigns, and transactional streams, which lands above the 150,000-email starting point of Professional at $499 per month. That step carries ten included seats, contact scoring, advanced reporting, additional channels, phone support, and deliverability specialist hours alongside the volume.

The invoice is an order of magnitude above the earlier months, and the honest reading is that this is no longer a budget tool decision — it is an operations decision. Before taking it, compare the same 160,000 sends against pooled alternatives and against Resend's transactional slider, which read $90 for Scale at 100,000 emails and $160 at 200,000 on October 7, 2026 (read the slider at resend.com/pricing for 160,000 itself), then decide what the extra Brevo capabilities are worth to your specific team rather than to the category.

The single most useful column is stored contacts: it grows in every scenario and never appears in the total. That is Brevo's structural advantage in one table, and the reason this vendor survives comparison against tools whose bills move with every signup regardless of sending.

Set beside the wider verified set — Loops free 1,000 contacts with 4,000 sends and Mailgun Basic at $15 per 10,000 — Brevo's shape reads as the volume-stepped budget option, which is exactly the position it occupies in this site's comparison.

Who Brevo is for

Brevo fits cost-sensitive generalists: the two-person startup where one founder runs campaigns, automation, transactional integration, and CRM hygiene alone. It fits European teams with data-region preferences, nonprofits and clubs on tight budgets, and any business whose email program is broad but shallow, meaning newsletters plus welcome flows plus receipts without deep billing-event orchestration. E-commerce sellers get cart recovery and coupon tooling without a commerce-platform premium.

Brevo is a weaker fit for SaaS teams whose core workflows are billing-triggered. Failed-payment recovery, trial-expiry conversion, and plan-change onboarding need middleware or custom glue on Brevo where they arrive natively elsewhere. Data-heavy scale-ups wanting warehouse-driven journeys and multi-channel orchestration will also outgrow the Standard canvas and should compare Customer.io through our Customer.io pricing guide before committing.

Agent and MCP fit

Agents operate Brevo through its conventional REST API and SMTP relay rather than a native MCP server, which shapes the governance story. Routine work such as audience audits, segment exports, campaign drafts, and delivery checks can be scripted or agent-assisted, but every flow needs custom tooling and scoped API keys instead of a governed protocol. Approval discipline therefore lives in team process rather than platform primitives: require agents to propose segments and drafts, keep bulk-send approval human, and log every agent API call for the audit practices our discussion scenarios detail.

The AI features inside Brevo itself, content generation, send-time optimization, and AI segmentation, reduce drafting toil without replacing supervision. Treat them as junior-drafter assistance inside the same supervised sending pipeline from our 15-tool comparison: agents draft, humans approve, delivery carries one reputation, and attribution closes the loop.

Where Brevo fits

Brevo wins raw budget breadth for newsletters, receipts, SMS, chat, and CRM in one general-purpose subscription. Teams whose transactional reliability is the top risk should compare the developer APIs in our Resend guide, while journey complexity points to Customer.io.

How Brevo fits SaaS budgets

Brevo charges stepped monthly volume with contacts free and capability bundled by tier. SaaS teams should check whether processor events, lifecycle triggers, and agent controls require a second system before choosing it as the generalist foundation.

On raw budget, Brevo wins the early months convincingly. Free at 300 per day and a Starter step at $9 undercut almost every alternative in this comparison set, and a pre-revenue product sending steady small volume can operate for a long time without a bill. The pooled alternative's free tier is also real — 2,500 emails per month — but once volume climbs, the arithmetic of your specific cadence decides which structure is cheaper rather than any categorical rule.

Where the comparison shifts is lifecycle depth. Failed payments, trial expiries, and plan changes are the events that most directly move SaaS revenue, and they arrive natively in the pooled model while requiring middleware or custom glue on Brevo. That integration is buildable — competent engineers build it routinely — but it is also owned, maintained, and quietly deprecated by whoever wrote it, and that recurring cost belongs beside the subscription in any honest comparison.

The agent-operation dimension separates further. Brevo is reachable through a conventional REST API and SMTP relay with custom tooling and scoped keys; the pooled alternative publishes an MCP server, CLI, and API for governed assistant operation from the same account. Teams planning to run campaign work with AI assistance under approval gates should weigh that difference heavily, because building an equivalent governance layer is possible but is a project rather than a setting.

Where each one earns its place

Brevo is the right call for broad, shallow programs run by one generalist: newsletters, welcome flows, receipts, and light commerce messaging, where budget discipline dominates and billing-event orchestration is not yet the constraint. Its multi-channel breadth under one login adds genuine value for teams that would otherwise hold email, SMS, and chat subscriptions separately.

A billing-native lifecycle platform is the right next step once subscription events become daily work and the contact database outgrows engagement. The migration logic usually runs in that direction — Brevo first for breadth, then lifecycle onto a specialist when triggers start mattering.

A fair decision sequence

• Price your next twelve months on Brevo's verified steps using your own send forecast.
• Add the middleware build-and-maintain cost to the Brevo total wherever billing triggers are required.
• Add the seat and approval-gate requirements below Professional to the Brevo total where multi-reviewer governance matters.
• Decide whether SMS and chat under one login genuinely replace separate subscriptions you would otherwise buy.
• Before choosing Brevo, check the current rate card and compare its daily cap with your launch calendar; this guide is a September 2026 snapshot.

The arithmetic above is the useful part — each side priced from its own verified figures, each structural difference named rather than glossed, and each team left to apply it to a real forecast instead of a category average.

Brevo questions and answers

What does Brevo actually cost?

The verified steps are free at 300 emails per day, Starter at $9 per month, Standard at $18 per month, and Professional at $499 per month beginning from 150,000 emails, with Enterprise custom above that and a pay-as-you-go credit option alongside.

Are stored contacts charged for?

Not on any published tier — Brevo meters sending volume rather than database size, so imports, dormant trials, and legacy lists do not raise the bill on their own.

What does the free tier really allow?

Up to 300 emails per day once the account is approved for sending, with contact storage, forms, templates, basic automation shapes, and transactional API access included — a genuine evaluation tier rather than a demo shell.

Which features are gated to higher tiers?

Unlimited multi-step automation, A/B testing, advanced reporting, send-time optimization, event tracking, and a landing page arrive with Standard at $18; contact scoring, additional channels, ten seats, phone support, and specialist deliverability hours arrive with Professional at $499.

How does pay-as-you-go compare with a plan?

Credits suit irregular senders: one email deducts one credit and unused credits never expire, so a business sending quarterly updates pays only for send months.

How does Brevo compare with pooled, contact-unlimited pricing?

Pooled models charge one meter for everything; compare that geometry with Brevo's stepped volume and the integration work required for billing triggers.

Verdict and checklist

Choose Brevo when budget discipline dominates, one generalist runs the whole program, and billing-trigger depth is not yet the constraint. Validate on the free 300-per-day tier, step to Starter at $9 or Standard at $18 as volume demands, reserve Professional at $499 for data-led multi-channel scale, and use pay-as-you-go credits for seasonal rhythms. Re-verify every figure at Brevo pricing, then return to the pricing index for the full verified set.

A sensible thirty-day plan

The sequence below gets every gate observed before it can reshape a roadmap, and it works whether the account is brand new or migrating from another budget tool.

• Day one: connect the domain, verify sending approval, and instrument a weekly sends-versus-cap dashboard.
• Day three: import contacts with suppression applied first, since storage is free but reputation is not.
• Week one: ship one welcome flow and one transactional stream, both human-approved before first send.
• Week two: measure average daily sends against the 300 free ceiling and forecast the launch-day peak.
• Week two: confirm which tier carries the automation depth your branching flows actually need.
• Week three: run one broadcast sized against the daily cap, and move to a paid step before it, not during it.
• Week three: count human approvers and check seat inclusion if multi-reviewer governance is required.
• Week four: price twelve months on Starter and Standard against the pooled anchors in the pricing index.
• Week four: budget SMS credits separately wherever the program mixes channels.
• Day thirty: re-read the live pricing page, then commit to the tier your forecast supports rather than the one your hope does.

Signals it is time to change the model

Three signals recur across teams that outgrow budget-stepped pricing: billing events become daily work and the middleware glue starts failing quietly; the stored database grows faster than engagement and the absence of a contact meter stops being an advantage worth having; or agent-run operations demand governed MCP-grade access and approval primitives that a conventional REST API cannot provide on its own.

None of these signals is an emergency, and none requires a dramatic migration. They are invitations to re-run the comparison with fresh numbers — the same comparison this guide has tried to make fair in both directions — and to move lifecycle work deliberately rather than by accumulated exception.

Mistakes that surface in the first invoices

The first is sizing a plan from monthly volume alone and discovering that the required automation depth sits one tier higher — cheap to avoid, since confirming the feature gate takes a single read of the live page before purchase.

The second is scheduling a launch-sized broadcast onto the free daily cap, trading a nine-dollar plan step for a throttled signup flow on the highest-visibility day of the quarter.

The third is treating pay-as-you-go credits as a discount rather than as a structure: they reward irregular senders and quietly penalize steady ones, because the comparison that matters is against your real cadence rather than your best-case month.

Each of these is visible in advance with the three numbers this guide asks you to track — monthly sends, automation requirements, and human approvers — reviewed together rather than in isolation whenever the program changes shape.

For the wider decision set, begin at the pricing index to place Brevo's steps beside every other verified vendor, read the 15-tool comparison for positioning context and ranking method, and take the operating questions — approval chains, staging discipline, cost attribution per agent run — into the discussion threads, where thirty-eight scenarios test governance before it becomes an incident.

For a useful next comparison, read Loops when a small SaaS audience matters more than send volume, Resend when engineers need separate transactional and automation meters, Customer.io when behavioral branching drives the program, and Postmark when delivery traceability is the buying criterion.

The closing discipline does not change with vendor: forecast your own sends, keep suppression tight, gate consequential mail behind a human, and let the live pricing page overrule every guide — including this one — at the moment you actually pay.

Keep the source links beside each figure while you read, and hold the arithmetic to the same standard across every guide in the set.

Open pricing index