MailWizz · Managed hosting

Managed MailWizz hosting, running on the PowerMTA stack we built it for.

Unlimited lists, unlimited subscribers, unlimited campaigns. Dedicated IPs, deliverability engineering, proper SaaS mode for agencies. Everything MailWizz should be — without you touching the server. License included, free migration on Growth and above.

MailWizz license included
SaaS-ready
Dedicated IPs
PayPal & Stripe
Free migration
From €89/mo

See plans Talk to sales Chat on WhatsApp

Why managed matters

MailWizz is powerful. Self-hosting it correctly is a full-time job.

MailWizz is one of the best self-hosted email marketing platforms ever built — but only if the box underneath it is configured for the job. Most do-it-yourself deployments we inherit suffer from the same issues: misconfigured cron, under-powered MySQL, PHP ini that kills large imports, a shared IP that already has a deliverability history, SPF and DKIM missing or misaligned, and bounce processing that quietly stopped working six months ago.

Blue Spirit hosts MailWizz on top of the same dedicated PowerMTA stack we sell separately — but we do the systems work so the MailWizz experience is just the UI. You click "Send campaign" and a team of engineers stands behind that button.

Dedicated PowerMTA stack

Every MailWizz install runs on its own PowerMTA instance with virtual MTAs configured for marketing, transactional and cold workloads. Proper queueing, throttling, IP rotation.

MailWizz Extended license

Included in every plan. Multi-customer SaaS mode unlocked, unlimited subscribers, unlimited lists, unlimited campaigns. PayPal and Stripe payment gateways pre-configured.

Authentication done right

SPF aligned, DKIM 2048-bit rotated quarterly, DMARC published with reporting endpoint we monitor, MTA-STS in place. Postmaster Tools registered, FBLs subscribed for every major ISP.

Bounce processing & FBLs

PowerMTA accounting files parsed and posted back to MailWizz so suppression lists update automatically. JMRP, Yahoo FBL, AOL FBL active. Hard bounces and complaints removed within the same hour.

IP warm-up included

Every IP shipped with a 30-60 day warmup plan calibrated for your actual list and content. We monitor placement daily and pause sending from any IP that crosses our reputation thresholds.

Updates & security patches

MailWizz core updates, PHP and MySQL versions, OS security patches, plus weekly off-site backups and daily database snapshots — all handled in low-traffic windows without disrupting your sending.

2026 reality

The self-hosted ESP landscape changed in 2024 — here is what matters now.

If your last benchmark of self-hosted email marketing software was 2022, the field has shifted. Three changes reshaped how operators choose between MailWizz, Mautic, Acelle, Sendy, Listmonk and the rest of the open-source stack — and ignoring them costs money on a multi-year decision.

First, the bulk sender requirements made deliverability tooling table stakes. Pre-2024, you could install Sendy, point it at Amazon SES, and ship newsletters with a default DKIM and DMARC at p=none. That works no longer. Gmail and Yahoo since February 2024, and Microsoft since May 2025, all enforce SPF/DKIM alignment, RFC 8058 one-click unsubscribe in headers, sustained complaint rate under 0.1% operationally (the published 0.3% is theoretical), and DMARC published with monitoring. Self-hosted ESPs that do not handle this out of the box now require add-on tooling — and that tooling adds €1,500-2,500/year to the real TCO that the platform comparison pages never mention.

Second, Mautic's resource footprint stopped scaling cheaply. Mautic 5.x with the Symfony stack now needs at least 2GB RAM dedicated to PHP-FPM plus a healthy MySQL configuration plus Redis for queue management — practical minimum is a 4GB VPS, and at any meaningful volume you are on a dedicated server. Compared to MailWizz running comfortably on a single 1GB VPS for low-volume use, Mautic's "free" license costs more in hosting than MailWizz's $86 one-time across the first year. The community size advantage Mautic has (200K+ users) does not change the unit economics.

Third, Sendy's Amazon SES lock-in became a liability. SES has tightened its acceptable use policy three times since 2023, and operators report increased account suspensions for "patterns inconsistent with SES guidelines" — patterns that are perfectly normal for legitimate bulk marketing. Sendy is locked to SES; if SES suspends you, Sendy stops working. MailWizz's BYOSP (Bring Your Own Service Provider) architecture lets you run SES, SendGrid, Mailgun, dedicated PowerMTA, KumoMTA or generic SMTP simultaneously with rotation between them. That portability is the #1 architectural reason MailWizz stayed dominant in the self-hosted space.

