Managed listmonk hosting
Pilae installs, patches, backs up and monitors listmonk for you, on your own servers or in any of 10+ Pilae Cloud regions, six of them in Switzerland and the EU.
From CHF 449EUR 479USD 559 a month on Starter, hosting and onboarding included.
- Business
- Open source
- Replaces Mailchimp
- Runs on
- Your own hardware, or a Pilae Cloud region
- Replaces
- Mailchimp, Brevo
- Licence
- AGPL-3.0
listmonk among the business apps
CRM, ERP, projects and scheduling. The records you are least willing to rent.
listmonk system requirements
Before anything is deployed, this is what has to exist. We size it with you in the first session, and we say so when your own hardware is already enough.
All 5 requirements, and why each is there
- CPU and memory2 vCPU · 2 GBFor listmonk and PostgreSQL on one machine. The Go binary itself uses little; the memory goes to Postgres, where view and click records grow with every campaign.
- DatabasePostgreSQLThe only dependency, and upstream’s minimum; we run a supported release. Subscribers, campaigns, templates and every setting, SMTP credentials included, live here, so this backup is the whole configuration.
- Mail relaySMTP, STARTTLS or TLSlistmonk neither delivers to recipients nor signs with DKIM. It hands every message to SMTP servers you configure, your own relay or a sending provider you contract, and the relay does the DKIM signing.
- Sending domainSPF, DKIM, DMARCAligned with the From address. Gmail and Yahoo require all three from bulk senders, together with one-click unsubscribe, which listmonk sends as List-Unsubscribe and List-Unsubscribe-Post headers.
- Bounce handlingPOP3 mailbox or webhookA POP3 mailbox behind the Return-Path that listmonk scans on an interval, or webhooks from one of the sending providers listmonk supports. Without it, dead addresses keep being mailed and the domain’s reputation pays for it.
Running listmonk in production: what it takes
Pin and deploy on PostgreSQL
The single listmonk binary at a version we have run, with PostgreSQL beside it. The upstream compose file upgrades the schema whenever the container starts, so the image is pinned and a restart never changes the database.
Keep the admin private, publish the reader paths
The admin and API answer only on your private network, behind Keycloak or Entra ID over OpenID Connect. Subscription pages, unsubscribe and tracked links, campaign images, the archive and the bounce webhooks go out through the Pilae gate on port 443.
Set up the domain, the relay and the bounces
SPF, DKIM and DMARC aligned with your From address, one-click unsubscribe on, and a send rate and hourly cap set to what the relay accepts. Hard bounces and complaints are blocklisted on the first occurrence, soft bounces only after several.
Restore with mail pointed at a sink
Each day the database and the uploads directory are copied offsite, encrypted. On the Enterprise plan, each month they are restored into a scratch instance where a campaign is opened. Its mail points at a sink, so a drill never reaches a subscriber.
Upgrade between campaigns
Releases can change the schema, and an upgraded database is not used with an older binary, so the rollback is the backup taken just before. The Pilae Agent tries the upgrade on a copy and, once you approve, applies it in your window, never while a campaign is sending.
From our runbook
An evening campaign, sent at the rate the relay accepts
infostart processing campaign (October briefing)
info48,210 recipients on 3 lists, 4 workers at 5 messages/s each
infoscanning bounce mailbox mail.acme.internal
info96 hard bounces blocklisted, 17 soft bounces recorded
infomessages exceeded (30000) for the window (1h0m0s since 01 Oct 26 18:00 +0200). Sleeping for 35m0s.
infosending resumed, 18,210 recipients remaining
infocampaign (October briefing) finished
info64 one-click unsubscribes applied since 18:00, 0 send errors
infobackup database and uploads: verified offsite
Migrating from Mailchimp to listmonk
Subscribers come across; history does not. A Mailchimp audience export can come as a ZIP with one CSV file per contact status, and listmonk imports CSV with an email, a name and a JSON column of attributes. Merge fields, tags and the opt-in timestamps go into that column, so consent records survive and segments can be rebuilt as queries over them. Unsubscribed and cleaned contacts come across as well, as the suppression list. Open and click history stays in Mailchimp reports. Drag-and-drop templates cannot be exported and are rebuilt, and customer journeys have no equivalent in listmonk. The import is the easy part; the sending domain and the new relay are where the care goes.
- AlternativesA HubSpot CRM alternative you ownOne of 3 apps for teams leaving HubSpot CRM.
- Migration guideHow to migrate from Mailchimp to listmonkMove from Mailchimp to self-hosted listmonk: export every audience, import the blocklist first, keep opt-in records, rebuild templates and warm up a new domain.
Moving from Mailchimp to listmonk, step by step
- Export every audience, all four files: Subscribed, unsubscribed, non-subscribed and cleaned contacts come out of Mailchimp as separate CSV files. The unsubscribed and cleaned files are the suppression list, and a migration that leaves them behind mails people who already said no.
- Reshape into listmonk's import format: Each file is reshaped to email, name and attributes. Subscribed contacts go in as confirmed and, through the import API, unsubscribed ones as unsubscribed on the same list. Cleaned addresses go in blocklist mode.
- Rebuild the templates: Custom-coded templates export as HTML and come across once merge tags such as *|FNAME|* become listmonk template expressions. Drag-and-drop templates are rebuilt in the visual builder, and a test campaign goes to a seed list before anything else.
- Move the sending, then close the account: SPF, DKIM and DMARC for the new relay are published before the first campaign, which goes to the most engaged segment at a reduced rate. Campaign reports are exported from Mailchimp before the account closes.
What listmonk is, and who runs it
Newsletters and mailing lists sent from your own domain, with the subscriber database in Switzerland, the EU or your own datacentre rather than with a marketing platform.
Self-hosted listmonk for newsletters and mailing lists
listmonk is a newsletter and mailing list manager: one Go binary with PostgreSQL behind it. It handles lists with single or double opt-in, segments written as SQL over subscriber attributes, campaigns built in a visual editor or as HTML, a public archive, and transactional messages over an API. It covers what most organisations use Mailchimp or Brevo for: the monthly newsletter, member announcements, the list people signed up to on the website. It does not run sequences such as a welcome series; where one matters, n8n drives it through the API.
The subscriber list lives on a dedicated machine on your premises or in whichever of our 10+ Pilae Cloud regions your data-protection assessment allows, six of them in Switzerland and the EU. Subscribers, consent timestamps and every campaign sit in a database you can name. Subscribers can export or wipe their own data from the public subscription pages, and views and clicks are counted without being tied to a person unless you turn that on.
Read the full briefFold the brief
listmonk in production: the relay, the domain and the database
Sending is the hard part, and it is not listmonk’s part. listmonk passes each message to a relay, and the reputation of your domain decides whether it reaches the inbox. So the work is in the domain and the list: SPF, DKIM and DMARC aligned with your From address, the one-click unsubscribe header, a send rate the relay accepts, and bounces fed back from the Return-Path mailbox or the provider’s webhooks, so a dead address is mailed once and not on every campaign.
The admin can see the whole list and change every setting, so it and the API answer only on your private network, behind Keycloak or Entra ID. What subscribers touch has to be public: subscription pages, unsubscribe and tracked links and campaign images go out through the Pilae gate on port 443. The database and the uploads directory are backed up daily, encrypted, to the country your contract names, and on Enterprise the monthly restore drill runs with outbound mail pointed at a sink. Probes check the public pages every 60 seconds and alert an engineer, and upgrades go through the Pilae Agent between campaigns.
listmonk licence and pricing
listmonk is AGPL-3.0, and there is one build: no paid edition and no fee per subscriber. OpenID Connect sign-on is in it. The cost outside our operation is the relay or sending provider, which you contract directly. Our operation follows the published plans. Talk to us about the lists you send to.
What Pilae is responsible for
The same commitments on every app we run, listmonk included, and what stays yours. How the platform does it.
Ours
- A pinned version: A version we have run, not whatever latest resolves to that day.
- A runbook: What it depends on, how it fails, what to do about it. In your repository.
- Daily backups: Encrypted and offsite, and on Enterprise restored every month. A backup nobody has restored is a file.
- A patch window: Security updates in a window you agreed, with a rollback ready.
- Someone watching: Every endpoint probed on the minute. An alert reaches a person, not a dashboard nobody opens.
Yours
- The credentials: You hold them. Ours are separate, named, logged and revocable with one command.
- The approval: We ask before anything changes outside an agreed window.
- The exit: The machine, the data, the compose files and the runbook are already yours. Nothing stops when our access does.
Who runs it
Engineers who answer for it
Our engineers review every plan the Pilae Agent prepares and answer for the result.
Your data stays where the contract says
On your own servers or in Pilae Cloud. On Business and Enterprise you choose the region, and your contract names each location.
A Swiss company, a Swiss contract
Pilae is a Swiss company, and your contract with it is governed by Swiss law.
listmonk runs on Starter from CHF 449EUR 479USD 559 a month in Pilae Cloud, or on Business with up to three apps on your own servers.
Compare the planslistmonk: common questions
Is listmonk open source?
Where do our subscriber lists live?
Will our newsletters reach the inbox?
Can listmonk replace Mailchimp?
Can staff sign in with our directory?
Ask the engineers who would run your listmonk
Thirty minutes on the deployment you already have, or the one you are about to start.
- Go deeperManaged operations and SLA for open-source appsPatching, daily encrypted backups, monitoring and incident response for your open-source apps, under an SLA with an availability commitment of up to 99.9%.
- CompareSelf-hosting vs managed open source: doing it yourself, or PilaeSelf-hosting gives you the apps and the whole job of running them. Pilae gives you the same open-source apps, operated under a contract, on your premises or in Pilae Cloud.
- CheckData processing agreement (DPA)Our standard DPA under the revised FADP and the GDPR, signed at onboarding, with every sub-processor for your service named in the agreement.
