Products · comparison

Laposta vs Mailchimp

Laposta suits newsletter senders who want hosting in the Netherlands and a contract with a Dutch company, and who need automation, signup forms and an API but not much more. Teams that rely on Mailchimp's A/B testing, SMS, landing pages or transactional email should not switch without a plan for those, because our data does not find them in Laposta as of 2026-10-16. Laposta's ultimate parent is still unknown.

What you gain with Laposta

• Contract with a Dutch company. Laposta's contracting entity is Laposta B.V., registered in the Netherlands (KvK 72409681, Zutphen). As of 2026-10-16, Mailchimp's contracting entity is The Rocket Science Group LLC, formed in Georgia, US, and its terms are governed by Georgia law. EU customers pay Intuit Ireland Software Limited, but the contract stays with the US entity.
• Hosting in the Netherlands, email delivery in the EU. Laposta's hosting subprocessors (BIT B.V. and TransIP B.V.) store all data in the Netherlands, and its servers are in a Dutch data centre. Its email delivery subprocessor, Postmastery B.V., states storage in the EU. As of 2026-10-16, Mailchimp's own servers are in US data centres, no EU data residency option was found, and its DPA allows processing in the US and wherever its affiliates or subprocessors operate.
• Dutch subprocessors only in core processing. Laposta lists three subprocessors, all Dutch. As of 2026-10-16, Mailchimp's subprocessor list includes US companies in core processing (Amazon for delivery and temporary storage, Akamai, Twilio for SMS), and the page shows a last update of 2024-02-29.
• Larger free tier. Laposta is free up to 2,000 contacts (12,000 emails per month), and its free plan includes up to 100 automations. Mailchimp's free plan covers up to 250 contacts and offers automation flows as a preview only.

What Laposta lacks

• No standard A/B testing. As of 2026-10-16, Laposta's help centre says there is no standard A/B test function yet. The documented workaround is manual: an extra field, segments and two separate campaigns. Mailchimp offers A/B testing on Essentials and higher (subject line, From name, content or send time, up to 3 variations), and multivariate testing on Standard and Premium. It is not on Mailchimp's free plan.
• No SMS found. SMS sending is not found in Laposta's documentation as of 2026-10-16 (pricing, function pages, help centre); no page says it is not offered. Mailchimp documents SMS as a paid add-on (credits) for Essentials and higher, after an application is approved, in select countries including most EU states.
• No landing page builder found. A landing page builder is not found in Laposta's documentation as of 2026-10-16. Laposta documents standalone signup forms and web versions and an archive page for newsletters, which are not the same thing. Mailchimp lists landing pages on all plans, including Free.
• No transactional email found. Laposta's API documentation covers lists, fields, segments, contacts, webhooks, campaigns and results; transactional or SMTP sending is not found in Laposta's documentation as of 2026-10-16. Mailchimp Transactional is a paid add-on for Standard or higher, sold in blocks of 25,000 emails per month, via API or SMTP.
• Plan limits differ. Laposta offers double opt-in on its signup forms on paid plans only, and its free plan allows up to 100 automations and 3 API keys. Mailchimp's automation is limited to 4 flow steps on Essentials, with branching on Standard and Premium.
• Narrower and weaker export. Laposta exports lists, segments, unsubscribed contacts and campaign results to Excel, and has a REST API. Its terms do not guarantee a readable export format, and free accounts get no export after termination. Mailchimp's account export (ZIP) also includes emails, templates, files and reports, and audiences export as CSV. Both still pass EUgrade's export criterion: customers can get their core data out themselves.
• Ultimate parent unknown. As of 2026-10-16, we could not confirm who owns Laposta B.V. The jurisdiction advantage above rests on the contracting entity, not on a confirmed ownership chain.
• Some non-EU services around the core. As of 2026-10-16, Laposta's help centre (docs.laposta.nl) runs on Help Scout (US) and its website loads Google Analytics. Neither is on the subprocessor list or part of core processing. We have not checked whether support email goes through Help Scout.
• Free tier limits. Laposta's free tier shows Laposta advertising below every email. Using your own DPA template instead of Laposta's standard one requires a paid subscription.
• Neither product is open source or self-hostable. Moving to Laposta does not reduce this kind of lock-in.

Migration effort: 2 / 5

For a plain newsletter, contacts move easily, because Mailchimp exports audiences as CSV and Laposta imports .csv, .xls or .xlsx files (first sheet only), but our data shows no import path in Laposta for templates, automations or campaign history, and teams using A/B tests, SMS, landing pages or transactional email need a replacement for those.

Verdict

For a newsletter whose main need is to send email to contact lists, Laposta stores contact data with Dutch hosting providers in the Netherlands, sends email through a Dutch subprocessor that states EU storage, uses only Dutch subprocessors in core processing, and contracts through a Dutch company. It also covers automation, signup forms, an API and contact import. As of 2026-10-16, Mailchimp is owned by Intuit Inc. (US), stores data in US data centres, and uses US subprocessors in core processing. Teams that depend on A/B testing, SMS, landing pages or transactional email should stay or plan a replacement: Laposta has no standard A/B testing, and the other three are not found in its documentation as of 2026-10-16. Laposta's ultimate parent is unknown, and its export is narrower than Mailchimp's and comes without a format guarantee.

Approved 2026-10-16. Facts used: 44, each linked to its source on the product pages.