The practical takeaway: in 2026, self-hosted ESP choice should optimize for two things — BYOSP flexibility (multi-provider routing) and bundled deliverability tooling (or a managed provider that handles it). The platforms that lock you to one SMTP provider or that require you to bolt on €2K of compliance tooling yourself are not actually cheaper than the managed alternatives once you do the math honestly.

Decision framework

Should MailWizz even be your platform? Decision tree.

Most "best self-hosted email platform" articles assume self-hosted is the right answer. We do not. The decision tree below is the same one we walk through on the discovery call to determine whether MailWizz hosting fits — including the branches that lead to "buy something else".

Two sub-points the diagram does not capture. First: even when DIY is the technically right answer (high volume + in-house team), most teams underestimate the ongoing maintenance load — MailWizz core updates, PHP version drift, MySQL tuning at scale, deliverability incidents at 2am. The DIY math looks great in month one and degrades quickly. Second: the SaaS branch (Mailchimp, ActiveCampaign) is the right answer more often than this market admits — if your monthly volume is genuinely under 50K and your engagement is healthy, the per-email economics of SaaS beat any self-hosted setup once you count operations time. We tell you on the call.

Our MailWizz stack — what actually runs underneath

Every Blue Spirit MailWizz install is provisioned on the same hardened stack. This is not a generic "VPS with PHP" — it is configured specifically for the MailWizz workload, calibrated against the actual bottlenecks we have seen across hundreds of deployments.

OS: AlmaLinux 9 or Ubuntu 22.04 LTS, hardened to CIS, automated security updates, kernel tuned for high-concurrency PHP-FPM and MySQL.
Web layer: nginx + PHP-FPM 8.2, opcache configured for MailWizz, fastcgi cache for static admin assets, gzip and brotli compression.
Database: MariaDB 10.11 or MySQL 8.0, tuned for MailWizz's specific query patterns (large list table scans, campaign bounce JOINs, segment evaluation), InnoDB buffer pool sized to fit your active dataset.
Cron: 8 separate MailWizz cron tasks running on independent schedules with proper locking, monitored individually so a stuck cron does not silently break campaign sending.
MTA layer: PowerMTA 6.0 with virtual MTAs configured per pool (marketing, transactional, cold), per-ISP throttling pre-tuned, integrated with MailWizz via SMTP and bounce/FBL feedback loops.
Authentication: SPF aligned, DKIM 2048-bit rotated quarterly, DMARC published with reporting endpoint, MTA-STS, TLS-RPT, BIMI when ready.
Backup: daily MySQL dump retained 7 days, weekly full filesystem snapshot retained 4 weeks, monthly off-site backup retained 6 months. Restore tested quarterly.
Monitoring: Prometheus metrics scraped every 15 seconds, Grafana dashboards for MailWizz queue depth + delivery rate + bounce rate per ISP + reputation trends + database health. Alerts route to our on-call rotation.

All of this is documented in your client folder and accessible via a read-only Grafana login. You do not have to trust us; you can see the numbers.

MailWizz + PowerMTA architecture — how a campaign actually sends.

The architectural diagram below shows what happens between you clicking "Send campaign" in the MailWizz UI and a recipient receiving the email in their inbox. Each layer is a place where a DIY deployment commonly breaks; we operate every layer.

Three architectural decisions in this stack worth highlighting because they are the difference between passable and excellent. First: transactional and cold pools are isolated, not shared with marketing. They have their own IPs, their own DKIM selectors, their own subdomains, their own throttling. The most common avoidable mistake we see in audits of other providers' MailWizz deployments is transactional traffic running on the marketing pool — which means a bad marketing campaign silently degrades critical password reset emails. Second: cron jobs are independent and individually monitored. MailWizz has 8 separate cron tasks (campaigns, bounce processing, FBL processing, list segments, autoresponders, etc.) and a default cron crontab runs them all in one job. When one stucks, all stop. Our setup runs each independently with its own monitoring. Third: per-ISP throttling values are not generic. The numbers in the diagram are starting points; real production tuning happens per-pool, per-ISP, per-warmup-phase. That tuning is what the managed plan pays for.

