Is Plunk really free?

Yes. Plunk is open source: the code is public and installing it costs nothing. At most you pay for hosting if you put it on a server, often a few euros a month. Brevo, on the other hand, costs €9 a month.

Do I need to code to install Plunk?

No. The level is intermediate and the install takes about 30 minutes with the prompt from the page: Claude does the work, you answer its questions.

How is it different from Brevo?

Plunk does most of what Brevo does, without a subscription, and your data stays with you. The point by point comparison is on the page.

Yes. With an open source tool installed on your side, your files stay on your machine or your server. Nobody can close your account or change the price.

Free alternative

Free alternative to Brevo

Brevo costs €9 a month. Plunk does the same job for free, in open source: you install it on your machine or a small server, and you stop paying.

Public entry price, taken from Brevo’s website (brevo.com). Over a year, that is €108 that stays in your pocket.

What replaces Brevo

The main alternative

Plunk

🟡 Intermediate⏱️ ~30 min to installSave €11/mo

Plunk gathers in one tool what you pay Mailchimp or Brevo for: campaigns (a newsletter to your whole list, with the editor and templates), automations (a welcome email when someone signs up, a sequence when they take some action) and transactional emails sent by your site or app through a simple API. Your contacts, segments and history live on your server, with no contact cap and no logo forced at the bottom of your emails. The twist: Plunk does not send by itself, it relies on Amazon SES, AWS's sending service, which charges about 9 cents per thousand emails. So you need an AWS account with your verified domain. The install uses Docker Compose, a Postgres database and a Redis, following the official docs. The project is AGPL-3.0 licensed, maintained by one developer who also sells a cloud version (1,000 emails a month free, then per email sent), and the repo is past 5,400 stars with regular updates.

Loucash’s verdict on Plunk

7/10

Let me say it upfront: this library runs on Brevo, and I have not migrated yet. Plunk is still the right alternative if you pay Mailchimp or Brevo for your list: campaigns, automations and transactional emails in one place, unlimited contacts, no forced logo, and everything stays with you. The API is simple, the dashboard is clean. What you have to accept: Plunk cannot send without Amazon SES. You need an AWS account, your verified domain, a request to leave the sandbox, and you carry the sending reputation. Mailchimp and Brevo, you mostly pay them for that, deliverability handled by people whose job it is. If your list is small or your sends rare, the price gap is not worth the time spent at AWS. My math: from a few thousand contacts and one send a week, Plunk saves you several tens of euros a month for a few cents at Amazon. That is when I will switch.

Who it is for: You pay Mailchimp or Brevo for a list of several thousand contacts, you have a server, and you accept to spend half an hour at Amazon SES.

See the full page →See the tool ↗

The prompt that installs Plunk

Paste this prompt into Claude: it checks the repository, asks you its questions and installs the tool step by step.

Installe Plunk sur mon serveur (la plateforme email open source, alternative à Mailchimp et Brevo, repo GitHub useplunk/plunk, image Docker driaug/plunk) en suivant la doc officielle docs.useplunk.com/self-hosting/introduction. Pars de zéro : vérifie que Docker et Docker Compose sont présents, sinon installe-les. Commence par Amazon SES : explique-moi comment créer un compte AWS, vérifier mon nom de domaine dans SES (enregistrements DNS DKIM et SPF à poser), créer un configuration set, demander la sortie du mode bac à sable pour envoyer à n'importe qui, et créer une clé d'accès IAM limitée à SES. Ensuite récupère le docker-compose.yml officiel de la doc, crée le fichier .env avec un JWT_SECRET long et aléatoire, les URL de mon tableau de bord et de mon API sur deux sous-domaines (app. et api.), la base Postgres et le Redis du compose, la région et les clés SES, et DISABLE_SIGNUPS à true dès que mon compte est créé. Mets un reverse proxy Caddy devant qui sert les deux sous-domaines en HTTPS avec certificats automatiques, sans publier les ports du conteneur. Lance le tout, crée mon compte, ajoute mon domaine d'envoi, puis envoie un mail de test à mon adresse depuis une campagne et un autre depuis l'API. Explique chaque étape simplement, je débute.

Review the GitHub repository and check whether it is safe to install given my machine and my infrastructure. Ask me as many questions as possible, using widgets, to clarify my request and be as precise as you can.

Frequently asked questions

Is Plunk really free?: Yes. Plunk is open source: the code is public and installing it costs nothing. At most you pay for hosting if you put it on a server, often a few euros a month. Brevo, on the other hand, costs €9 a month.
Do I need to code to install Plunk?: No. The level is intermediate and the install takes about 30 minutes with the prompt from the page: Claude does the work, you answer its questions.
How is it different from Brevo?: Plunk does most of what Brevo does, without a subscription, and your data stays with you. The point by point comparison is on the page.
Do I own my data?: Yes. With an open source tool installed on your side, your files stay on your machine or your server. Nobody can close your account or change the price.