Acelle Mail Hosting

Acelle Mail occupies a distinct place among self-hosted email platforms: it is the one built from the ground up not just to send your own email, but to let you run an email-marketing business. Where other platforms are applications you use, Acelle is closer to a product you can own and resell — a polished Laravel application with a complete multi-tenant SaaS layer underneath it. That makes it the natural choice for agencies and founders who want to become their own ESP rather than just escape a SaaS bill. This page explains what Acelle is, what makes it different, the architecture that keeps it performing, and the honest truth it shares with every platform: that the software is not what lands your mail.

What is Acelle Mail, and what is Acelle hosting?

Acelle Mail is a self-hosted email marketing platform written in PHP and Laravel, in active development since 2016 and often described as the Mailchimp you host and own. It gives you the full marketing toolkit — a drag-and-drop campaign builder, a visual branching automation designer, A/B testing, segmentation, autoresponders, RSS-to-email, real-time campaign statistics and a REST API — installed on your own server through a quick web installer that generates the authentication records you publish. Acelle hosting means running that Laravel application on infrastructure configured for it: the server, the database, the queue workers it depends on, and the delivery layer it sends through. Because Acelle is a one-time commercial license with the full source included, hosting it gives you a platform and data you own outright, with the freedom to customise and rebrand that a SaaS cannot offer.

What makes Acelle different: the built-in SaaS layer

The feature that sets Acelle apart from the rest of the self-hosted field is its multi-tenant SaaS layer, which has been part of the platform since version 4. On top of the marketing application, Acelle includes a complete SaaS framework — customer accounts, subscription plans, billing with multiple payment gateways, prorated upgrades, dunning for failed payments, and white-label branding — so a single Acelle install can serve many paying customers, each with their own lists, campaigns and plan limits. In other words, Acelle is not just software for sending your own mail; it is a kit for becoming an email-service provider, selling sending to your own customers under your own brand. MailWizz offers a multi-tenant mode too, but Acelle is shaped around the SaaS model more completely, with the billing and customer-management machinery built in rather than bolted on. For an agency or founder whose goal is a product, that shape is the whole appeal.

How does Acelle compare to MailWizz and Mautic?

The three major self-hosted platforms sort by what you are trying to build. Acelle is the SaaS-shaped one — its built-in billing and multi-tenant framework make it the choice when the goal is to run an email-service product. MailWizz is the focused email-marketing application, lighter and strong for agencies doing white-label client work without needing a full billing system. Mautic is the marketing automation platform, built around lead scoring and multi-step workflows for B2B nurture rather than mass sending. They overlap, but their centres of gravity differ, and the right one follows from your purpose.

Source-available, not open-source: what that means

Acelle is frequently listed as open-source, and it is worth correcting because the distinction has practical consequences. Acelle is source-available commercial software: the complete, unencrypted Laravel source ships with every license, so you can read it, modify it, extend it through its plugin system, and white-label it as your own — but the license is a paid one-time fee, not a free open-source license. The meaningful difference is copyleft. Genuinely open-source platforms like Mautic carry licenses that can require you to share modifications if you offer the software as a service, which complicates reselling. Acelle’s commercial source-available license carries no such obligation, so you can build a white-label product on it without exposing your changes. For the reseller and SaaS use case Acelle is designed for, that no-copyleft freedom is part of why it fits — you own what you build on top of it.

Acelle’s built-in deliverability features

Acelle includes deliverability tooling that is genuinely uncommon in self-hosted platforms, and it is worth knowing what helps. It has automated IP warmup, which ramps a new sending IP’s volume on a schedule — a feature most self-hosted tools leave entirely to you. It supports a custom tracking domain, so your link tracking runs under your own domain and isolates your sending reputation rather than sharing a generic one. It runs campaigns through SpamAssassin before sending, flagging content likely to trip filters, and it includes email verification and automatic bounce and feedback-loop handling to keep lists clean. These are real advantages that reduce the manual deliverability work Acelle requires. The honest framing, though, is that they assist deliverability rather than deliver it — they make good practice easier, but the sending layer underneath still determines whether mail lands.

Does Acelle handle deliverability by itself?

No, and Acelle’s own documentation says so plainly: deliverability depends on the sending service you connect, not on Acelle. The platform supports many sending drivers — standard SMTP, Amazon SES, SendGrid, Mailgun, SparkPost and others — and it is the quality and reputation of that delivery layer, combined with your list and sending discipline, that decides inbox placement. Acelle’s built-in warmup and tracking-domain features genuinely help, but they sit on top of a delivery layer that does the actual work, and a great Acelle install sending through a weak or unwarmed sending path lands in spam just like any other platform would. This is the truth that runs through every self-hosted email platform: the application is the front end, and the delivery layer is what lands the mail. Hosting Acelle well means running that delivery layer well, not just installing the application.

Acelle and PowerMTA: keep them on separate servers