Who uses Blue Spirit's MailWizz hosting

Three operator profiles dominate our MailWizz client base, and the plans are sized for each. Understanding which profile you fit shapes which plan tier we recommend and which features matter most during onboarding.

Email marketing agencies reselling to multiple end customers run the SaaS mode of MailWizz with white-label branding, per-customer billing through PayPal/Stripe, and per-customer sending limits we help calibrate. We have agencies running 30+ end clients on a single Growth deployment, with separate sub-accounts per client and isolated reputation contained at the client level. The economics work because the agency charges €300-1,500/month per end client, of which the infrastructure cost is a fixed line item rather than a per-customer variable. Our role is to keep the platform running and the deliverability healthy; the agency owns the relationship with their customers and the campaign content.

Publishers and content businesses running large newsletter operations (200K-2M subscribers) use MailWizz directly for their own list, with sophisticated segmentation, automation, A/B testing across audience cohorts. Plain MailWizz UI, our infrastructure underneath. Open and click rates land where they should because deliverability is engineered, not improvised. The pattern we see: publishers who started on Mailchimp or ConvertKit grow past the price-per-subscriber inflection point (typically around 100K subscribers where SaaS pricing exceeds €500/month) and migrate to managed self-hosted to flatten the cost curve. We migrate the list, the templates, the segments, the automations — operations continue without a campaign-shaped gap.

Email marketing SaaS builders use MailWizz as the back-end of their own product — a custom front-end calls the MailWizz API, end customers never see MailWizz UI directly. We have several SaaS clients running this pattern with their own custom branding stacked on the API layer, with us as the silent infrastructure partner. This is the highest-leverage use case for MailWizz hosting because the SaaS builder gets a battle-tested email engine without writing one, and we provide the operational guarantee that the infrastructure stays current with mailbox provider requirements as they shift. The MailWizz API surface covers what most builders need; for gaps, we have helped clients choose between extending MailWizz (cheaper, slower) and writing a thin compatibility layer (more flexible, more code).

Five mistakes we keep finding in DIY MailWizz setups

About a third of our new MailWizz clients arrive after running it themselves for some time and hitting a wall. We audit the inherited setup before migrating. The five mistakes below account for over 75% of what we find:

1. Default cron entry running everything in one job

The MailWizz docs show a single cron entry that runs all 8 tasks sequentially. It works on day one. Six months later, the campaign send cron gets stuck because the bounce processing cron got into a bad state, and the entire pipeline halts silently. The fix is 8 independent cron entries with proper locking via flock, each monitored separately so a stuck cron is detected within minutes. We have rescued multiple clients whose campaigns simply stopped sending and they did not know for days.

2. PHP memory_limit and max_execution_time at default values

Default PHP settings (memory_limit 128M, max_execution_time 30s) work for small lists. They fail catastrophically at 500K+ subscribers per list. Imports time out, segment evaluation crashes mid-flight, large campaigns take days instead of hours. Our standard tuning is memory_limit 512M for CLI, max_execution_time 0 (unlimited) for cron, opcache appropriately sized. The DIY setups we inherit almost universally run at default and the operators do not know why their imports keep failing.

3. SMTP delivery server pointed at shared cloud SMTP

Operators set up MailWizz, point the delivery server at a shared SendGrid or Mailgun account, ship newsletters. It works for a few months. Then a single bad campaign on the shared cloud platform tanks the IP reputation of the entire shared pool — and your perfectly clean program suffers because someone else's list is dirty. The architecturally correct setup is dedicated IPs (either via SendGrid Pro / Mailgun Dedicated, or via PowerMTA/KumoMTA managed) with reputation isolated to your sending alone. The cost difference at meaningful volume is small; the reputation difference is enormous.

4. Bounce processing not actually running, or running but not posting back to suppression

MailWizz's bounce server can read POP3 or process server-side accounting files. The DIY setup we inherit usually has it configured but not running, or running but with a misconfigured suppression flow that processes bounces internally without actually adding them to the suppression list. Result: the next campaign re-sends to known hard-bounced addresses, complaint rate spikes, reputation degrades. Fix: bounce processing posted back to MailWizz API every 60 seconds, hard bounces and complaints removed from active lists in the same minute they arrive.

5. SPF/DKIM/DMARC misalignment on the From domain

