MailWizz Servers

All plans include EU-based dedicated servers, commercial MTA license, and full DKIM/SPF/DMARC/rDNS configuration. Extra IPs: €18/IP/month.

MailWizz Server: The Complete Buyer's Guide

People searching for 'MailWizz server hosting', 'managed MailWizz', or 'MailWizz dedicated server' are at the decision point between self-hosted and fully managed email marketing infrastructure. This guide covers everything you need to make that decision — and what to expect from a managed MailWizz environment.

What 'Managed MailWizz Server' Actually Means

MailWizz is a self-hosted application — you download it from the MailWizz website, install it on a server, and configure it. In theory, this is straightforward. In practice, a production MailWizz environment requires: a properly configured web server (Nginx/Apache), PHP-FPM with the right extensions and memory limits, MySQL optimization for large subscriber tables, cron job scheduling for delivery queues and bounce processing, SMTP delivery server connection, DKIM/SPF/DMARC configuration, and ongoing maintenance as MailWizz releases updates.

A managed MailWizz server means Cloud Server for Email handles all of that. You log in to MailWizz, upload your list, create your campaign, and send. We handle the infrastructure layer completely — server, software, authentication, delivery, monitoring, and updates.

MailWizz Server Plans: Technical Specifications

Each plan pairs MailWizz EMS running on our application cluster with a dedicated sending server. MailWizz never runs on the same server as the SMTP relay — this separation prevents resource contention at high send volumes and allows each component to be optimized independently.

• Application server (MailWizz): Multi-processor cluster with dedicated PHP workers, MySQL with InnoDB optimization, Redis for queue management, and automated weekly backups. All plans share this application layer — it is over-provisioned to handle any plan's campaign management demands.
• Sending server (dedicated per client): The server varies by plan (VPS for Starter/Basic, dedicated hardware for Standard and above). This is where your dedicated IPs live and where delivery happens. The hardware specifications in your plan apply to this server.
• Network: 1 Gbit/s unmetered on all plans. EU peering with DE-CIX Frankfurt and AMS-IX Amsterdam for low-latency delivery to European ISPs.

MailWizz Long-Tail: Specific Questions We Answer

MailWizz vs Mailchimp: Why Senders Switch

This is the most common migration path we see. Mailchimp users typically hit one of three walls: (1) per-subscriber pricing becomes significant above 25,000 subscribers, (2) account suspended after spam complaints on a campaign, or (3) inbox placement declines due to shared IP pool contamination from co-tenants. MailWizz on dedicated infrastructure solves all three: flat-rate pricing regardless of list size, no account suspensions for spam reports, and IP reputation isolation.

MailWizz Server Requirements: What You'd Need to Self-Host

If you were to self-host MailWizz on a VPS, the minimum requirements for production use are: PHP 8.1+ with extensions (curl, gd, openssl, mbstring, dom, pdo_mysql, imap), MySQL 5.7+/MariaDB 10.x, 2GB+ RAM (4GB+ recommended), cron jobs every 5 minutes, and a dedicated SMTP server for delivery. The VPS cost plus PowerMTA license cost plus your administration time typically exceeds our managed plans once volume exceeds 10,000 emails/day.

MailWizz Bounce Server: How It Works in Our Environment

MailWizz includes a native IMAP bounce server that monitors a designated inbox for bounce notification emails. In our managed environment, we configure this IMAP connection to our bounce processing server, which receives SMTP-level bounce responses forwarded by the delivery server. Hard bounces are suppressed within seconds of the SMTP rejection event — before MailWizz's normal cron-based processing cycle. This real-time suppression is important for list hygiene at high volume, where accumulating bounced addresses over hours can cause reputation damage during a single campaign send.

MailWizz API: Integrating with Your CRM or E-commerce Platform

MailWizz provides a full REST API for subscriber management, list management, campaign creation, and statistics retrieval. Common integrations from our clients: Salesforce to MailWizz subscriber sync via Zapier, WooCommerce customer post-purchase sequence via MailWizz API, HubSpot contact segmentation to MailWizz custom fields, and custom PHP/Python applications managing subscriber lifecycle via the API. We provide API documentation and connectivity testing as part of onboarding for Professional and higher plans.

MailWizz Server Plans FAQ

For a comparison of MailWizz against competing email marketing platforms, see our comparison library — including MailWizz vs Mailchimp, MailWizz vs SendGrid, and MailWizz vs Sendy.

MailWizz Server Security and Compliance

Running MailWizz on our managed EU infrastructure satisfies several compliance requirements that self-hosted or shared-ESP alternatives cannot address cleanly.

• GDPR Article 28 Data Processing Agreement: Available for all clients. Covers subscriber data processing purpose, retention, security measures, and breach notification. EU data residency — subscriber data never leaves EU servers.
• CAN-SPAM compliance headers: RFC 8058 List-Unsubscribe-Post injected at the relay level for all commercial messages. Required by Google for bulk senders since February 2024.
• CASL (Canada's Anti-Spam Legislation): MailWizz custom fields support consent date, consent source, and relationship type documentation for Canadian sender programs.
• Suppression list processing: Unsubscribes processed in real-time via MailWizz's native suppression list. Bounce suppressions added within seconds of SMTP-level rejection via our relay's Intelligence Bounce™ processing.
• Two-factor authentication: MailWizz admin panel can be protected with 2FA via plugin. Recommended for all production environments.

From Mailchimp, Klaviyo, or Brevo to MailWizz: Migration Guide

Migrating from a shared ESP to MailWizz on dedicated infrastructure is straightforward for list data but requires careful planning for IP warming. The process:

• Export your list: Download your subscriber list as CSV from your current ESP. Include engagement data (last open/click date) if available — this is critical for warming segmentation.
• Import to MailWizz: MailWizz imports standard CSV with custom field mapping. Engagement segments (30-day, 60-day, 90-day active) can be created during import using the engagement date field.
• IP warming parallel run: Keep sending from your current ESP for 8–12 weeks while warming new dedicated IPs with your most engaged segments. No disruption to your current sending program.
• Full migration: Once new IPs reach HIGH Postmaster Tools reputation, migrate full production volume to MailWizz and cancel your shared ESP subscription.
• Cost comparison: At 100,000 subscribers, Mailchimp costs €450–600/month. Our MailWizz Professional plan at €490/month includes unlimited subscribers and daily monitoring — comparable total cost with far better deliverability control.

We handle the technical side of migration for all Professional and Scale clients. Contact infrastructure@cloudserverforemail.com with your current ESP, subscriber count, and engagement data availability.