The most important architectural decision in an Acelle deployment is keeping the application and the delivery engine apart. Acelle is a resource-intensive Laravel application, and a serious delivery layer like PowerMTA or KumoMTA does heavy sending work; run both on one server and the MTA’s sending starves Acelle’s interface of CPU and memory during a campaign, so the dashboard crawls exactly when you are trying to use it. The correct architecture runs Acelle on its own tuned server and the MTA on its own with the sending IPs, connected over authenticated SMTP — Acelle decides what to send and to whom, PowerMTA delivers it with all its IP rotation and throttling. This separation is not an optimisation; it is the difference between a smooth platform and a sluggish one, and it is how a deployment that actually performs is built. Collapsing the two is one of the most common reasons a self-hosted Acelle feels slow.

What does Acelle hosting require?

A production Acelle install needs more than the base requirements suggest. The foundation is a Linux server with PHP 8.x and MySQL or MariaDB, set up through Acelle’s web installer. But the parts that determine whether it runs reliably are the queue workers — Acelle processes campaign sending and automation through background workers, with Supervisor and distributed-worker support in recent versions, and if those workers are misconfigured or stop, sending stalls quietly with no error. Caching and database tuning matter as your contact counts climb, the license tier must match your use (the extended license for the multi-tenant SaaS features), and the whole thing needs a delivery layer to send through. Recent Acelle versions add distributed deployment, smart caching and even a plugin layer for AI assistants with adapters for self-hosted and commercial models — capability that rewards a properly engineered host. None of this is beyond a skilled operator, but it is real work, which is what managed hosting handles.

Running Acelle as your own ESP

Acelle’s SaaS layer makes becoming an email-service provider technically straightforward, and it is worth being clear-eyed about what that entails beyond the software. Once you are selling sending to customers, you have an ESP’s responsibilities: you are accountable for your tenants’ sending practices, because their bad behaviour damages the shared reputation everyone on your platform depends on; you need abuse handling and acceptable-use enforcement; and you carry compliance obligations under laws like CASL and CAN-SPAM that now extend across your customers’ sending, not just your own. The billing screen is the easy part; running a clean, well-policed sending platform is the real work, and it is what separates a durable ESP from one that gets its IP ranges blocklisted by a few careless customers. We host the infrastructure for exactly this model and bring the deliverability discipline that keeps a multi-tenant platform healthy — which for an ESP is the difference between a business and a liability.

How we host and run Acelle for you

With MCSNET, Acelle hosting is the full stack deployed the way it should be. We install Acelle on its own tuned server — PHP and the Laravel stack configured, the database optimised, queue workers and Supervisor set up so background sending actually runs, caching in place — with the license tier matched to whether you are sending your own mail or running a multi-tenant ESP. Separately, on its own server, we run the delivery layer on PowerMTA or KumoMTA with our own IPs, handling reverse DNS, authentication, warming, and reputation and blocklist monitoring, so Acelle sends through infrastructure built to land in the inbox. The two layers stay separate so neither starves the other, and the whole thing runs as one managed system. Your platform and data stay yours, resident in Canada under PIPEDA with a CASL-aware, permission-based approach.

For multi-tenant deployments we also configure the operational guardrails an ESP needs from day one: per-tenant sending limits, suppression handling that works across customers, and monitoring that attributes a reputation problem to the tenant causing it rather than letting one careless customer drag the whole platform down. Those controls are what make Acelle’s SaaS layer safe to actually sell on, and they are the part a bare install leaves entirely to you.

# mcsnet · acelle stack · brand.example
app server    acelle · php 8 · laravel 12  tuned
workers       supervisor · distributed queue  firing
tenants       multi-tenant · per-plan limits active
delivery      powermta · SEPARATE server · own ips
warmup        per-ip warm · custom tracking domain
auth          spf/dkim/dmarc · rdns on all ips  ok
data          resident in canada · pipeda
status        app + delivery separated · running clean

Why work with us?

Because we know how Acelle is actually meant to run, and we own the layer that decides whether it works. Plenty of hosts will drop Acelle on a single VPS next to an MTA and watch it crawl; we deploy it the correct way, on separate tuned servers, and pair it with a real delivery layer on IPs we own and warm. For the ESP use case in particular, we bring the deliverability and abuse-management discipline that keeps a multi-tenant platform off blocklists, which is the hard part of running an email business. Your data stays resident in Canada under PIPEDA with a permission-based, CASL-aware approach — which matters doubly when you are responsible for tenants’ sending too. We host the version of Acelle that performs and lasts, not the one that struggles on a cheap box.

Who this is for, and who it is not

It is for agencies, founders and businesses that want to own a complete email platform — and especially those who want to run their own white-label email service on Acelle’s multi-tenant SaaS layer, billing their own customers under their own brand. It is for operators who value source-available ownership and the freedom to customise and resell without copyleft constraints. It is not for a small sender with a single modest list, who would find Acelle’s SaaS machinery to be overhead they will never use — a simpler tool serves them better, and we will say so. And it is not a vehicle for spam: running an ESP means policing your tenants, and we host the legitimate, permission-based version only. Acelle hosting sits within the email marketing software cluster alongside MailWizz and Mautic, and depends on the delivery layer every one of them sends through. Deployed on separate tuned servers, paired with real sending infrastructure, and run for legitimate sending, Acelle becomes the owned platform — or the owned ESP — it is designed to be.