What is newsletter publisher hosting?

Newsletter publisher hosting describes infrastructure for B2C email publishers sending newsletters to opt-in subscriber lists at scale. The operational requirements differ from cold email or transactional email: lists are large (10K-10M+ subscribers), sends are concentrated (one email reaches the full list within minutes), content is editorial rather than promotional, and the publisher's economics depend on inbox placement to drive opens and ad revenue.

Why do newsletter publishers leave ESPs like Mailchimp and Substack?

Three reasons dominate. First, cost: ESP pricing scales linearly with list size, often $1-$3 per 1000 subscribers per month plus per-send fees. A 100K subscriber list on Mailchimp runs $300-$500/month minimum. Second, content restrictions: ESP terms restrict certain content categories (crypto, adult-adjacent, certain political content). Third, operational control: ESPs control list segmentation, sending schedule constraints, and feature rollouts in ways that publishers operating their own infrastructure can avoid.

What infrastructure do newsletter publishers actually need?

A typical newsletter publisher with 100K-1M subscribers needs: dedicated SMTP infrastructure with multiple dedicated IPs, list segmentation by engagement, warmup capacity for adding new IPs as the list grows, FBL processing, custom rDNS per sending IP, bounce processing to maintain list hygiene, and operational support for deliverability issues. The infrastructure scales linearly with list size and send frequency.

How does ASH pricing compare to Mailchimp at newsletter scale?

A 100K subscriber list sending 2 messages per week on Mailchimp runs approximately $300-$500/month. Same list and frequency on our Scale tier (€149/month) plus 4-8 dedicated IPs (€20-€40/month additional) plus dedicated server (€99-€199/month if needed) totals €270-€400/month. Pricing is similar at this scale but the operational properties are different: ASH provides dedicated IPs, custom rDNS, content latitude. The cost advantage grows with scale: at 1M subscribers self-hosted runs roughly half the ESP cost.

Can ASH serve newsletter platforms running MailWizz or Acelle?

Yes. Many newsletter publishers run their own newsletter platforms (MailWizz, Acelle Mail, Sendy, custom platforms) for cost and control reasons. We offer dedicated MailWizz and Acelle server packages as well as PowerMTA infrastructure for the underlying SMTP delivery. The architecture is: newsletter platform handles list management and campaign creation, PowerMTA handles the actual SMTP delivery to recipients.

What is the deliverability difference from Mailchimp/Substack?

Mainstream ESPs operate large shared IP pools where individual sender reputation gets averaged with thousands of other senders. Dedicated IPs at offshore SMTP providers like ASH put the reputation entirely under your control. For sustained high-quality sending, dedicated IPs typically produce better deliverability than shared pools. For inconsistent or new senders, shared pools provide reputation buffering.

What content categories does ASH support that mainstream ESPs do not?

We support most legal content categories that mainstream ESPs decline. Cryptocurrency newsletters, political commentary across the spectrum, adult industry news (not explicit adult content), certain financial topics, recreational substance information in legal jurisdictions, gambling-adjacent content, and journalism critical of governments. We do not support: pure scam operations, content facilitating illegal activity, malware distribution, phishing infrastructure, or content directed at minors inappropriately.

What about GDPR and CAN-SPAM compliance?

Compliance is the publisher's responsibility. Publishers must comply with GDPR for EU recipients, CAN-SPAM for US recipients, CASL for Canadian recipients, and similar regional frameworks. Our infrastructure supports compliance requirements (list management, unsubscribe processing, one-click unsubscribe per RFC 8058) but does not enforce them. We provide the infrastructure; compliance posture is the publisher's operational choice.

B2C scale · Dedicated IPs · List-managed warmup

Hosting for Newsletter Publishers
infrastructure for operators leaving SaaS ESPs at scale.

At 50K subscribers Mailchimp is convenient. At 500K subscribers Mailchimp is expensive. At 5M subscribers the economics force every serious publisher to self-hosted infrastructure regardless of content policy. We are the infrastructure layer for that migration.

Quick answer

Newsletter publisher hosting requires infrastructure for sending B2C newsletters to opt-in lists at scale: dedicated SMTP with multiple dedicated IPs, list segmentation by engagement, warmup capacity for new IPs, FBL processing, custom rDNS per IP, and bounce processing for list hygiene. Mainstream ESPs (Mailchimp, Substack, Beehiiv) work for early-stage publishers but become expensive at 100K+ subscribers and impose content restrictions. Self-hosted alternatives (MailWizz, Acelle, Sendy) on PowerMTA-tuned offshore infrastructure typically cost 30-60% less than ESPs at scale and provide content latitude ESPs do not. Pricing starts around €270-€400/month for 100K subscriber operations.

Key facts about newsletter publisher hosting

