Acelle Mail
Self-hosted email marketing application built on Laravel. The modern-architecture alternative to MailWizz.
What Acelle Mail is
Acelle Mail is a self-hosted email marketing application. Operators install it on their own server, configure delivery backends, and run their email marketing operations without depending on a third-party ESP.
The feature scope is roughly equivalent to MailWizz: subscriber list management with custom fields, campaign creation and sending, automation workflows, template editor, click/open tracking, bounce processing, multi-tenant support for ESP resellers serving multiple end-clients.
The technical foundation differs from MailWizz. Acelle uses Laravel (modern PHP framework, current version), while MailWizz uses Yii (older PHP framework). The practical effect: operators with Laravel experience find Acelle's codebase easier to understand and customize.
Architecture
Standard Laravel application stack:
- PHP 8.x running on PHP-FPM or Apache mod_php.
- MySQL or MariaDB for the database. Standard Laravel migrations create the schema.
- Redis recommended for caching and queue processing (though file-based queues work for smaller deployments).
- Cron jobs for sending queue processing, automation triggers, scheduled tasks.
Acelle connects to delivery backends for actual mail transmission. Supported backends:
- PowerMTA via API or SMTP submission
- Postal via SMTP submission
- Amazon SES via SDK
- SendGrid, Mailgun, Sparkpost via their APIs (you can use Acelle as the marketing UI on top of a commercial sending backend)
- Generic SMTP (any compliant SMTP server)
Resource requirements for a typical deployment serving up to a few million monthly messages: 4-8 GB RAM, 4 CPU cores, modest disk space (database grows with subscriber count and campaign history).
How Acelle compares to MailWizz
Same segment, different design philosophies.
MailWizz strengths: larger installed base (thousands of operators), more mature ecosystem (community forums, third-party plugins, documentation), longer track record in production.
Acelle strengths: modern Laravel architecture, cleaner codebase for operators who need to customize, faster Laravel-based update path, generally better admin UI design.
Functional parity: both support the same core feature set. Multi-tenant operation, subscriber management with custom fields, segmentation, automation workflows, template editor, click/open tracking, multiple delivery backends.
Cost parity: €399 for a personal license is the typical price point for both. Extended licenses (for serving multiple customers) cost more.
See the full MailWizz vs Acelle comparison for detail on which fits which operator.
When Acelle makes sense
Operators with Laravel familiarity: if your team already works with Laravel, picking up Acelle's codebase is straightforward. Customizations, extensions, and debugging all benefit from prior Laravel knowledge.
Operators preferring modern PHP patterns: Laravel's patterns (Eloquent ORM, service container, dependency injection, modern testing tools) are cleaner than older PHP framework patterns. Operators who care about code quality often prefer Acelle for this reason alone.
Multi-tenant ESP resellers wanting a modern UI: Acelle's admin and client interfaces feel more current than MailWizz's. For resellers whose end-customers see the platform UI, the impression matters.
Fresh deployments without legacy considerations: if you are choosing fresh today without existing MailWizz infrastructure to maintain, Acelle is a reasonable choice on equal footing with MailWizz.
When Acelle does not make sense
Existing MailWizz deployments at scale: migration cost is real. If you already run MailWizz and have invested in customizations, templates, integrations, the switch to Acelle is unlikely to repay itself in the short term.
Operators wanting the largest community: MailWizz's installed base is larger. Operators who value finding answers via existing community resources may prefer MailWizz for the volume of available material.
Operations without PHP expertise at all: both Acelle and MailWizz require some PHP comfort when something needs debugging. Operations entirely without PHP knowledge benefit equally from Postal (Ruby/Rails — same need for framework expertise but different framework) or commercial SaaS (no expertise needed).