Contents
MailWizz and Mautic are the two most-deployed self-hosted PHP-based email platforms in 2026, but they target different operational profiles. MailWizz is focused email marketing software with a one-time license and BYOSP (bring-your-own-sending-provider) architecture; it does email marketing well without trying to expand into adjacent functions. Mautic is open-source marketing automation that includes email alongside landing pages, lead scoring, multi-channel campaigns, and CRM-like contact management; it aims to replace the entire marketing stack with an open-source alternative to HubSpot. The choice between them depends on whether the team needs focused email marketing or comprehensive marketing automation.
This comparison covers the practical decision between MailWizz and Mautic in 2026: the architectural and positioning difference between focused email marketing and full marketing automation, MailWizz's BYOSP model and multi-delivery-server rotation capabilities, Mautic's broader feature scope including landing pages and lead scoring, technical stack and resource requirements (PHP/MySQL with approximately 1GB RAM for MailWizz versus PHP/Symfony/MySQL with 2GB+ RAM for Mautic), cost models (one-time license versus open-source plus infrastructure), feature coverage across both platforms, use case fit by team profile and email programme needs, and the decision framework for selecting between them.
Different purposes, different shapes
One tool. One job. The other tool. Many jobs. Different operational mathematics.
Both platforms run as self-hosted PHP applications on Linux infrastructure, but the similarity ends at the deployment layer. The applications themselves have fundamentally different design goals that produce different operational shapes.
MailWizz was built with focused intent: do email marketing well. Send bulk campaigns reliably. Handle bounces cleanly. Support multiple sending providers with rotation. Provide a clean admin interface that marketing teams can use without training. Refined since 2013, the platform has matured around this one operational profile. The feature set covers email marketing comprehensively but does not extend into adjacent functions (no landing pages beyond simple subscribe forms, no CRM features, no multi-channel orchestration).
Mautic was built with expansive intent: replace the entire commercial marketing automation stack with an open-source alternative. Email is one channel among several. Landing pages, lead scoring, progressive profiling, multi-step automation workflows, dynamic content, CRM-like contact management, social posting integration, SMS support, segmentation built around behavioural data. The platform aims to provide HubSpot-equivalent capabilities at zero license cost, accepting the operational complexity that comprehensive scope produces.
The shape difference produces different operational consequences. MailWizz operations focus on the email marketing function: SMTP delivery server configuration, list management, campaign deliverability, bounce processing. Mautic operations span a broader surface: email plus landing pages plus automation workflows plus integrations plus contact management. The teams suited to each platform are typically different: MailWizz fits teams whose email programme is the primary marketing activity; Mautic fits teams running comprehensive marketing programmes across multiple channels.
MailWizz positioning and capabilities
MailWizz positions as the email marketing application for self-hosted deployments. The capability set:
Campaign management. Create and schedule one-time campaigns, recurring campaigns, autoresponders triggered by subscriber events. The campaign editor supports HTML email templates with merge tags, A/B testing with multiple variants, send-time scheduling including time-zone-aware delivery.
List management. Unlimited lists per customer account. Custom fields per list. Import from CSV, JSON, text files, external databases. Automatic deduplication. List segmentation based on subscriber attributes and engagement history.
BYOSP (bring-your-own-sending-provider) model. MailWizz does not include its own SMTP delivery; it relies on external SMTP services. Supported providers: Amazon SES, SendGrid, Mailgun, SparkPost, Postmark, Pepipost, Elastic Email, plus any standard SMTP server (self-hosted Postfix, PowerMTA, KumoMTA, etc.). Multiple delivery servers can be configured per customer with rotation logic distributing volume across them.
Bounce processing. Built-in bounce server configuration that processes bounce messages from configured POP3/IMAP mailboxes. Hard bounces trigger automatic suppression; soft bounces are tracked with configurable thresholds before suppression.
Multi-tenant architecture. Create unlimited customer accounts within a single MailWizz installation. Each customer has isolated lists, campaigns, templates, and statistics. The architecture supports agency and SaaS-style deployments where one operator manages email infrastructure for multiple clients.
Reporting and analytics. Per-campaign reports including delivery, opens, clicks, bounces, complaints, unsubscribes. Aggregate reports across campaigns. Geographic and device breakdowns. Export to CSV or PDF.
API access. REST API with documented endpoints for campaigns, lists, subscribers, templates. Official SDKs for PHP, Python, Ruby, Node.js, and small REST apps. Webhooks for event notifications.
White-labelling. The interface can be branded for the operator's identity. Custom domains, custom logos, custom email templates for system notifications. Popular for agencies offering email-as-a-service to clients.
Theme and extension ecosystem. Active community of developers producing themes, extensions, and integrations. Marketplace for purchasing additional functionality (advanced reporting, custom integrations, specialised editors).
What MailWizz does not provide: landing page builder, lead scoring, behavioural automation beyond basic autoresponders, multi-channel orchestration (no SMS or push notifications), CRM-like contact management beyond email lists, complex multi-step workflow visualisation.
Mautic positioning and capabilities
Mautic positions as the open-source alternative to commercial marketing automation platforms (HubSpot, Marketo, Pardot). The capability set:
Email marketing. Campaign creation with drag-and-drop editor, segmented sending, A/B testing, deliverability monitoring. The email capabilities are reasonable but not the platform's primary strength.
Marketing automation workflows. Visual workflow builder for multi-step campaigns with branching logic, conditional waits, goal tracking, segment changes triggered by contact behaviour. Workflows can include email sends, contact attribute updates, segment additions or removals, web hooks to external systems, internal team notifications, and integrations with other Mautic features.
Landing pages. Built-in landing page builder for capturing leads, hosting campaign content, A/B testing page variants. Pages are hosted on the Mautic domain or can use custom domains. SEO-friendly URLs and meta data support.
Lead scoring and grading. Score contacts based on behavioural events (opened email, clicked link, visited specific page, submitted form). Grading separates from scoring and reflects contact attributes (job title, company size, industry). Scoring and grading drive automation workflows and segment membership.
Progressive profiling. Forms that progressively collect more information from leads over time, asking for one or two additional fields per interaction rather than demanding extensive forms upfront.
Multi-channel campaigns. Email plus SMS plus social posting plus internal team alerts coordinated through the workflow builder. Multi-channel marketing without integrating separate platforms.
Contact management. Detailed contact profiles with behavioural history, attribute fields, score and grade tracking, segment membership history. CRM-like features for marketing-focused teams that do not need full CRM.
Integrations. Native integrations with Facebook, HubSpot, Microsoft (Office 365, Dynamics), Zoho, SendGrid, MailChimp, Salesforce, Pipedrive, and many other commercial platforms. REST API for custom integrations.
Acquia enterprise support. Acquia (parent company of Drupal) provides commercial Mautic support and the Acquia Marketing Cloud product line. Self-hosted Mautic is GPL open source; managed Mautic Cloud is commercially available.
Community. 200,000+ user community with active forums, Slack, regular contributors, plugin marketplace. The community is among the largest of any open-source marketing platform.
What Mautic does not provide as well as commercial alternatives: polished UX comparable to HubSpot or Marketo, integrated CRM functionality (Mautic is marketing-focused), enterprise sales features (use Salesforce or similar), advanced analytics and AI-driven optimization that commercial platforms offer.
Technical stack and resource requirements
The technical stacks differ in ways that affect operational profile substantially.
| Aspect | MailWizz | Mautic |
|---|---|---|
| Language | PHP 7.4+ | PHP 8.0+ (recently) |
| Framework | Yii Framework (lightweight) | Symfony (heavier, more comprehensive) |
| Database | MySQL 5.7+ / MariaDB 10.3+ | MySQL 5.7+ / MariaDB 10.3+ |
| Minimum RAM | 1GB (works on shared hosting) | 2GB minimum, 4GB+ recommended |
| Web server | Apache or Nginx | Apache or Nginx |
| Required PHP extensions | gd, imap, zip, mbstring, curl | Similar plus additional Symfony requirements |
| Cron requirements | Required for campaign sending | Required for campaigns, automations, scoring |
| Background workers | Optional (improves throughput) | Strongly recommended |
| Cache layer | Optional (Redis or Memcached) | Strongly recommended (Redis or Memcached) |
| Suitable for shared hosting | Yes (small deployments) | No (requires VPS or dedicated) |
The stack difference reflects the architectural difference. MailWizz uses the lightweight Yii framework optimised for performance with minimal overhead; Mautic uses Symfony which provides comprehensive feature support but with heavier baseline resource consumption.
For deployment scale:
MailWizz operational profile. Runs comfortably on a single VPS with 1-2GB RAM for moderate volumes (up to several hundred thousand monthly emails). High-volume deployments (millions monthly) typically use a dedicated server with 4-8GB RAM plus separate database server. Background workers process campaign sending in parallel; scaling out adds more workers rather than more application servers.
Mautic operational profile. Requires VPS with 2GB+ RAM as starting point; production deployments typically use 4-8GB RAM. Database can become a bottleneck for large contact databases (10M+ contacts) requiring separate database server with appropriate sizing. Symfony's caching and queue management need Redis for production use. Multi-server deployments require Mautic clustering configuration which is operationally more complex than scaling MailWizz.
The resource difference matters for cost-conscious operators. A $20-50 monthly VPS can host moderate-scale MailWizz; equivalent Mautic typically needs $50-150 monthly VPS plus database overhead.
Cost models compared
The cost models are structurally different.
MailWizz: one-time license model.
- Standard License: $299 one-time (for use on one site, one production environment)
- Extended License: $449 one-time (for end-user reselling, white-label SaaS)
- Included support and updates: 6 months from purchase
- License extension: $159 per 12 months for continued support and updates after the initial period
- No per-subscriber fees, no per-email volume fees, no list size limits within the software
- External sending costs: whatever the chosen SMTP provider charges (AWS SES at $0.10 per 1000 emails, SendGrid tiered pricing, etc.)
Mautic: open-source plus operational cost.
- Software license: free under GPL
- Self-hosted infrastructure: $50-200 monthly typical (VPS, database, optional CDN, monitoring)
- Acquia Cloud Mautic: enterprise pricing not publicly disclosed
- No per-subscriber fees in self-hosted deployment
- External sending costs: whatever SMTP provider charges (Mautic also uses external SMTP)
The cost comparison over multi-year operations:
| Year | MailWizz cumulative cost | Mautic cumulative cost |
|---|---|---|
| Year 1 | $299 license + $0 (first 6 months included) + $400-2,400 infrastructure | $0 software + $600-2,400 infrastructure |
| Year 2 | +$159 license extension + $400-2,400 infrastructure | $0 software + $600-2,400 infrastructure |
| Year 3 | +$159 license extension + $400-2,400 infrastructure | $0 software + $600-2,400 infrastructure |
| Year 5 cumulative | $299 + 4× $159 = $935 software + 5× $400-2,400 = $2,000-12,000 infrastructure | $0 software + 5× $600-2,400 = $3,000-12,000 infrastructure |
Over 5 years, total ownership cost is comparable: MailWizz's higher software cost is offset by lighter infrastructure requirements. The decision is not primarily cost-driven; it is capability and operational profile-driven.
Feature coverage side by side
The feature comparison:
| Feature | MailWizz | Mautic |
|---|---|---|
| Email campaigns | ✓ Refined | ✓ Good |
| Drag-and-drop editor | ✓ Available | ✓ Available |
| A/B testing | ✓ Built-in | ✓ Built-in |
| Autoresponders | ✓ Available | ✓ Available (via workflows) |
| List segmentation | ✓ Comprehensive | ✓ Comprehensive |
| Multi-SMTP rotation | ✓ Native and refined | ✓ Available but less polished |
| Bounce processing | ✓ Built-in POP3/IMAP processing | ✓ Built-in |
| Multi-tenant accounts | ✓ Native | ~ Workarounds exist |
| API access | ✓ REST API with multi-language SDKs | ✓ REST API |
| Webhooks | ✓ Available | ✓ Available |
| White-labelling | ✓ Refined | ~ Available with effort |
| Landing pages | ✗ Basic subscribe forms only | ✓ Full builder |
| Lead scoring | ✗ Not available | ✓ Built-in |
| Progressive profiling | ✗ Not available | ✓ Built-in |
| Multi-step workflows | ~ Basic autoresponders | ✓ Visual workflow builder |
| Multi-channel (SMS, social) | ✗ Email only | ✓ Built-in |
| CRM-like contact management | ✗ List-based only | ✓ Contact-centric |
| Integrations marketplace | ✓ MailWizz extension marketplace | ✓ Larger ecosystem (200k+ community) |
The pattern is clear: MailWizz covers email marketing comprehensively but does not extend into broader marketing automation. Mautic covers email reasonably plus the broader marketing automation surface. Teams that need only email marketing find MailWizz's feature coverage complete; teams that need landing pages, lead scoring, and workflows find Mautic's broader coverage essential.
Some teams choose Mautic for its broader feature coverage even though they only use the email marketing function. The result is over-engineered infrastructure: Mautic's resource requirements, operational complexity, and steeper learning curve produce ongoing friction without delivering corresponding value. The team would be better served by MailWizz (or a simpler tool like Listmonk) that matches the actual usage pattern. The right framing: choose the platform whose feature scope matches your actual operations, not the platform whose feature scope sounds comprehensive on paper. Buying capability you do not use is paying complexity cost without benefit.
Use case fit
The use case patterns where each platform fits best:
MailWizz fit patterns:
- Agencies running email marketing for multiple clients. The multi-tenant architecture and white-labelling make MailWizz operationally clean for agency use. Each client gets isolated lists, campaigns, statistics; the agency operates a single MailWizz instance.
- Affiliate marketing programmes. Bulk email to large lists with multi-SMTP rotation is core MailWizz capability. The BYOSP model lets affiliates rotate across multiple SMTP providers based on cost, reputation, or specific campaign needs.
- SaaS-style email infrastructure. Some operators sell MailWizz access as a service to clients, leveraging the multi-tenant architecture for billable usage.
- High-volume bulk email senders. The lightweight architecture handles millions of monthly messages efficiently when paired with proper SMTP infrastructure.
- Teams wanting predictable one-time cost. The license model produces known capital cost without ongoing per-subscriber fees.
Mautic fit patterns:
- Inbound marketing teams. The combination of landing pages, forms, lead scoring, and progressive profiling supports inbound marketing operations comparable to HubSpot.
- Lead generation programmes. Scoring and grading mechanics drive lead qualification workflows that feed into sales handoff processes.
- Multi-channel campaigns. Email plus SMS plus social coordinated through workflows for unified customer experience.
- Organisations replacing commercial marketing automation. Teams migrating away from HubSpot, Marketo, or Pardot for cost or data sovereignty reasons typically choose Mautic.
- Teams with marketing automation expertise. Mautic's workflow builder is powerful for teams that can leverage it; the same capability is unused complexity for teams that do not need it.
Operational complexity
The operational complexity gap is one of the most significant practical differences.
MailWizz operational tasks:
- Install and configure on a single VPS (typically 1-3 hours for new admins)
- Configure SMTP delivery servers and bounce servers (1 hour per server)
- Set up cron job for campaign sending (15 minutes)
- Manage license updates annually if continuing support is desired
- Apply security patches when released (typically monthly cycle)
- Routine database maintenance (weekly backups, occasional optimisation)
Mautic operational tasks (additional to MailWizz baseline):
- Initial setup is more complex (typically 4-8 hours for new admins given Symfony configuration)
- Configure Redis or Memcached for caching (essential for production performance)
- Set up multiple cron jobs for different Mautic functions (campaigns, scoring, segment updates, etc.)
- Configure background workers for asynchronous processing
- Tune Symfony performance for the deployment (cache warmup, configuration optimisation)
- Manage database growth more carefully (large contact databases need indexing and optimisation)
- Monitor more components (Mautic itself, Redis, queue workers, integration health)
- Handle Mautic updates which sometimes have non-trivial migration steps
The operational complexity multiplier is approximately 2-3x for Mautic versus MailWizz. The complexity is justified when Mautic's broader features are operationally valuable; the complexity is unjustified overhead when only email marketing is actually used.
An agency client we worked with in 2024 illustrates the operational complexity trade-off in practice. They had been running Mautic since 2020 for client email programmes, choosing it for its open-source license and feature comprehensiveness. By 2024 the operational reality was: they used roughly 30% of Mautic's features (email marketing, basic segmentation, simple autoresponders), while spending substantial time on operational tasks (database optimization for growing contact databases, Symfony cache management, intermittent integration failures, complex upgrade cycles). We migrated their email programmes to MailWizz over 8 weeks. The migration included data export, MailWizz infrastructure setup, list and template recreation, integration configuration with their existing SMTP providers. Post-migration operational time dropped approximately 60% with no loss of capability for their actual use cases. The lesson: matching platform to actual usage produces better outcomes than choosing comprehensive platforms when only a subset of capability is used. Mautic remains the right choice for teams genuinely using its full surface; MailWizz is the right choice for teams whose actual operations are email-focused.
Decision framework
The decision framework for MailWizz versus Mautic in 2026:
Choose MailWizz when: the email programme is the primary marketing activity; agency or multi-tenant deployment with white-labelling matters; high-volume bulk email sending is the use case; operational simplicity is preferred over feature breadth; the team has limited DevOps capacity; predictable one-time license cost is preferred over ongoing infrastructure overhead; BYOSP model with multiple SMTP provider rotation is operationally valuable.
Choose Mautic when: the marketing programme spans email plus landing pages plus lead scoring plus multi-channel campaigns; the team is replacing commercial marketing automation (HubSpot, Marketo, Pardot) for cost or data sovereignty reasons; open-source licensing matters as a strategic preference; the team has DevOps capacity to manage the more complex infrastructure; the broader feature surface justifies the operational complexity.
Consider alternatives when: the email programme is small (under 50K monthly) and the operational burden of self-hosting either platform is not justified (consider managed alternatives like Klaviyo, Mailchimp, or Sequenzy); the team prefers modern infrastructure (consider Listmonk for a Go-based lightweight alternative to MailWizz; consider Mailcoach for Laravel-based deployments); transactional email is the primary use case rather than marketing (consider Postmark, SendGrid, Postal, or Cuttlefish for transactional-focused tools).
The 2026 default decision: for focused email marketing, MailWizz. For comprehensive marketing automation, Mautic. For deployments that do not need self-hosting, managed alternatives. The platforms are not direct competitors; they serve genuinely different operational profiles. Teams that approach the choice from the "which is better" framing tend to choose poorly; teams that approach it from the "which fits my operational profile" framing typically choose well.