Mailpiece vs listmonk
A single binary. Plus Postgres. Plus you.
We think a newsletter belongs to the person who writes it, and listmonk agrees: it is free, open source and runs on your own server. Where we differ is shape. listmonk is a mailing list manager for lists, queries and campaigns; Mailpiece is a newsletter, built for writing posts that live on your site and reach everyone who asked.
With listmonk
A campaign, sent to your lists
- Write in blocks, a rich editor, Markdown or HTML
- Choose who gets it with lists and queries
- Count views, clicks and links in its reports
- Publish to an archive, campaign by campaign
With Mailpiece
A post, not a campaign
- Ask your agent to write it, or write it yourself
- Everyone who asked gets the same issue
- No tracking, ever. Readers say if they liked it
- The post lives on your domain, with a feed
A week with each
build the campaign in an editor and a template, or through its API
tell your agent what this week's issue is about, and it drafts, tests and schedules it
sort subscribers into lists and query them for each send
write to everyone who asked, when you choose
read the campaign's views, clicks and top links, unless you turn tracking off
hear from the readers who say they liked it
turn on the archive and publish each campaign to it
keep every issue as a post on your own domain
run the app your developers and campaigns need
run a newsletter, with welcome and goodbye emails
Side by side
- listmonk is built for running mailing lists, query by query, campaign by campaign. In Mailpiece, you write to readers, and every issue has a home on your site.
- In listmonk, you write in anything from blocks to raw HTML, or create campaigns through its API. In Mailpiece, your agent does all you can do on screen: drafts, sends you a test, schedules, publishes.
- In listmonk, your list lives on your server. In Mailpiece, it does too.
- In listmonk, your readers are counted in reports unless you turn it off. In Mailpiece, they're left alone.
- As your list grows, listmonk stays the same, because it's yours. So does Mailpiece.
- In listmonk, your day goes to lists and campaigns. In Mailpiece, you write, test and send.
Moving from listmonk
Install Mailpiece, export your subscribers from listmonk and import the addresses, then connect the mail provider you want to send with. Your next issue goes out from Mailpiece. Only the addresses come across: your lists, attributes, templates, archive and reports stay in listmonk, so keep it running for as long as you want them.
Who should stay on listmonk?
Anyone who runs mail more than they write it: a product sending to many lists, messages fired from its own code, subscribers sorted by their attributes. listmonk does that well, in the open, and Mailpiece doesn't try to.
listmonk is free, open source and self-hosted too. Why switch?
You don't have to: both keep your list on your own server and both let you pick who sends. Switch if you'd rather write than run a mailing system: Mailpiece gives every issue a home on your own domain, lets your agent write and test it, and never tracks anyone.
Move your newsletter this afternoon
Install Mailpiece on a server, import your list, connect your sender, and send your next issue from it.