The most common single mistake. MailWizz is configured to send From your-brand.com but the SPF record only authorizes the SMTP provider's hosts, the DKIM signature uses a generic d= value that does not match the From domain, and DMARC is at p=none with no monitoring. The mail "delivers" in the sense that it returns 250 OK, but Gmail and Microsoft both filter it to spam silently. Fix: SPF aligned with From domain via includes for the actual delivery infrastructure, DKIM d= matching the From domain, DMARC at p=quarantine or p=reject with reporting endpoint we monitor.

MailWizz vs the alternatives — feature comparison.

Most "MailWizz vs X" comparisons are written by vendors with skin in the game. Here is the matrix as we see it from the operations side, after running multiple of these in production. Tick the cells that match your requirements; that tells you the right answer.

Capability	MailWizz	Sendy	Mautic	Acelle	Listmonk
License cost (one-time USD)	$86 (Reg) / $449 (Ext)	$69	$0 (GPL)	$59-$199	$0 (AGPL)
BYOSP (multi-SMTP)	Yes — SES, SG, MG, custom	Amazon SES only	Yes	Yes	Yes (SMTP)
SaaS mode (multi-customer)	Yes (Extended)	No	Limited	Yes	No
Automation workflows	Yes	No	Most powerful in class	Yes	Basic
A/B testing	Yes	No	Yes	Yes	No
Stack (language)	PHP / Yii	PHP	PHP / Symfony (heavy)	PHP / Laravel	Go (lightweight)
Min RAM (production)	1-2 GB	512 MB	2-4 GB	1-2 GB	256 MB
Community size 2026	Largest self-hosted ESP	Established	200K+ users	Smaller	Growing fast
Plugin ecosystem	CodeCanyon (50+ plugins)	Limited	Extensive	Limited	Minimal
Best fit profile	Agency / SaaS / publisher	Solo blog / minimal newsletter	Marketing automation needs	Similar to MailWizz, smaller	Tech-savvy minimal newsletter

Reading the table honestly: Listmonk wins on resource efficiency if you only need newsletter sending and your team is comfortable with Go and a minimal interface. Sendy wins on simplicity and price for solo operators with all-Amazon-SES workflows and basic newsletter needs. Mautic wins on automation depth if you need full marketing automation with lead scoring, landing pages, multi-channel — but its resource footprint and operational complexity push it toward teams with dedicated DevOps. MailWizz wins for the agency/SaaS/publisher profile — the specific combination of mature SaaS mode, BYOSP flexibility, and broad plugin ecosystem fits this operator type better than any alternative. What we sell — managed MailWizz on PowerMTA — bundles MailWizz's flexibility with the operational simplicity of SaaS at a price point comparable to running it yourself once you count engineering time honestly.

The real cost of running MailWizz — license is 5% of TCO.

License is what marketing pages compare. Operations time is what your CFO ends up paying. The chart below is the realistic year-1 TCO for an in-house MailWizz deployment matched to our Growth plan.

The real cost of running MailWizz — license is 5% of TCO

Annual cost breakdown for a small-to-medium MailWizz deployment, USD.

Annual MailWizz TCO breakdown by cost category
Categoría	Annual cost USD
MailWizz Extended license	200
Server + bandwidth	1800
Operations time (SRE)	12480
Deliverability tooling	2000
Incident overhead	3500

Operations time assumes a part-time SRE at $80/hour for 3 hours/week. Deliverability tooling includes Postmaster, GlockApps, MXToolbox monitoring, blacklist scanners, DMARC report parser. Incident overhead amortizes typical incidents (one major outage / blacklist event per year). Server cost reflects a dedicated bare-metal box with 5 IPv4. License figure assumes Extended for SaaS mode.

Cost honesty

Year-1 total cost across self-hosted ESP options (1M emails/month).

The chart below normalizes year-1 total cost for a 1M emails/month operation across five typical paths plus our managed Growth plan. All numbers include license, hosting, operations time, and deliverability tooling — the components that differ across providers. SaaS at low volume is included as a benchmark point.

Year-1 total cost — self-hosted ESP options (USD, 2026)

License + hosting + operations time + deliverability tooling, for 1M emails/month.

