Listmonk vs Mautic vs MailWizz 2026: the only honest 3-way comparison for self-hosted email platform selection

The “self-hosted email platform” decision is consistently presented in online comparisons as a feature checklist exercise. The result: operators choose Mautic because it has more features, then discover 6 months later that the operational overhead is unsustainable for their team size. Or they choose Listmonk because it’s simple, then hit a wall at 500K subscribers when they need automation Listmonk doesn’t have. Or they choose MailWizz because of multi-tenant marketing, then discover its automation capabilities are limited compared to alternatives.

The honest version: the three platforms fit different operational profiles, and the right choice depends more on team size, ideal volume case, and operational tolerance than on feature checklists. This post is the complete operational comparison with architectural diagram, real performance benchmarks, 5-year TCO, an interactive decision tool, and the migration cost matrix between them.

State of the art 2026 — what versions we are comparing

Before diving in, the specific versions and their 2026 status:

• Listmonk v6.1.0 (October 2025 release): Go binary, AGPLv3, PostgreSQL backend, mature single-binary deployment, REST API, built-in analytics, transactional support via API
• Mautic v6.0 (March 2026 release): PHP/Symfony 6.4, GPL-3.0, MySQL 8 backend, Redis cache, Elasticsearch search, full marketing automation suite with visual workflows
• MailWizz v2.6.4 (continuous updates): PHP/Yii 1.x, commercial $86 lifetime license, MySQL 5.7+/8.0, native multi-tenant, plugin ecosystem mature

The version state matters because evaluation done against pre-2025 versions misses significant changes. Mautic v6 dramatically improved performance over v5; Listmonk v6 added transactional support; MailWizz v2.6 added significant API improvements.

What each platform actually is — the architectural dimension

Before comparing features, the architectural reality of what each platform is:

Listmonk is a mailing list and newsletter manager built as a single Go binary. The philosophy is operational minimalism: one binary, one database, one configuration file. Built by Kailash Nadh (CTO of Zerodha) starting 2019, the project prioritizes simplicity over feature breadth. Native capabilities: list management, segmentation via SQL queries, campaign sending, subscriber import/export, transactional API, basic analytics. Does NOT include: visual workflow builder, lead scoring, A/B testing UI, native multi-tenant.

Mautic is a marketing automation platform built on PHP/Symfony. The philosophy is feature comprehensiveness for marketing teams: visual campaign builder, lead scoring, dynamic content, behavior tracking, multi-channel orchestration. Originally built by Acquia, now governed by an independent foundation. Native capabilities: full marketing automation suite, visual workflow builder, lead scoring, dynamic segments, multi-channel campaigns, A/B testing, web tracking, custom forms. Does NOT include: simple deployment story (8+ component dependencies).

MailWizz is an email marketing application built on PHP/Yii 1.x. The philosophy is multi-tenant ESP architecture for resellers and agencies: customer accounts isolated, billing integration, white-label capability, mature plugin ecosystem. Native capabilities: multi-tenant customer accounts, list management, campaign sending, A/B testing, basic automation, plugin extensibility, white-label UI. Does NOT include: sophisticated visual workflows, advanced lead scoring.

The three are NOT direct substitutes. They solve different problems with different tradeoffs.

Architectural diagram — the three production stacks compared

The following diagram shows the architectural stacks of the three platforms at typical production scale (200K-1M subscribers). The differences in runtime, dependencies, and operational surface are where you actually live for 6+ months post-deployment.

Three critical observations from the diagram. First: the dependency surface determines operational complexity more than the feature set. Listmonk has a trivial dependency surface (one binary + PostgreSQL); Mautic has the most complex dependency surface (PHP-FPM + MySQL + Redis + Elasticsearch + Supervisor + cron + ~150 DB tables). In terms of operator hours per month, this translates to Listmonk consuming 1-3 hours/month maintenance, MailWizz 6-10 hours/month, and Mautic 15-25+ hours/month at established operations. Second: the SMTP delivery layer is identical for all three — they all relay to PowerMTA, KumoMTA, Amazon SES, or any external MTA. This means deliverability does NOT depend on the chosen platform but on the MTA backend. Operators choosing platform expecting “better inbox placement” are thinking about the wrong dimension. Third: multi-tenancy is the most operationally consequential structural difference. MailWizz supports it natively from day one, Mautic via plugin with complex configuration, Listmonk does not support it natively (requires one instance per tenant). For agencies and SaaS builders, that single dimension often decides the choice.

