Brevo alternatives: 6 options compared

Compare recorded free and open-source options, their capabilities and operating requirements. Source dates are shown below; licenses, hosted limits and project activity can change.

brevo $9/mo→compare free options KINDAcan I vibecode it? the honest breakdown →📮 newsletters

what to keep, change or build

People still pay for Brevo because newsletter operators pay for inbox placement, growth mechanics, and operational confidence on publication day. The recurring cost buys DNS authentication, reputation, bounces, complaints, unsubscribe compliance, templates, queues, analytics, backups, and support, not just the visible interface.

The scoped build: Collect subscribers with clear consent records, compose and send a low-volume newsletter and transactional messages, publish a web archive, and report basic delivery and click events. The guide makes a conditional build assessment. Its requirements and technical boundaries determine whether a DIY version fits.

Do not assume parity: deliverability infrastructure, multichannel messaging, CRM, automation, and support; inbox-placement expertise; advanced automations; commerce integrations; recommendation and ad networks.

Ongoing work: DNS authentication, reputation, bounces, complaints, unsubscribe compliance, templates, queues, analytics, backups, and support.

Read the Brevo implementation scope, requirements and prompt →

shortlist by the workflow you need

Control the deployment: listmonk, Plunk, Notifuse. Include updates, backups and service operations in the decision.

Start with a managed service: Brevo Free, Loops Free, Sender Free. Check the current free tier, data export and paid feature boundaries.

Before asking AI to rebuild an alternative: compare its documented install, engine and storage requirements below. Extending an existing project may save implementation work when its license allows it; a desktop workflow or free hosted tier alone does not establish that the software is easy to recreate. Use the linked product details and build guide to check the smaller scope.

listmonkopen sourcewebself-hosteddocker to self-host

Fast campaigns plus a transactional API and explicit subscriber states; the visual polish is utilitarian.

licenseAGPL-3.0

runsyour server

installDocker Compose or a single release binary plus PostgreSQL

dataSubscribers, campaigns, templates, and analytics live in a PostgreSQL database on your server.

the catch vs Brevolistmonk is fast and explicit about subscriber states, but it lacks Brevo's managed deliverability, broad automation suite, CRM-style contact tools, and polished visual workflow builder.

setupYou still need a PostgreSQL database and a trustworthy SMTP/API sender with authenticated DNS.

recorded source check 2026-08-10 · installation not tested

Plunkopen sourcewebself-hosteddocker to self-host

Transactional and campaign email with workflows; self-hosting is free, sending is not magic.

licenseAGPL-3.0

runsyour machine or their cloud

installHosted signup or Docker Compose

dataSelf-hosted data lives in PostgreSQL, queues in Redis, and uploads in bundled MinIO or another S3-compatible store.

the catch vs BrevoPlunk handles both transactional and campaign email, but self-hosting its multi-service stack and configuring SES is much less turnkey than Brevo's managed sending and compliance workflow.

setupThe self-host path needs Docker, several subdomains, DNS/TLS, and an AWS SES account with credentials and domain verification.

recorded source check 2026-08-10 · installation not tested

Notifuseopen sourcewebself-hosteddocker to self-host

Campaigns, transactional API and subscription records in one compose stack; delivery still needs an SMTP provider.

licenseAGPL-3.0

runsyour machine or their cloud

installNotifuse Cloud signup or self-host with Docker

dataSelf-hosted contact, campaign, event, and analytics data lives in PostgreSQL; uploaded assets use S3-compatible storage.

the catch vs BrevoNotifuse can hold contacts, campaigns, and transactional events, but you must supply and operate the hosting, object storage, and actual mail-delivery provider that Brevo bundles.

setupSelf-hosting needs Docker, PostgreSQL, object storage, a public domain, and a separately configured SMTP or email API provider.

recorded source check 2026-08-10 · installation not tested

Brevo Freefree optionwebthey host it

The vendor's own free tier does newsletters and transactional mail; 300 messages a day is the small print.

licenseproprietary, free

runstheir cloud

installHosted signup

dataContacts, campaigns, consent records, and message events live in Brevo's cloud; contacts can be exported as CSV.

the catch vs BrevoBrevo Free keeps the same product and consent records, but the 300-message daily cap, Brevo branding, and paid-gated reporting and automation limits are the tradeoff.

setupAuthenticating a custom sending domain requires adding DNS records.

recorded source check 2026-08-10 · installation not tested

Loops Freefree optionwebthey host it

Marketing and transactional email share one hosted account; the free ceiling is 1,000 contacts.

licenseproprietary, free

runstheir cloud

installHosted signup

dataContacts, custom properties, events, workflows, and message history live in Loops' cloud; contacts can be imported/exported as CSV.

the catch vs BrevoLoops Free unifies marketing and transactional email, but its 1,000-contact and 4,000-email rolling limits are tighter and its consent/list-management surface is narrower than Brevo's.

setupYou must authenticate a sending domain and instrument your app or API before lifecycle emails become useful.

recorded source check 2026-08-10 · installation not tested

Sender Freefree optionwebthey host it

Newsletters, transactional email and consent-friendly lists with 15,000 monthly sends; one seat means one cook.

licenseproprietary, free

runstheir cloud

installHosted signup

dataSubscribers, campaigns, automations, and engagement events live in Sender's cloud; subscriber data can be exported.

the catch vs BrevoSender Free covers the core hosted job, but one free user, vendor branding, and its contact/send ceilings make collaboration and growth weaker than Brevo.

setupA custom sending domain must be verified with DNS records for reliable delivery.

recorded source check 2026-08-10 · installation not tested

latest recorded source check 2026-08-10 · check current terms at the source

choose by workflow and operating requirements

Use the recorded scenario and feature gaps to choose a shortlist. Open-source code can still require hosting, storage, model APIs or paid services; a free tier can limit features.

toollicense / editionrunning itplatformsstarsactive
listmonk detailsAGPL-3.0docker to self-hostweb, self-hosted22,6002026-07
Plunk detailsAGPL-3.0docker to self-hostweb, self-hosted5,3002026-08
Notifuse detailsAGPL-3.0docker to self-hostweb, self-hosted2,0382026-08
Brevo Free detailsproprietary, freethey host itweb——
Loops Free detailsproprietary, freethey host itweb——
Sender Free detailsproprietary, freethey host itweb——
Considering a DIY version? Read the build scope, implementation prompt and trade-offs.get the prompt →
why people still pay for Brevo

People still pay for Brevo because newsletter operators pay for inbox placement, growth mechanics, and operational confidence on publication day. The recurring cost buys DNS authentication, reputation, bounces, complaints, unsubscribe compliance, templates, queues, analytics, backups, and support, not just the visible interface. The recorded subscription totals $108 a year before any costs of an alternative.

Questions about these alternatives

Is there a free alternative to Brevo?

The catalogue lists listmonk, Plunk, Notifuse and 3 more. Compare the specific free edition, license, hosting costs and current availability before choosing; a listing does not promise that every feature is free.

Should I just build my own Brevo?

Our verdict is KINDA. The core loop is buildable, but a dependable replacement becomes a real weekend or multi-day project. For Brevo, send a low-volume newsletter and transactional messages with clear consent records. The hard boundary is deliverability infrastructure, multichannel messaging, crm, automation, and support, plus deliverability, growth network, and integrations. Review the scope, implementation prompt and trade-offs in the Brevo build guide.

Every week, more subscriptions die.

New verdicts, new prompts, the week's most-doomed apps.
One email. Unsubscribe in one click.

free forever · no scanner spam · the prompt stays on the site, the deaths come to you

$weekly: what got a verdict, what died.