List size tiers: 10K-100K (early stage), 100K-1M (growth stage), 1M-10M (mature publisher), 10M+ (large media operations).
Mainstream ESP pricing at scale: Mailchimp at 100K subscribers ~$300/month, 500K ~$1500/month, 1M ~$3000/month. Beehiiv at 100K ~$200/month, 1M ~$2500/month.
Self-hosted infrastructure at same scale: 100K subscribers on PowerMTA + MailWizz at €270-€400/month. 1M subscribers at €600-€1200/month. Cost advantage grows with scale.
Authentication requirements: SPF, DKIM (2048-bit), DMARC mandatory per Gmail/Yahoo February 2024 bulk-sender rules. Microsoft enforced May 2025. One-click unsubscribe per RFC 8058 required since June 2024.
Complaint rate tolerance: Gmail Postmaster Tools v2 enforces 0.1% complaint rate threshold. Above 0.3% triggers deliverability degradation. Above 0.5% can produce wholesale blocking.
Bounce processing: Hard bounces must be suppressed immediately. Soft bounces require retry logic with eventual suppression after consecutive failures. List hygiene practice directly affects deliverability.
List segmentation by engagement: Mature publishers separate engaged subscribers (opened or clicked in last 30-90 days) from unengaged on different sending IPs.
Common platform options: MailWizz (self-hosted ESP at €69 license + monthly), Acelle Mail (open-source alternative), Sendy (one-time $69 license), Listmonk (open-source Go-based), custom platforms.

The publisher journey from ESP to self-hosted

Most newsletter publishers start on a mainstream ESP. Mailchimp, ConvertKit (now Kit), Substack, Beehiiv, Buttondown, Ghost (which uses Mailgun under the hood), or similar. The ESP provides everything needed for the early stage: list management UI, template editor, signup form embeds, basic analytics, managed deliverability. At small scale (under 10K subscribers, sending weekly or less), this works well.

The pressure to migrate builds at predictable points.

Pricing pressure at 50K-200K subscribers

ESP pricing scales linearly with list size. A 50K list runs $100-$200/month at most ESPs. A 200K list runs $400-$800/month. At this tier, infrastructure costs become a meaningful line item in newsletter economics. Publishers comparing ESP costs against the equivalent self-hosted setup begin running the numbers and finding the gap meaningful.

Content policy pressure

Publishers operating in specific content categories find their ESP relationships becoming uncomfortable. Crypto newsletters get warnings about "high-risk" classifications. Political newsletters get caught up in periodic platform policy changes. Adult-adjacent content (not explicit, but topics like dating, alcohol, gambling) faces inconsistent enforcement. Publishers operating in these segments live with the latent risk that their ESP relationship could be terminated at any time, sometimes with weeks of notice and sometimes immediately.

Operational control pressure

Mature publishers want operational control that ESPs do not provide. The ability to send at specific times based on engagement patterns rather than ESP-imposed schedule limits. The ability to integrate custom analytics and tracking. The ability to use proprietary templating systems. The ability to control specific deliverability practices that ESPs handle automatically (or do not handle well).

The migration tipping point

Each publisher has a personal tipping point where the migration to self-hosted infrastructure becomes operationally sensible. The tipping point is typically when ESP costs exceed approximately $500/month, content policy concerns reach a specific threat level, or operational frustrations accumulate to the point where building custom infrastructure feels less risky than continuing the status quo.

The self-hosted newsletter architecture

The standard self-hosted newsletter stack has several layers that interact in specific ways.

Layer 1: Newsletter platform

The application that handles list management, subscriber signup, campaign creation, sending scheduling, and analytics. The dominant options are MailWizz (commercial PHP application $69 license, mature, widely-used, multi-tenant capable), Acelle Mail (open-source MailWizz alternative with similar feature set), Sendy (commercial $69 one-time, built specifically for Amazon SES but adaptable), Listmonk (open-source Go-based platform with modern UI and good performance), and custom platforms (Rails, Django, Go for larger publishers).

Layer 2: SMTP infrastructure

The mail transfer agent that actually delivers messages to recipient mailbox providers. The dominant options are PowerMTA (commercial industry-standard with significant license cost but high performance and mature deliverability tooling), Postal (open-source alternative with reasonable performance and free license), Postfix with tuning (open-source standard that works at moderate scale but has performance limitations at high volume), and Halon (commercial alternative to PowerMTA used by some large ESPs).

Layer 3: Infrastructure hosting

The actual servers running the above layers. The infrastructure requirements include clean dedicated IPs (critical), port 25 outbound open (essential), custom rDNS configurable (essential), enough compute and I/O for the volume, network capacity for spike sends, and DDoS protection for visible publisher sites.

Layer 4: Operational tooling

FBL processing (incoming complaint messages from Microsoft, Yahoo, Comcast, others). Postmaster Tools v2 monitoring (Gmail compliance). SNDS monitoring (Microsoft IP reputation). Bounce processing (suppression list management). Authentication maintenance (DKIM key rotation, SPF record updates). Deliverability monitoring across major receivers.