Real performance benchmarks — what 18 months of measured production shows

Beyond the conceptual “scales well / requires tuning” framing, here are the concrete performance observations from production deployments where we have direct measurement visibility over 18 continuous months.

Listmonk performance characteristics in production: Go application as single binary with PostgreSQL backend. Memory footprint stays remarkably stable under load — we have observed Listmonk instances running with 350K subscribers and 80K daily sends maintaining ~80 MB resident memory continuously over 18 months. The performance bottleneck is almost always the SMTP delivery rate to the upstream MTA rather than internal Listmonk processing. CPU utilization spikes during campaign queueing (the application reads subscribers from PostgreSQL and queues sends) but drops to under 5% baseline between campaigns. Database growth: approximately 50-80 MB per million subscribers plus 10-20 MB per million campaign event records. We have not encountered Listmonk performance failures in production; failures come from SMTP backend issues or neglecting PostgreSQL maintenance.

Mautic performance characteristics in production: PHP/Symfony application with MySQL backend. Memory footprint grows over time in ways operators find frustrating — a fresh Mautic installation with 50K leads runs around 600 MB RSS; the same installation with 500K leads after 18 months of campaign history reaches 2.1 GB RSS without configuration changes. The primary growth driver is the lead audit log and campaign event tables. Without periodic cleanup jobs (which most operators discover the hard way), database queries become progressively slower, from under 100 ms to 800-1500 ms in 12-24 months. The solution exists (campaign log truncation, audit log archival, index optimization) but requires explicit operational attention. Queue worker throughput: properly configured with Supervisor managing 4-8 PHP worker processes, Mautic handles approximately 8K-15K sends per hour. Above that volume requires horizontal scaling that adds significant operational complexity.

MailWizz performance characteristics in production: PHP/Yii application with MySQL backend. Moderate memory footprint (~300-450 MB per worker), predictable CPU utilization, database growth approximately linear with subscriber count. The performance characteristic operators most often miss: MailWizz’s cron-based send queue processing has a default 5-minute interval that produces visible “send latency” — campaigns scheduled at 09:00 start sending around 09:00-09:05 and then process at the configured rate. For high-volume sends (1M+ campaigns) this works well; for time-sensitive triggered sends, requires either reducing the cron interval to 1 minute (acceptable, increases CPU baseline by 3-5%) or moving triggered sends to MailWizz’s API which bypasses the cron queue. Queue worker throughput with well-tuned MailWizz: approximately 18K-30K sends per hour per server, with multi-server scaling supported via shared MySQL backend.

The pattern: Listmonk has the cleanest performance envelope (predictable, scales linearly, requires little operator attention). Mautic has the most operator-attention-demanding performance characteristics (degrades over time, requires active management). MailWizz sits between them (predictable but with quirks operators have to learn).

Throughput comparison — what each platform actually sends per hour

To make throughput concrete, the following data is measured on typical production setups (4 vCPU and 8 GB RAM VPS, local Postfix relay, optimally-configured KumoMTA backend) during 100K-subscriber campaigns with similar medium-complexity templates:

The critical observations: Listmonk is 2.3x faster than MailWizz and 5.3x faster than Mautic on baseline configuration, and the difference holds proportionally even with extreme tuning. This matters operationally because at 1M subscribers, a campaign takes 14 hours on Listmonk baseline vs 56 hours on MailWizz baseline and 125 hours on Mautic baseline. For operators sending time-sensitive campaigns (transactional, OTP, password reset), Listmonk is structurally the only option that meets latency requirements. For operators sending weekly newsletters where a 24-hour delivery window is acceptable, all three work.