Year-1 total cost in USD across self-hosted ESP options for 1M emails/month
Categoría	Year-1 total cost USD (license + ops + tooling)
Sendy + DIY hosting	16800
Listmonk (free, all DIY)	14500
Mautic + DIY hosting	19200
MailWizz + DIY hosting (1M/mo)	19980
Mailchimp Standard (250K)	4140
Blue Spirit MailWizz Growth	3236

Sendy DIY: $69 license + $1,800 hosting + $12,480 ops time at $80/hr × 3hr/wk + $2,000 deliverability tooling + $451 SES = $16,800. Listmonk: $0 license + $1,800 hosting + $10,400 ops time (lighter platform) + $2,000 tooling + $300 SMTP = $14,500. Mautic: $0 license + $3,600 hosting (heavier) + $13,000 ops time (more complex) + $2,300 tooling + $300 SMTP = $19,200. MailWizz DIY: $200 license + $1,800 hosting + $13,480 ops time + $2,000 tooling + $2,500 SMTP = $19,980. Mailchimp Standard 250K subs at ~$345/mo includes SaaS managed everything but lacks self-hosted control and BYOSP flexibility. Blue Spirit MailWizz Growth: €249/mo × 12 = €2,988 ≈ $3,236. The chart shows the managed Growth plan beats every DIY self-hosted option once operations time is honestly counted.

Three patterns the chart makes obvious. First: operations time dominates every DIY path. Even with a "free" license like Mautic or Listmonk, the 200-300 hours/year of skilled engineering time costs more than the managed alternative. Second: SaaS at low volume genuinely wins on simplicity — Mailchimp Standard at 250K subscribers is cheap, zero-ops, and totally appropriate if your volume and feature needs match. The argument for self-hosting starts above 500K subscribers or when you need BYOSP / SaaS mode that Mailchimp does not offer. Third: the gap between managed MailWizz and DIY MailWizz is approximately $16,000/year at this scale — that is roughly 200 hours of senior engineering time the operator gets back. For most teams, that is the entire argument.

What each plan actually sustains — volume and IP allocation.

The numbers below are what each plan sustains in steady state with a clean list and engaged audience, post-warm-up. They are deliberately conservative — we would rather under-promise and over-deliver. If your campaign mix is mostly transactional or highly engaged, you can push higher; if your list is questionable or your content is borderline, lower.

MailWizz hosting plans — sustainable volume and IP allocation

Daily emails sustainable post-warmup, dedicated IPs included per plan.

Sustainable daily volume and dedicated IPs by MailWizz plan tier
Categoría	Sustainable emails/day (post-warmup)	Dedicated IPs included
Starter (€89/mo)	250000	2
Growth (€249/mo)	1000000	5
Scale (€749/mo)	5000000	10

Volumes are conservative steady-state figures with bulk marketing content, post-warmup, on a clean list with engagement above 15%. Transactional loads or very engaged audiences sustain higher; questionable lists or borderline content sustain lower. Above Scale we go custom — talk to us about a dedicated PowerMTA cluster sized for your specific needs. Numbers exclude Enterprise plan which is bespoke.

What is included that competitors hide behind extra fees

MailWizz Extended license — yours to use while subscribed; no separate CodeCanyon purchase.
SaaS mode unlocked — multi-customer, payment gateways pre-configured, branding hooks ready.
Dedicated IPs with proper rDNS, warm-up, and reputation monitoring per IP.
PowerMTA license — included in the back-end stack, configured for your sending profile.
Bounce, FBL, suppression sync — bounces parsed every 60 seconds and pushed to MailWizz.
Postmaster Tools registration — Google Postmaster, Microsoft SNDS/JMRP, AOL FBL, Yahoo FBL.
SPF, DKIM (rotating 2048-bit), DMARC, MTA-STS, TLS-RPT all published and monitored.
Backups — daily MySQL snapshots retained 7 days, weekly off-site retained 4 weeks, monthly off-site retained 6 months.
Updates — MailWizz core, PHP, MySQL, OS — applied in low-traffic windows with staging validation for major versions.
Migration from Sendy/Mautic/Acelle/Mailchimp/existing MailWizz — free on Growth and above, €500 one-off on Starter.
Engineer access — direct chat for incidents, weekly office hours for planning questions.

What is not included (on purpose)