What we provide and what we do not

We specifically provide layer 3 and layer 4 of the architecture above. We can also provide layer 2 (PowerMTA managed servers, Postal on dedicated infrastructure, Postfix on customer VPS). Layer 1 (the newsletter platform) is the customer's choice; we support all standard options.

Our typical newsletter publisher customer runs MailWizz or Acelle on our infrastructure with PowerMTA handling SMTP delivery.

Component	Hosted by	Customer responsibility
Newsletter platform (MailWizz/Acelle)	ASH dedicated/VPS	Configuration, templates, lists
PowerMTA SMTP	ASH managed server	Customer access if requested
Database (MySQL/MariaDB)	ASH infrastructure	Backups (auto + verification)
IPs and rDNS	ASH (assigned + configured)	Choose sending hostname
Authentication (SPF/DKIM/DMARC)	Guided setup at onboarding	Publish DNS records
FBL processing	ASH centralized	Configure suppression actions
Postmaster Tools enrollment	Guided	Customer Google account
List management	Customer in MailWizz/Acelle	All list operations
Content and design	Customer	All editorial
Compliance (GDPR/CAN-SPAM)	Infrastructure supports	Customer compliance posture
IP warmup	ASH managed	Coordinate with launch
Bounce processing	Configurable per customer	Suppression policies
Deliverability monitoring	Both layers	Respond to issues

The pricing comparison in detail

Honest comparison of self-hosted infrastructure costs versus mainstream ESP costs requires looking at total operational cost rather than just infrastructure pricing.

Mailchimp at 100K subscribers

Standard plan with 100K contacts and 1.2M monthly sends (2 sends/week to full list) runs approximately $475/month. Higher tiers (Premium) add features at higher prices. The customer gets managed UI, automated deliverability, segmentation, automations, A/B testing, integrations, and support.

Beehiiv at 100K subscribers

Growth plan starting at $79/month at 10K, scaling to approximately $400/month at 100K subscribers with full features. The customer gets modern UI, monetization features, and simpler workflow than Mailchimp.

Self-hosted on ASH at 100K subscribers

MailWizz license (one-time €69 amortized) plus ASH Scale tier (€149/month) plus 4 dedicated IPs (€32/month) plus dedicated database server if needed (€99/month) equals approximately €282-€412/month total. The customer gets full operational control, dedicated IPs with customer-owned reputation, content latitude, no per-subscriber pricing, and ability to scale to larger lists without proportional cost increases.

The crossover point

At 100K subscribers, the costs are comparable. At 250K subscribers, self-hosted becomes meaningfully cheaper. At 1M subscribers, self-hosted runs roughly half the ESP cost. The economic case for migration strengthens with scale.

The hidden cost of self-hosting

Self-hosted requires operational competence the customer either has internally or pays for externally. Setting up MailWizz, integrating PowerMTA, configuring authentication, monitoring deliverability, handling FBL feedback, processing bounces — these are operational tasks ESPs handle automatically. Publishers who underestimate this operational overhead end up either spending consultant fees that erode the cost advantage or experiencing deliverability problems that erode the revenue side.

The dedicated IP question for newsletters

Dedicated IPs are operationally significant for newsletter publishers but the value depends on volume and list quality.

Why dedicated IPs matter for newsletters

Sender reputation at major mailbox providers is largely IP-based. Dedicated IPs put the reputation entirely under the publisher's control. Good sending practice (engaged list, low complaint rate, high inbox placement) builds positive reputation specifically on the publisher's IPs. The reputation accumulates over months and produces compounding deliverability benefits.

When dedicated IPs are operationally premature

Dedicated IPs require warmup. A new dedicated IP starts with neutral reputation and must build positive reputation through controlled sending. Publishers sending below 50K daily messages cannot generate enough volume to maintain positive reputation on dedicated IPs; the IP sits idle most of the time and the reputation does not build. Below this volume threshold, shared pools at mainstream ESPs often outperform dedicated IPs.

When dedicated IPs are operationally essential