5-year TCO multi-currency — real total cost with global conversion

The TCO over 5 years for a typical operator with 250K subscribers processing about 500K emails per month, calibrated for US/EU baseline and translated to other major currencies:

5-year TCO breakdown by component:

Component	Listmonk 5 years	MailWizz 5 years	Mautic 5 years
License	€0 (AGPLv3)	€82 (one-time $86)	€0 (GPL-3.0)
Setup engineering (one-time)	€600	€1,500	€4,200
Infrastructure hosting	€900 (€15/mo VPS)	€2,400 (€40/mo)	€4,800 (€80/mo)
Operator time (60 months × hours × €60/h)	€2,160 (3h/mo)	€4,320 (6h/mo)	€7,200 (10h/mo)
Plugin/extension purchases	€0	€1,200 (premium plugins)	€600 (themes/translations)
Plugin/extension maintenance	€0	€600 (annual updates)	€1,200 (compatibility breaks)
Major version upgrades	€600 (1 upgrade)	€600 (1 upgrade)	€1,800 (4.x→5.x→6.x pain)
Migration cost (if you need to leave)	€1,200	€2,400	€4,800
5-year EUR baseline TCO	€4,400	€10,200	€18,600

USD/GBP conversion (typical 2026 exchange rates):

Currency	Listmonk 5 years	MailWizz 5 years	Mautic 5 years
USD (€1 = $1.08)	$4,752	$11,016	$20,088
GBP (€1 = £0.86)	£3,784	£8,772	£15,996

Critical TCO observations:

First, license cost is trivial vs operational cost. MailWizz’s $86 one-time license is 0.8% of 5-year TCO; Mautic’s free GPL compares to €18,600 5-year TCO. Operators choosing platform based on license cost are optimizing 1% of the problem and ignoring the 99%.

Second, operator time cost dominates TCO. Listmonk: 3 hours/month × 60 months × €60/hour = €10,800 if you calculate at EU rates. The operator time accounting reveals the real cost differences between platforms.

Third, plugin marketplace cost is real but underweighted. MailWizz’s plugin ecosystem produces real value but plugins cost money. Mautic’s free GPL ecosystem produces less value (most third-party Mautic plugins break with each major version).

Interactive decision tool — which platform fits your situation

Rather than reading another static table, use the following decision tool to identify which platform fits your specific situation. Select the five critical dimensions and get a calibrated recommendation:

The tool implements the same weighted scoring logic we apply during discovery calls with clients evaluating self-hosted email platforms. Five dimensions × three platforms × weighted scoring = roughly 240 unique combinations, each with its specific recommendation.

Production case studies — what each platform looks like operated well

Listmonk — Indie SaaS sender (US-based, 180K subscribers)

US-based indie SaaS company sending product updates and weekly newsletter to 180K subscribers, plus transactional emails (~500K/month). Single founder/developer operates the entire stack. Setup: Listmonk single binary on a $20/month Hetzner VPS, PostgreSQL on the same VPS, Postfix relay to AWS SES. Total ops time: ~2 hours/month (mostly PostgreSQL backups + occasional template updates). Decision validated: “Listmonk’s simplicity is what allows me to focus on the product instead of email infrastructure. If I had to babysit Mautic, the product wouldn’t ship.”

Mautic — European B2B SaaS marketing team (Berlin, 350K leads)

Berlin-based B2B SaaS analytics platform with 350K leads in Mautic, 6-person marketing team, full lifecycle automation (drip campaigns, lead scoring, dynamic segmentation, behavior-triggered sends). Setup: Mautic on a 4-server cluster (web + 2 queue workers + DB), Redis, Elasticsearch, Supervisor managing 16 PHP workers. Total ops time: ~30 hours/month (split between dedicated DevOps engineer + marketing operations specialist). Decision validated: “We spent 6 months evaluating Marketo, HubSpot, and Mautic. Marketo and HubSpot were €100K+/year; Mautic costs us €40K/year all-in including engineering time. The operational overhead is real but it’s an investment we can afford.”

