Mailchimp vs Self-hosted

Different cost models with very different shapes.

Mailchimp and equivalents. Per-subscriber tiers with monthly fees. Mailchimp Standard at 50K contacts is around €230/month. ConvertKit at 50K is around €200/month. ActiveCampaign Lite at 50K is around €260/month. Cost scales linearly with list size. Some plans cap monthly sends; exceed the cap and you pay overage.

Self-hosted (MailWizz + PowerMTA + dedicated infra). Mostly fixed costs. MailWizz license one-time around €70-100. PowerMTA license €2K-10K annually. Dedicated server €100-300/month. IPs €5-10/month each. Total monthly: roughly €150-400/month for a typical setup, regardless of whether you have 10K or 500K subscribers.

The asymmetry is what drives the decision. SaaS scales with you. Self-hosted is a fixed cost that's expensive at low volume and cheap at high volume.

Real crossover is more nuanced than just headline price comparison. Send frequency matters.

• 5K subscribers, sending weekly: Mailchimp Free or Essentials, around €10-30/month. Self-hosted overhead doesn't make sense.
• 20K subscribers, sending weekly: Mailchimp Standard around €100/month. Self-hosted at €200/month is more expensive. Stay on SaaS.
• 50K subscribers, sending weekly: Mailchimp around €230/month. Self-hosted around €200-300/month. Roughly tied. Decision rests on non-cost factors.
• 100K subscribers, sending 2× weekly: Mailchimp around €450/month plus possible overage. Self-hosted same €200-300/month. Self-hosted wins on cost.
• 500K subscribers, daily campaigns: Mailchimp around €1,500-2,500/month. Self-hosted around €400-600/month. Self-hosted wins decisively.
• 2M+ subscribers, multiple daily sends: Mailchimp custom enterprise pricing, often €5K+/month. Self-hosted with proper infrastructure around €1K-2K/month. Self-hosted wins by a multiple.

The headline cost comparison favours self-hosted past 50-100K subscribers. The full cost picture is more complicated.

• Engineering time. Self-hosted requires someone who knows DKIM, SPF, DMARC, IP warming, bounce processing, FBL handling. Fractional contractor or in-house, that's 5-15 hours/month for ongoing operations plus 40-80 hours initial setup. At €50-150/hour, the annual operational cost is €5K-25K.
• Deliverability operations. SaaS providers handle warming, monitoring, RBL delisting, abuse handling. Self-hosted operators do all of this themselves or pay a managed service. Add €200-500/month for managed deliverability.
• Infrastructure failures. Server crashes, IP listings, ISP blocks. Self-hosted operators handle these directly. SaaS providers absorb them.
• Legal exposure. Self-hosted operators are directly responsible for compliance with GDPR, CAN-SPAM, CASL. SaaS providers ship features that make compliance easier (one-click unsubscribe, signup verification, suppression lists). Self-hosted operators implement these themselves.

True crossover with these factors included is usually higher than the naive subscriber-count comparison suggests. Maybe 100K-200K subscribers depending on send frequency and operational sophistication. Below that, SaaS economic advantage is bigger than it looks. Above that, self-hosted advantage is also bigger than it looks.

Past pure economics, specific reasons that push toward self-hosted regardless of size. The most common one isn't even cost. It's the structural risk of running a business that depends on email through an intermediary that can terminate you on 24 hours' notice with no appeal process and no way to migrate your subscriber list before the lights go out. SaaS providers don't always exercise that power, but they reserve it explicitly in their terms, and certain industries trigger it predictably. If you're in one of those industries, self-hosted is essential infrastructure, not a luxury.

• SaaS termination risk. Mailchimp, ConvertKit, ActiveCampaign all reserve broad rights to terminate accounts. Industries that regularly trigger termination: cold outreach, certain crypto, gambling, adult, certain political mail, lead generation, multi-level marketing. If your business depends on email and your industry is termination-prone, the SaaS dependency is existential risk.
• Data sovereignty. Healthcare, legal, finance, government. Subscriber data on US-based SaaS infrastructure may violate contractual or regulatory requirements. Self-hosted in your chosen jurisdiction solves it.
• Custom workflows. Sophisticated automations that SaaS UIs can't express. Multi-step decision trees with external API calls. Application logic that needs to live alongside the email infrastructure rather than as an afterthought.
• Reseller business. Running ESP-as-a-service for your own customers. Can't do that on top of someone else's SaaS at a viable margin.
• Multi-brand operations. Multiple separate brands that should be operated independently and not cross-linked through a single SaaS account.

Don't over-engineer. SaaS is the right answer in many situations.

• Volume below 50K subscribers. Self-hosted overhead doesn't pay back.
• No engineering team. Operating an MTA cluster requires someone with relevant skills. Without them, self-hosted produces worse outcomes than SaaS, not better.
• Mainstream ESP-friendly business. If your business doesn't risk SaaS termination, the SaaS route is operationally simpler and reduces the surface area you have to manage.
• Need built-in features SaaS provides. Drag-and-drop email builders, e-commerce integrations, signup-form widgets, A/B testing UIs. SaaS UIs are mature; self-hosted equivalents are usually less polished.
• Compliance-heavy regulated content. Sometimes SaaS providers handle parts of compliance for you. Self-hosted means owning all of it.

Increasingly common: SaaS for one workload, self-hosted for another.

• Transactional via SaaS, marketing self-hosted. Postmark or AWS SES for password resets and order confirmations (high reputation cost, low volume). MailWizz + PowerMTA for marketing campaigns (high volume, segmentation needs).
• Public brands SaaS, sensitive brands self-hosted. Most products on Mailchimp; the politically sensitive product on dedicated infrastructure to avoid termination risk.
• SaaS for lower-volume customers, self-hosted for high-volume. Reseller or agency model where small clients are routed through SaaS and large clients have their own dedicated infrastructure.

