Mailpiece vs Keila
Open-source campaigns, made in Germany, hosted in the EU.
We think a newsletter belongs to the person who writes it, and Keila agrees: it is open source and made in Germany, you can run it yourself or on its cloud in the EU, and you can turn tracking off. Where we differ is shape. Keila is built for sending campaigns to segments; Mailpiece is built for writing posts that live on your site and reach everyone who asked.
With Keila
A campaign, sent to a segment
- Write in blocks, Markdown or your own layout
- Choose who gets it with segments and fields
- Count opens and clicks without IPs or cookies, or turn it off
- Its cloud in Germany and France, or your own server
With Mailpiece
A post, the same for everyone
- 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 its editor, or through its API
tell your agent what this week's issue is about, and it drafts, tests and schedules it
shape segments and custom fields for each send
write to everyone who asked, when you choose
turn tracking off, campaign by campaign
never think about tracking, because there is none
share a campaign's web link if you want one
keep every issue as a post on your own domain
send one welcome email when someone signs up
greet new readers with a series, and say goodbye when they leave
Side by side
- Keila is built for campaigns, segment by segment, made with care in Germany and hosted in the EU. In Mailpiece, you write one letter for everyone, from a server you choose.
- In Keila, you build campaigns in its editor, or through its API. In Mailpiece, your agent does all you can do on screen: drafts, sends you a test, schedules, publishes.
- In Keila, your list lives on its cloud in the EU or on your own server. In Mailpiece, it lives on your server, wherever you choose to run it.
- In Keila, opens and clicks are counted without IPs or cookies, unless you turn it off. In Mailpiece, they're left alone.
- As your list grows, Keila stays the same if you host it yourself. In Mailpiece, nothing changes.
- In Keila, you shape campaigns and segments. In Mailpiece, you write, test and send.
Moving from Keila
Install Mailpiece, export your contacts from Keila and import them, then connect the mail provider you want to send with. Your next issue goes out from Mailpiece. Only the addresses come across: your old campaigns, segments, custom fields and forms stay in Keila, so keep it running for as long as you want them.
Who should stay on Keila?
Anyone who sends campaigns more than they write posts: a shop or a project mailing different news to different segments, with custom fields, several senders and layouts of their own. And a sender who wants an EU-hosted service that takes the GDPR seriously and signs a data processing agreement with them. Keila does all of that well, in the open, and Mailpiece doesn't try to.
Keila is open source and self-hosted too. Why switch?
You don't have to: both keep your list on a server you choose and both let you pick who sends. Switch if you'd rather write than run campaigns: Mailpiece gives every issue a home on your own domain, lets your agent write and test it, and never tracks anyone.
Does Keila handle the GDPR?
Carefully, and it is one of its strengths. Keila is made in Germany, its cloud runs on European infrastructure in Germany and France, and it offers the data processing agreement the GDPR asks of a service that holds your list. Mailpiece runs on your own server, so where your data lives is yours to choose.
Move your newsletter this afternoon
Install Mailpiece on a server, import your list, connect your sender, and send your next issue from it.