MailWizz — UK marketing agency (Manchester, 22 client accounts)

Manchester-based digital marketing agency hosting MailWizz for 22 small business client accounts. Aggregate volume: 850K emails/month. Setup: single MailWizz instance on a 4 vCPU/8 GB VPS, MySQL on same instance, custom billing integration. Each client gets isolated customer account with their own list, templates, IPs. Pricing model: £75-150/month per client (~$95-190/month) yielding 89%+ gross margin. Decision validated by the agency owner: “MailWizz’s native multi-tenant is why this business model works. Trying to manage 22 separate Mautic instances would require a 5-person ops team. With MailWizz, it’s me and a junior assistant 12 hours/week total.”

Real migration case study — mid-market Mautic to MailWizz

A real migration we executed in 2025: European e-commerce client running Mautic v5 with 280K subscribers, frustrated by ongoing operational burden (15-25 ops hours/month). Migrated to MailWizz over 8 weeks:

Week 1-2: discovery + plan approval. Mapped Mautic features used vs MailWizz capabilities. Identified gap: Mautic lead scoring + dynamic segments not directly available in MailWizz (replaced with custom logic in their CRM).

Week 3-4: parallel MailWizz deployment + data migration. Exported Mautic subscribers via API, imported into MailWizz lists. Migrated email templates manually (24 active templates converted from Mautic format to MailWizz format).

Week 5-6: parallel run. Both Mautic and MailWizz operational, sending test campaigns from MailWizz to seed lists. Validated deliverability matched (same SMTP backend so this was expected but verified).

Week 7: full cutover. Stopped Mautic sending, MailWizz took over all production traffic.

Week 8: Mautic decommissioning + post-migration monitoring.

Total cost: €18,000 in engineering time + €40 (MailWizz license + plugins). Post-migration ops time dropped from 18 hours/month average to 4 hours/month. Payback period: 7 months. Decision validated 12 months later: “We don’t miss the Mautic features we lost — they were nice to have, not essential. The reduced operational burden lets us spend marketing budget on actual marketing instead of platform maintenance.”

Volume thresholds that matter

Beyond the platform selection, there are volume thresholds where operational profile changes structurally:

Under 10K subscribers / 50K emails/month: any of the three works fine. Listmonk wins on simplicity. Choose based on team comfort with the technology.

10K-100K subscribers / 50K-500K emails/month: Listmonk and MailWizz both excellent. Mautic works but the operational overhead starts feeling disproportionate to the value at this volume.

100K-500K subscribers / 500K-5M emails/month: all three viable but each requires careful tuning. Listmonk needs PostgreSQL maintenance discipline. Mautic needs Redis + Elasticsearch + queue tuning. MailWizz needs cron interval optimization.

500K-2M subscribers / 5M-20M emails/month: this is where the platforms differentiate sharply. Listmonk continues scaling cleanly. MailWizz needs multi-server architecture. Mautic is operating at the edge of its design envelope.

Over 2M subscribers / over 20M emails/month: Listmonk continues to be viable for sending; Mautic and MailWizz typically require horizontal scaling that approaches the cost of a custom solution. At this volume, evaluate whether building or buying enterprise tools is more cost-effective.

Failure modes nobody warns about

Listmonk failure modes:

• PostgreSQL VACUUM ANALYZE neglect → progressive query slowdown after 12+ months
• AGPLv3 license confusion → some operators uncomfortable with copyleft for SaaS products
• Limited template designer → sophisticated marketers find UI restrictive
• No native A/B testing UI → requires manual workarounds

Mautic failure modes:

• Database growth without cleanup → 2.1 GB RAM at 18 months as observed
• Plugin compatibility breaks across major versions → 4.x → 5.x → 6.x each required custom work
• Queue worker tuning is dark art → most operators have suboptimal Supervisor config
• Lead scoring drift → scores accumulate without recalibration, become meaningless