Publishers sending above 500K daily messages should use dedicated IPs. The volume is sufficient to maintain reputation. The risk of being averaged with other senders in shared pools (potential reputation damage from other senders' issues) outweighs the benefit of pool buffering. Custom rDNS per IP is also operationally important at this scale for branding and authentication.

The IP segmentation pattern at scale

Large publishers use multiple dedicated IPs for list segmentation by engagement. The pattern: engaged subscribers (opened or clicked in recent campaigns) get sent from "Tier 1" IPs that maintain high reputation. Less-engaged subscribers (have not engaged in 30-90 days) get sent from "Tier 2" IPs where re-engagement attempts happen. Unengaged subscribers (no engagement in 180+ days) either get separate "Tier 3" IPs or get pruned from the list entirely. The segmentation preserves Tier 1 reputation while attempting re-engagement on lower-reputation infrastructure.

The categories of newsletter publishers we serve

Niche content publishers (50K-500K)

Newsletters covering specific topics with engaged audiences. Tech analysis, financial commentary, specific industry insights, cultural commentary. The audience is engaged enough to support self-hosted infrastructure economics; the topic is specific enough to potentially face ESP content concerns. This is the largest segment of our newsletter customer base.

Crypto and finance newsletters

Crypto-focused newsletters face periodic ESP termination as platform compliance shifts. Established crypto newsletters operate on self-hosted infrastructure as a stability measure regardless of cost optimization. Many of our customers in this segment migrated after ESP termination events.

Political and journalism newsletters

Independent journalism and political analysis newsletters face ESP content scrutiny that varies with platform priorities. Substack has been more permissive than Mailchimp historically; Mailchimp more permissive than Beehiiv; all have shifted over time. Publishers operating in politically sensitive content prefer infrastructure they control.

Adult-adjacent newsletters

Newsletters covering dating, alcohol, gambling, adult industry news (not explicit content) face inconsistent ESP enforcement. Some make it onto major ESPs through careful framing; others get terminated periodically. Self-hosted infrastructure provides stability.

Multi-language publishers

Publishers serving non-English audiences sometimes find mainstream ESPs less optimized for their use case. International deliverability through ESPs can be inconsistent. Self-hosted infrastructure with regional jurisdiction selection (our Bulgaria, Romania, Panama, Hong Kong, Singapore pops) lets publishers locate sending infrastructure closer to their audience.

Large legacy publishers

Established publishers (200K-2M subscribers) where ESP costs have grown to meaningful line items. The migration to self-hosted is primarily cost-driven rather than content-driven, but the additional operational control is welcomed.

What migration from ESP to self-hosted actually looks like

The migration is a multi-phase project rather than a switch. Phases typically run over 30-90 days.

Phase 1: Infrastructure setup (week 1)

Provision the infrastructure: MailWizz or Acelle on dedicated server, PowerMTA configured with the required VMTAs, dedicated IPs assigned and rDNS configured, database backed up and ready, authentication DNS records prepared.

Phase 2: List migration (week 1-2)

Export subscriber list from ESP. Verify the export quality (some ESPs withhold subscriber data on cancellation, requiring earlier export). Import to MailWizz/Acelle. Configure list segments matching the ESP setup.

Phase 3: Template recreation (week 2-3)

Newsletter templates rebuild in the new platform. Most templates do not transfer cleanly; styling needs to be tested in the new environment. Test sends to internal addresses verify rendering across major email clients.

Phase 4: IP warmup (week 2-8)

New dedicated IPs go through 30-45 day warmup. The warmup uses managed seed traffic or engaged-subscriber sub-lists. Production sending stays on the ESP during this phase to maintain revenue flow.

Phase 5: Cutover (week 8-10)

Once IPs are warmed and the new platform is verified, the actual cutover happens. Most publishers split-test the cutover: half the list gets sent from new infrastructure, half stays on ESP for one or two campaigns to verify equivalent deliverability before full migration.

Phase 6: ESP termination (week 10-12)

After verifying the new infrastructure performs at least as well as the ESP, cancel the ESP subscription. Most ESPs offer refunds for unused prepaid time; some do not. Plan the cutover timing to align with billing cycle if refund is uncertain.

Phase 7: Optimization (ongoing)

Self-hosted infrastructure rewards operational attention. Monitor Postmaster Tools, SNDS, and similar feedback systems. Adjust IP segmentation as list grows. Refresh DKIM keys quarterly. Update authentication setups for new domains. Coordinate with us on any deliverability anomalies.

What we honestly recommend against

Self-hosted infrastructure is not the right choice for every newsletter publisher.

Under 10K subscribers

The operational overhead exceeds the cost savings. Stick with mainstream ESPs (Beehiiv, ConvertKit, Mailchimp) where the cost is manageable and the operational layer is free.

Under 50K subscribers with no content policy concerns

The infrastructure setup time and ongoing operational attention outweigh the cost savings at this scale. ESPs work well enough.

Publishers without technical capability

Self-hosted requires technical familiarity with Linux, SMTP, DNS, and email infrastructure. Publishers who would need to hire consultants to manage the setup often find the consultant fees erode the cost advantage of self-hosting.

Publishers who value UI features over cost

Mainstream ESPs invest heavily in user interface, automation features, and integration ecosystems. MailWizz and Acelle have basic UIs that get the job done but do not match Substack or Beehiiv on user experience. Publishers who depend on advanced features (A/B testing, sophisticated automation, advanced analytics) should evaluate carefully whether self-hosted platforms support their actual usage patterns.