Custom MailWizz development — adding new features to MailWizz core or building custom plugins. We can recommend trusted developers.
Email content / copywriting — we host the platform, not your campaigns. Your team owns the content.
List acquisition — we do not provide subscriber lists, scrape contacts, or facilitate any list-buying. Doing so is against our acceptable use policy.
Open-ended consulting — for strategic deliverability work see our Audit and Recovery products. The MailWizz hosting price covers operating the platform; deep-dive strategy work is priced separately.

When MailWizz hosting is NOT for you

Volume below 50,000 emails/month with no agency reselling. SaaS platforms (Mailchimp, ActiveCampaign, ConvertKit) are cheaper at this scale. Come back when you cross 100K/month or when SaaS pricing starts to hurt.

Pure transactional workload. If you are sending password resets and order confirmations only, Postmark or Amazon SES is purpose-built. MailWizz's marketing-oriented UI is overkill for transactional-only.

Cold email B2B as primary use case. See our Cold Email Infrastructure product. MailWizz can run cold campaigns but the architecture is optimized for permission-based marketing; cold programs need different tooling (mailbox rotation, per-mailbox monitoring, swap-on-burn).

We turn down 1 in 4 prospective clients on these criteria. The 3 in 4 we accept tend to scale well precisely because we make sure the fit is right at the start. The discovery call exists to figure this out — if the conversation reveals you need something different from MailWizz hosting, we redirect you to the right product (audit, recovery, cold email infrastructure, PowerMTA hosting, or a SaaS recommendation) without trying to force-fit the wrong tool. Senior engineering time is too expensive for everyone to waste on misaligned engagements.

MailWizz hosting plans

Transparent monthly pricing, all-inclusive scope. License, IPs, deliverability engineering, monitoring, updates — all bundled.

MailWizz Starter

From

€ 89 /month

Setup: € 29

Managed MailWizz + PowerMTA stack
2 dedicated IPv4 + rotation
Up to 250k emails/day
Unlimited lists, subscribers & campaigns
DKIM, SPF, DMARC pre-configured
cPanel access for files
Weekly backups
Email ticket support

Request a quote

MailWizz Growth

From

€ 169 /month

Setup: € 29

Managed MailWizz + PowerMTA stack
5 dedicated IPv4 with PTR
Up to 1M emails/day
SaaS mode: unlimited customers & plans
Payment gateways (PayPal, Stripe) ready
24/7 IP reputation monitoring
Fortnightly IP cleaning
Priority ticket support + WhatsApp

Request a quote

MailWizz Scale

From

€ 279 /month

Setup: Free

8 vCPU · 16 GB RAM dedicated server
10 dedicated IPv4
Up to 5M emails/day
Multi-VMTA advanced routing
Redis + MySQL tuning for concurrency
CDN for tracking links
Priority support (4h)

Request a quote

MailWizz hosting — frequently asked questions

Is MailWizz included, or do I need to buy a separate licence?

Our MailWizz hosting plans include a valid Extended MailWizz licence operated by our team. You do not need to buy a licence from CodeCanyon separately. If you already own one we can migrate it and apply a discount on the first 3 months — ask us for details. The license is the cheapest line item in the real TCO; the systems engineering is what costs.

Can I run MailWizz in SaaS mode and sell to my own customers?

Yes. Growth and Scale plans are SaaS-ready out of the box: multi-customer mode enabled, pricing plans, PayPal and Stripe gateways pre-configured, email templates, language files for ES/EN, recurring billing. We help you structure per-customer sending limits so one heavy user does not burn the shared reputation. We have agencies running 30+ end customers on a single Blue Spirit MailWizz deployment.

What is the real sending capacity of each plan?

Starter sustains around 250,000 emails per day with a clean list and an engaged audience — that is roughly 7-8 million per month at conservative pacing. Growth sustains roughly one million per day (30M/month). Scale sustains five million per day (150M/month). These are conservative, post-warm-up figures with bulk marketing content. Transactional loads go higher; questionable lists go lower. Above Scale we go custom — talk to us about a dedicated PowerMTA cluster.

Do I get dedicated IPs, or is this shared?

All MailWizz plans include dedicated IPs — 2 on Starter, 5 on Growth, 10 on Scale. They are yours while your account is active, with proper rDNS and warm-up. We never mix your sending reputation with another client. If you need additional IPs mid-contract (multi-brand sending, transactional/marketing split), we provision them with proper warm-up — €60/month per additional IP including IP setup and warm-up.

