Open Source Brevo Alternatives

listmonk is a standalone newsletter and mailing list manager you host yourself, packed into a single binary that uses a PostgreSQL database as its data store.

The backend is written in Go and the frontend in Vue with Buefy, which is why the whole application arrives as one executable rather than a set of services to wire together. A live demo is published for anyone who wants to click around before committing to an install.

Getting it running takes one of two routes.

• Docker: pull the latest image from Docker Hub and start the sample compose file with one command.
• Binary: download a release, extract the executable and run it directly on the host.
• Configuration: a new-config flag generates the config file you edit before first run.
• Database setup: an install flag prepares the Postgres schema, and an upgrade flag migrates an existing one.
• Idempotent upgrades: running an upgrade more than once has no side effects.

Either path leaves the admin interface waiting on port 9000. listmonk is free software under AGPLv3, and the project publishes a developer setup guide for anyone who wants to work on it rather than only run it.

Mautic is the largest open source marketing automation project, and it exists so an organization can run integrated campaigns without renting a platform to do it. Contacts, segments and campaign history live in a database you administer, on a server you control.

The project frames its aim as being the most privacy-focused, accessible and extendable marketing automation product on the market. It was verified as a Digital Public Good in 2024, and both the frontend and the backend are meant to be customized rather than merely configured.

What that self-hosted position actually buys is worth being specific about.

• No third-party dependency: campaigns run on infrastructure you own instead of a vendor SaaS.
• Data ownership: contact records and campaign history sit in your own database.
• No vendor lock-in: the software can be modified, extended or left behind at will.
• Unlimited segmentation: segments and automation are not capped by a pricing tier.
• Multi-channel reach: additional channels arrive without additional cost.
• Custom integrations: anything the project does not ship can be built against it.

Installing with Composer is the recommended route, and a prepackaged production download exists for anyone who would rather stay away from the command line. A DDEV configuration ships in the repository, so a single start command runs the first-run process and configures the application automatically.

One caution from the maintainers deserves repeating. Source outside a tagged release should be treated as alpha and kept out of production, where a schema drifting from the release line can break the updater and require manual repair.

Notifuse sends newsletters and transactional email from infrastructure you control, positioning itself against Mailchimp, Brevo, Klaviyo and their peers. What it removes is the per email bill and the copy of your contact list living in someone else's database.

The backend is Go, arranged in domain, service, repository and HTTP layers, with PostgreSQL as the only datastore. The admin console is React, TypeScript and Ant Design, and an embeddable notification center widget ships beside it. Delivery goes out through a provider you connect, with Amazon SES, Mailgun, Postmark, Mailjet, SparkPost, SendGrid and plain SMTP supported.

The platform reaches well past broadcast sending.

• Visual builder: drag and drop editing on MJML components with real-time preview.
• Automations: multi-step journeys built as a graph of delay, branch, filter, webhook and A/B test nodes.
• Liquid templating: drop contact fields into subject lines and bodies.
• Web analytics: cookieless traffic measurement with engaged time sessions and channel attribution, all on PostgreSQL.
• Transactional API: trigger mail from your own code over REST and receive events by webhook.
• Workspaces: keep separate tenants for teams or agency clients.

Deployment is a Docker image with an interactive setup wizard, and the web analytics side needs PostgreSQL 17 or newer. The project does not accept pull requests, though issues are welcome, and version 40.0 onward carries a Business Source License 1.1 that converts to AGPL-3.0 four years after each release, while version 39 and everything earlier stays AGPL permanently. Five capabilities require a license key and the send path contains no license check.

Keila is a newsletter tool built as an alternative to Mailchimp and similar hosted services. It covers the whole loop: growing a contact list through sign-up forms, designing a campaign, sending it, and reading what happened afterward, without the list itself living on a platform you do not control.

Campaigns can be written in a visual block editor, in Markdown with or without a WYSIWYG layer, in MJML for fully custom responsive layouts, or in plain text. Base templates absorb the differences between Gmail, Outlook, Thunderbird, mobile, and desktop. For a small newsletter you can send through your own inbox over SMTP; larger projects point Keila at AWS SES, Sendgrid, Mailgun, or Postmark instead.

The features around sending are where a list actually gets managed.

• Form builder: sign-up forms with additional checkboxes, text fields, and dropdowns.
• Bot protection: hCaptcha or Friendly Captcha on forms, plus double opt-in confirmation of new sign-ups.
• Segments: subsets of a list built from contact data such as language or tags, through a visual editor or a segment language.
• Liquid templating: personalization from custom contact data held as a JSON object, using Shopify's Liquid.
• Analytics: open and click tracking that can be switched off entirely with one setting.
• API: contacts, campaigns, forms, segments, and templates all addressable, with CSV import and export.

Self-hosting needs the official Docker image and a PostgreSQL database and nothing else, though a reverse proxy has to forward WebSockets correctly. Keila is written in Elixir, and a sample Docker Compose file ships in the repository.