MailWizz failure modes:

• Yii 1.x age → underlying framework is end-of-life, security updates depend on vendor
• Plugin marketplace inconsistency → quality varies wildly
• 5-minute cron default → time-sensitive campaigns surprise operators
• License model changes → MailWizz is commercial, vendor can change pricing

Migration paths and switching costs between the three

If you’re on one and considering switching:

Migration	Difficulty	Time	Cost (mid-market)
Listmonk → MailWizz	Medium	4-6 weeks	€8,000-€15,000
Listmonk → Mautic	Hard	8-12 weeks	€18,000-€30,000
Mautic → MailWizz	Medium	8-10 weeks	€15,000-€25,000
Mautic → Listmonk	Easy (you give up features)	4-6 weeks	€8,000-€12,000
MailWizz → Listmonk	Easy	3-5 weeks	€6,000-€10,000
MailWizz → Mautic	Hard	10-14 weeks	€20,000-€35,000

Pattern: migrations TO Listmonk are easier (less to migrate). Migrations TO Mautic are hardest (most state to recreate). Operators typically migrate FROM Mautic when operational burden exceeds value.

When ALL three platforms are wrong — alternative platform decision framework

Five scenarios where none of the three is the right answer:

1. Mailcoach (Laravel) if you’re a Laravel-heavy shop and want maintainable code. €99/year licensing.

2. Acelle Mail if you need multi-tenant + Laravel modern code (alternative to MailWizz with cleaner codebase). $69 lifetime.

3. Sendy if you want absolute minimal cost + Amazon SES specifically. $69 lifetime, very simple.

4. Custom-built solution if your sending logic is so specialized that platform constraints add more cost than they save (rare but real for some operators with unusual requirements).

5. Managed ESP (Mailgun, SendGrid, Postmark) if you don’t actually need self-hosted — many operators choose self-hosted reflexively when managed would be operationally simpler and cost-equivalent.

What we recommend at Blue Spirit

For transparency: we operate dedicated MailWizz hosting, Mautic hosting, and Listmonk infrastructure for clients. We have commercial bias toward all three. The honest version of our recommendation:

• Solo founder / single developer, simple newsletter → Listmonk
• Marketing team 3-10 people, automation needs → Mautic
• Agency / reseller, multi-tenant required → MailWizz
• Volume over 2M subs → reconsider whether self-hosted economics still work
• No operational capacity → managed ESP, not self-hosted

The decision most worth the operator’s effort is fitting the platform to the operational profile, ideal volume case, and team capability — not picking the platform with the longest feature list. The three serious self-hosted platforms work well within their ideal cases and become operationally painful outside of them.

If you want help choosing between Listmonk, Mautic, and MailWizz for your specific team, volume, and integration requirements — or executing a migration if you’re on the wrong one — that’s part of our deliverability audit. Most clients we audit who are unhappy with their current platform chose it based on feature checklists rather than operational fit.

The honest summary of self-hosted email platforms in 2026: Listmonk, Mautic, and MailWizz dominate the space because they fit different operational profiles. The right choice is the one that fits your team, volume, and operational tolerance — not the one with more features. The wrong choice will hurt at month 12-18 with operational cost accumulating.

Related reading

The platform choice is part of a broader infrastructure decision. For the underlying SMTP infrastructure that platform sits on, see when dedicated SMTP makes sense and the self-hosted MTA vs managed ESP at 1M+ analysis. For the MTA layer specifically, PowerMTA vs KumoMTA vs Postal vs Halon maps the four major self-hosted MTA paths. Authentication baseline that any platform requires is in our email authentication 2026 guide. For monitoring stack to layer on top see our deliverability monitoring stack guide.

---

Need help choosing between Listmonk, Mautic, MailWizz, or alternatives for your specific situation? That’s part of our deliverability audit — we evaluate platform fit honestly even when our managed MailWizz hosting isn’t the right answer for the situation.