Will you handle updates, backups and downtime?

Yes. MailWizz core, cron jobs, database tuning, PHP version management, system security patches, weekly off-site backups, daily MySQL snapshots retained 7 days, uptime monitoring with PagerDuty integration, and 24/7 incident response. If the server goes down, we know before you do — and we usually fix it before the morning email goes out. SLA is 99.9% uptime measured monthly; below that we credit your account.

How do you handle MailWizz core updates without breaking my customisations?

We track every customisation we apply and document it in your client folder. Before any major MailWizz upgrade we test in a staging copy of your installation, validate that your custom hooks, templates and integrations still work, and only push to production when everything passes. Patches and minor versions go in low-traffic windows (typically Sunday 04:00 UTC) without breaking anything visible. Major version upgrades are coordinated with you in advance.

Can I migrate from my existing MailWizz, Sendy, Mautic, Acelle or Mailchimp?

Yes. Migration from any of those is included free on Growth and above (€500 one-off on Starter). The standard scope: lists with subscriber states preserved (active/unsubscribed/bounced), campaigns with historical stats where the source platform supports export, templates, automations, custom fields, suppression history, segments. From Mailchimp specifically we map merge fields and tags to MailWizz custom fields and lists. Migration takes 5-10 business days depending on data size.

Why MailWizz instead of Mautic, Acelle, Sendy or self-hosted Mailcoach?

MailWizz has the largest installed base of any self-hosted email marketing platform, the most mature SaaS mode, the deepest CodeCanyon ecosystem of plugins, and the cleanest separation between front-end UI and back-end MTA. The 2026 honest comparison: Sendy ($69 one-time) is cheaper but locked to Amazon SES with no automation; Mautic is more powerful but Symfony-heavy and needs 2GB+ RAM; Acelle is similar to MailWizz but smaller community; Mailcoach is Laravel-elegant but tied to one stack; Listmonk is the lightest open-source option but has no SaaS mode. MailWizz hits the sweet spot for the operator profile we serve — agencies, publishers, SaaS builders running BYOSP with multiple delivery providers.

When is MailWizz hosting NOT the right product for me?

Three cases where you should buy something else. First, if your monthly volume is under 50,000 emails — at that scale Mailchimp, ActiveCampaign or ConvertKit will be cheaper and zero-ops. Second, if you need pure transactional mail (password resets, order confirmations) — Postmark or Amazon SES is a better fit. Third, if you primarily run B2B cold email — that is our Cold Email Infrastructure product, not MailWizz hosting. We catch all three on the discovery call and tell you which product actually fits.

How fast is provisioning?

Starter: 2-3 business days from payment to live MailWizz with first IPs warmed. Growth: 4-5 business days because we provision and warm 5 IPs in parallel. Scale: 5-7 business days. The IP warm-up is the long pole — we cannot ship cold IPs and expect them to deliver day one. You get visibility into the warm-up progress while we work.

How does MailWizz hosting compare to your PowerMTA hosting?

They are different products in the same stack. PowerMTA hosting gives you the bare MTA layer — you bring your own front-end (a custom app, a different platform). MailWizz hosting bundles MailWizz UI on top of PowerMTA so you have campaign management, list management, automation, all out of the box. Many agencies and SaaS builders use MailWizz hosting; many ESPs and developers building custom platforms use PowerMTA hosting directly. We can also run a hybrid where MailWizz handles your marketing and a separate PowerMTA pool handles transactional. Discuss on the discovery call.

What about the new Google/Yahoo/Microsoft sender requirements?

Every MailWizz instance we provision is configured for the 2024-2025 bulk sender requirements out of the box: SPF aligned, DKIM 2048-bit with rotating selectors, DMARC published with reporting endpoint we monitor, RFC 8058 one-click unsubscribe in headers, complaint rate kept below 0.1% through engagement-aware warm-up. Microsoft May 2025 enforcement (4.7.500-4.7.799 codes, 2K external/24h limit on Exchange Online) is also handled. We update configurations when ISPs change requirements; that is part of the service.

Ready to stop running MailWizz yourself?

Tell us your monthly volume target, current setup (DIY MailWizz, Sendy, Mautic, Mailchimp), and one operational pain you would like solved. We respond with a specific recommendation — plan tier, migration path, realistic timeline.

Get a quote Chat on WhatsApp