Hybrid setups need clear separation of subscriber data and reputation profiles. Subscribers in two systems means double the suppression-list management burden. Doable, but adds operational complexity that should be weighed against the savings.

The breakeven analysis above used 2024-era Mailchimp pricing. The 2026 baseline is meaningfully different and shifts every threshold downward. Anyone running this comparison in 2026 should use current numbers, not numbers from older guidance.

Mailchimp changed pricing twice in the first four months of 2026. In January, the free plan was cut from 500 contacts and 1,000 monthly sends down to 250 contacts and 500 sends, effective February 17. In April, legacy plan users who created their accounts before May 2019 and never migrated to a current tier were hit with an 11-13% price increase. Since Intuit acquired Mailchimp for USD 12 billion in 2021, paid-plan pricing has increased 30-33%, roughly three times the rate of most competitors over the same period. The free plan has gone from 2,000 contacts in 2022, to 500 in 2023, to 250 in 2026. Automation was stripped from the free tier entirely by mid-2025.

The per-subscriber math at scale in 2026 looks like this: at 10,000 subscribers, Mailchimp runs USD 200-350 per month versus USD 49-99 for comparable alternatives. At 100,000 subscribers, Mailchimp tiers run USD 1,000+ per month while beehiiv's Scale plan covers the full subscriber range at a flat USD 43 per month on annual billing. The gap widens with every pricing cycle, and Mailchimp has shown no indication that the trajectory will reverse.

The structural consequence: the 50K-100K subscriber breakeven from 2024-era guidance has moved down to roughly 10K-30K subscribers in 2026 for senders sending 2-3 times per week. Senders above that range should run the math with current Mailchimp pricing rather than legacy numbers. Many will find self-hosting (or migration to a cheaper managed alternative) pays back inside the first month.

Most legacy mailchimp-vs-self framing treats the decision as binary: stay on Mailchimp or move to self-hosting. That framing made sense in 2022 when managed alternatives were either as expensive as Mailchimp (ActiveCampaign, HubSpot) or operationally limited (early ConvertKit, MailerLite). The 2026 landscape is different. Several managed alternatives have matured into credible competitors that capture most of the cost benefit relative to Mailchimp without the operational overhead of self-hosting.

For most newsletter publishers under 50K subscribers, beehiiv, ConvertKit (now Kit), MailerLite, or Brevo are probably the better choice. They run USD 0-99 per month for typical newsletter use cases, integrate with the major distribution and analytics platforms, and require no infrastructure operational overhead. The newsletter migration case study (linked elsewhere in our case-study library) documents one specific publisher's decision to go self-hosted at 180K subscribers; the same publisher at 20K subscribers would likely have chosen beehiiv or a similar managed alternative rather than self-hosting.

Self-hosting becomes the right answer in three specific situations. First, when subscriber count and send frequency push monthly Mailchimp cost above USD 1,000-1,500 and the team has the operational capacity to manage infrastructure. Second, when editorial-policy concerns make managed platforms a structural risk (publishers in politically-adjacent or commentary-heavy niches frequently fall into this category). Third, when specific feature requirements (advanced segmentation across multiple lists, custom data integration, multi-tenant management for agency-like operations) push beyond what managed platforms support. Outside these situations, the operational overhead of self-hosting rarely pays back.

The decision matrix in 2026 has effectively three axes: subscriber count and frequency drive cost, editorial-policy posture drives platform risk, and feature requirements drive technical fit. Self-hosting wins when at least two of these three axes push toward it. Managed alternatives win when at most one does. Mailchimp specifically wins only when the team has organisational inertia around its specific tooling and the cost is not yet painful enough to motivate the migration work, which is the position most established Mailchimp customers find themselves in until pricing crosses an internal threshold.

Migration from Mailchimp to any alternative (managed or self-hosted) involves specific data and configuration that transfers cleanly versus requires rebuilding. Understanding which is which up-front avoids the most common migration failure mode: assuming reputation and engagement history transfer when they do not.

Transfers cleanly: subscriber list (via CSV export), basic tags and segmentation rules (with field mapping during import), suppression list of bounces and unsubscribes (also via CSV), basic template content (HTML can be re-imported with minor adjustments).

Requires rebuilding: automation workflows (each platform uses different syntax for triggers and branches), template-level features like merge tags and conditional content (proprietary syntax does not translate), integrations with e-commerce platforms, CRMs, and analytics tools (each integration is platform-specific), audience scoring rules where they exist.

Does not transfer at all: sender reputation. Reputation lives at the sending IP and domain level, not at the platform level. Moving to new infrastructure means starting reputation from neutral, which is recoverable but never free. Senders who skip this consideration and run a flat cutover commonly produce 4-6 weeks of degraded delivery during the new-infrastructure warmup period. The parallel-period strategy documented in the newsletter-migration case study addresses this by running both infrastructures simultaneously for 30 days while subscriber traffic shifts progressively, which preserves placement through the transition.

Engagement history (open and click data per subscriber, historical send performance) typically does not migrate. Most platforms store this in proprietary formats and migration tools do not handle it. The practical workaround is to export raw engagement data before cutover, archive it for reference, and accept that the new platform starts with zero engagement history. For most newsletter operations this loss is manageable; for sophisticated segmentation programs that depend on multi-month engagement history, it requires explicit planning to reconstruct equivalent segmentation rules on the new platform from whatever transferred data is available.