MailWizz vs Sendy: Enterprise Self-Hosted Platform vs SES Wrapper (2027)
In the world of self-hosted email marketing, MailWizz and Sendy represent two fundamentally divergent scales of operation. Sendy is an ultra-minimalist, single-tier newsletter dashboard designed exclusively to transmit mass marketing blasts via Amazon SES API at bottom-dollar pricing ($69 one-time). MailWizz is an industrial-strength email marketing suite engineered with a multi-tenant agency framework, multi-threaded campaign queues, automated bounce and feedback loop handlers, and native support for arbitrary SMTP relays, dedicated bare-metal PowerMTA/Postfix clusters, and multi-cloud API delivery engines.
- 1. Architectural Roots & Design Philosophies
- 2. Delivery Routing: Multi-MTA vs Amazon SES Tethering
- 3. Dispatch Mechanics & Queue Multi-Threading
- 4. Agency Multi-Tenancy & Client Monetization
- 5. Full Technical Specification Matrix
- 6. Operational Risk: What Happens When AWS Bans You?
- 7. High-Volume Agency Migration Case Study
- 8. Strategic Decision Framework
1. Architectural Roots & Design Philosophies
Both MailWizz and Sendy run on standard PHP and MySQL server environments, but their internal codebases reflect radically different objectives:
Sendy was created in 2012 by Hex to solve a single problem: allowing bloggers, indie creators, and small businesses to send bulk newsletters through Amazon Simple Email Service (SES) at $0.10 per thousand emails, avoiding Mailchimp’s costly subscription tiers. Sendy is lightweight, relies on procedural PHP patterns, and features a clean, simple dashboard. However, it lacks an object-oriented extensibility layer, enterprise modularity, or dynamic delivery routing.
MailWizz EMA was architected as an enterprise-grade platform on the Yii framework. It is designed to handle dozens of concurrent operators, millions of subscribers, complex behavioral automations, and diverse sending endpoints. MailWizz separates the administration portal, agency customer accounts, frontend subscriber portals, and backend CLI daemon workers into dedicated modules.
2. Delivery Routing: Multi-MTA vs Amazon SES Tethering
The single most significant technical dividing line between these two platforms is how they transmit email to recipient mail transfer agents:
| Capability | MailWizz EMA | Sendy |
|---|---|---|
| Amazon SES Native API | Supported via AWS SDK with SNS automated bounce webhooks | Supported natively (Primary intended transmission pipe) |
| Dedicated Bare-Metal PowerMTA / Postfix | Fully supported via native SMTP connections with connection pooling | Unsupported (Sendy only offers basic generic SMTP as fallback) |
| Cloud ESP API Webhooks (Mailgun, SendGrid, SparkPost) | Native modular API integrations with automated event sync | Requires external code modifications or third-party patches |
| Dynamic Server Rotation & Weighted Load Balancing | Yes (e.g., send 60% on PowerMTA IP pool, 40% on SES, with automatic failover) | No (Strict 1:1 binding per brand or sequential send) |
3. Dispatch Mechanics & Queue Multi-Threading
When launching a campaign to 500,000 recipients, campaign queue execution speed determines deliverability freshness. Stale campaigns that trickle out over 12 hours miss critical time-zone engagement windows.
Sendy relies on a sequential cron script (`scheduled.php`) that runs every minute, pulling batches and transmitting them serially over HTTP API calls to SES. While reliable for small batches (20,000 to 50,000 records), large volumes encounter PHP execution bottlenecks and memory constraints unless heavily customized.
In contrast, MailWizz utilizes a multi-process PCNTL architecture capable of spawning dozens of concurrent Linux worker threads across multiple CPU cores:
# MailWizz Parallel Dispatch Configuration Campaign Sending Settings: - Parallel Processes (PCNTL): 16 Workers - Campaigns in Parallel: 5 Simultaneous Campaigns - Batch Size per Worker: 500 Subscribers - Memory Limit per Process: 512M - Micro-sleep Throttling: 0ms (Full Hardware Throttle) Total Theoretical Throughput: Up to 350,000 emails/hour per bare-metal node
4. Agency Multi-Tenancy & Client Monetization
Sendy provides a basic “Brands” feature that allows agency owners to isolate lists and campaigns for individual clients. However, it lacks a complete billing and monetization infrastructure. Agency operators must manually invoice clients outside the application or build custom scripts.
MailWizz includes a complete, out-of-the-box SaaS monetization system:
- Tiered Pricing Plans: Create recurring subscription or prepaid credit packages (e.g., $99/mo for 250,000 sending credits).
- Payment Gateways: Native integrations with Stripe, PayPal, Authorize.Net, Mollie, and 2Checkout.
- Dedicated Resource Allocation: Restrict client accounts to specific delivery servers, custom sending domains, or maximum hourly quotas.
- Self-Service Client Portal: End-users log in to a fully white-labeled interface featuring your agency domain and branding.
5. Full Technical Specification Matrix
| Feature | MailWizz EMA (v2.x) | Sendy (v6.x) |
|---|---|---|
| Framework & Base Language | Yii Framework (PHP 8.1 – 8.4, OOP, MVC architecture) | Procedural PHP (Legacy procedural codebase) |
| Database Engine | MySQL 8.0+ / MariaDB 10.6+ with InnoDB indexing | MySQL / MariaDB |
| Automated Customer Journeys | Advanced autoresponders, recurring events, dynamic triggers | Basic drip autoresponders based on subscription date |
| Bounce & FBL Processing | Automated in-band POP3/IMAP bounce mailboxes + Webhooks | Amazon SNS notifications webhook endpoint only |
| List Segmentation | Multi-condition conditional segmentation & custom fields | Basic list filtering and custom field tags |
| Template Designer | Drag-and-drop visual builder, code editor, MJML support | WYSIWYG editor (CKEditor) and raw HTML upload |
| API & Webhooks | Complete RESTful JSON API with comprehensive webhook hooks | Simple HTTP POST parameter API (limited endpoints) |
6. Operational Risk: What Happens When AWS Bans You?
- Zero Single Point of Failure: If an upstream cloud relay pauses your account, switch sending traffic to a backup SMTP cluster in 60 seconds.
- Data Protection: Full database ownership ensures subscriber histories, unsubscriptions, and metrics remain intact on your servers.
- Infrastructure Agility: Migrate seamlessly between bare metal, private clouds, or commercial MTA engines without interrupting subscriber journeys.
- AWS Account Suspension: Amazon SES maintains a strict 5.0% bounce rate and 0.1% complaint limit. An account freeze instantly halts all Sendy operations.
- Fallback Complexity: Using non-SES SMTP relays within Sendy degrades performance and requires extensive manual reconfiguration.
- Development Cadence: Slower core release cycles mean modern authentication standards (BIMI, strict DMARC reporting) require manual intervention.
7. High-Volume Agency Migration Case Study
Performance Marketing Agency Upgrades from Sendy to MailWizz + PowerMTA
A lead-generation and marketing agency managing email delivery for 18 corporate clients ran into severe operational walls with Sendy. When one client uploaded an outdated B2B list that produced a 4.2% bounce rate, Amazon SES placed their entire AWS sending account on probation, threatening all other 17 client operations.
The agency migrated to MailWizz paired with dedicated AutoSMTP PowerMTA infrastructure:
- Client Isolation: Each client was assigned their own tenant sub-account, private sending domain, and dedicated IP address pool.
- Fault Containment: Elevated bounce rates from one client no longer affect other clients or trigger upstream account bans.
- Agency Billing: The agency integrated Stripe directly into MailWizz, automatically charging clients for usage and generating $8,500/month in recurring infrastructure margin.
8. Strategic Decision Framework
You are an independent author, indie hacker, or small creator sending simple, occasional newsletters to under 50,000 subscribers, you already have an established Amazon Web Services account in good standing, and you have zero need for complex automations, client billing, or multi-server load balancing.
You operate a commercial business, agency, or high-volume publishing brand sending more than 100,000 emails per month. If you need multi-tenant sub-accounts, multi-server load balancing, support for dedicated bare-metal MTA engines (like PowerMTA), and complete resilience against third-party platform bans, MailWizz is the undisputed industry standard.
Deploy MailWizz on Fully Managed Dedicated Bare Metal
Skip the complexity of server administration, database tuning, and bounce daemon monitoring. AutoSMTP provides turn-key, pre-installed MailWizz environments powered by dedicated bare-metal PowerMTA or KumoMTA clusters.
Pre-configured MailWizz frontend and enterprise MTA engines on dedicated NVMe bare metal with zero shared resource bottlenecks.
Intelligent warmup algorithms monitoring Google Postmaster spam ratios (<0.1%) and real-time deferrals across clean IPv4 subnets.
RFC 5321 in-band 550 bounce suppression and automated Yahoo/Outlook Complaint Feedback Loop processing directly into MailWizz.
Pre-configured rDNS/PTR, SPF, 2048-bit DKIM, strict DMARC, and BIMI SVG certificates managed 24/7 by deliverability engineers.
Stop paying subscriber penalties. Scale your email sending with dedicated bare-metal MTA power today.