Acelle Mail · Managed hosting

Managed Acelle Mail hosting. SaaS-first, Laravel-clean, PowerMTA-backed.

Acelle Mail is the modern, multi-tenant email marketing platform your engineering team can actually extend. We operate it on dedicated PowerMTA with the same deliverability stack as every Blue Spirit plan.

Acelle licence included
Multi-tenant out of the box
Laravel 10
Amazon SES compatible
Dedicated IPs

Talk to sales Compare with MailWizz Chat on WhatsApp

Why pick Acelle

A cleaner Laravel codebase for teams who want to extend, not patch.

Acelle Mail was built as a SaaS-first Laravel application from day one. Customer accounts, billing plans, resource quotas, API tokens and webhook delivery are baked into the core — not sold as add-ons. For engineering teams that want to ship a branded email marketing product without rewriting the boring parts, Acelle is usually the right answer.

We pair it with the same PowerMTA 6.0 back-end we use for every other email product. The result is a UI your customers love, a codebase your developers enjoy extending, and an MTA that actually delivers mail.

SaaS mode on day one

Plans, subscriptions, resource limits, coupons, Stripe/PayPal checkout — configured and live.

PowerMTA back-end

Acelle points at a dedicated PowerMTA 6.0 VMTA pool, not a shared relay. Full reputation isolation.

Laravel-friendly ops

Composer, artisan, supervisor, queue workers, horizon-style monitoring — configured correctly. Extension development stays clean.

Authentication handled

Sender-domain DKIM, SPF, DMARC and MTA-STS — with helper commands inside Acelle to verify status per customer.

Analytics you can trust

Bounce parsing from PowerMTA accounting files, webhook ingestion, open/click analytics with proper bot filtering.

Backups and patches

Core Acelle updates tested in staging, security patches applied, weekly off-site backups and MySQL point-in-time snapshots.

When Acelle beats MailWizz and when it does not

Both platforms deliver email. The choice is rarely about features at the surface and usually about how you plan to use them. Acelle wins when you are a SaaS builder or agency who needs native multi-tenant billing, resource quotas and a clean Laravel codebase to extend. It wins for teams with a strong PHP/Laravel background because the codebase is idiomatic and plays well with modern tooling. It also has first-class Amazon SES integration that some users prefer as a hedge alongside PowerMTA.

MailWizz wins when you need the broadest ecosystem of extensions and integrations, when you want more granular template and campaign features out of the box, or when you are coming from a YII background and want the familiarity. Both are excellent. Both run beautifully on our PowerMTA stack. We will tell you which is right for you based on your answers during onboarding — not based on which product margin is higher.

What happens during onboarding

Day 1: server provisioned, Acelle installed, Nginx configured with HTTPS, MySQL and Redis tuned, supervisor running the Laravel queues, admin account created. Day 2-3: your domains connected with SPF, DKIM, DMARC and tracking CNAMEs. Day 3-5: delivery server pointed at PowerMTA VMTAs, test campaigns sent, postmaster tools enrolled, feedback loops connected. Day 5+: your IP warm-up plan starts in the background while you onboard content and customers.

What it actually costs

Acelle plans follow the same pricing structure as MailWizz because the underlying infrastructure is the same. Starter from € 89, Growth from € 169, Scale from € 279. Ask for a quote that reflects your expected customer count and volume — we tailor the PowerMTA IP allocation and warm-up plan accordingly.

2026 reality

Three forces reshaped the Acelle Mail landscape between 2024 and 2026.

If your last evaluation of Acelle Mail was 2023, three concrete shifts changed the picture meaningfully. The platform matured operationally, the surrounding ecosystem of supported sending providers expanded, and Acelle's positioning in the open-source email-marketing landscape clarified.

First, Acelle Mail moved to Laravel 12 with PHP 8.2+ requirements as of version 4.1.5 (released March 15, 2026 as LTS). The codebase upgrade matters operationally because Laravel 12 is the current major release with first-class queue routing, structured PHP 8 attribute syntax, and modern dependency injection patterns that make extension development substantially cleaner than Laravel 5-era patches. PHP 8.2+ requirement also drops compatibility with older shared hosting environments — Acelle now realistically requires VPS or dedicated server hosting, which is consistent with how serious senders run it anyway. Operators on Acelle 4.0 or earlier should plan a migration to 4.1.5 LTS within Q2-Q3 2026 because security patches will track 4.1.x going forward.

Second, the SendGrid free tier discontinuation (May 2025) and broader ESP suspension wave drove meaningful adoption of self-hosted Acelle as a SendGrid alternative. SaaS builders who had been hedging on Resend, Postmark, or Mailjet OEM increasingly evaluated Acelle because the SaaS-from-day-one architecture maps cleanly to "I want to give my end-customers branded email-sending capability without rebuilding the marketing-email layer". The CodeCanyon sales figures reflect this — Acelle has sold 50,000+ copies as of 2026, with the Extended SaaS license ($199 one-time) seeing disproportionate growth in 2024-2025. The structural appeal: one-time $199 vs $1,000+/month SendGrid Pro tier billing for equivalent functionality at SaaS scale.

Third, the supported sending-provider matrix expanded substantially. Acelle 4.1.5 ships with first-class integration for Amazon SES, SendGrid, Mailgun, SparkPost, Postmark, MailerSend, Brevo, SMTP2GO, and any standard SMTP — plus the Acelle 4.1.5-p22 release added official Supervisor support, distributed deployment, and remote Redis queues for horizontal scaling. Operationally this means Acelle handles the modern multi-provider deployment patterns (where you might route transactional through Postmark, marketing through self-hosted PowerMTA, and bulk through Amazon SES based on cost-per-email and deliverability profile per traffic type) as a first-class capability rather than as a hand-coded extension. Operators in 2026 evaluating Acelle should think of it less as "open-source MailChimp clone" and more as "open-source ESP orchestration layer with Laravel extensibility".

The takeaway: in 2026 Acelle is in its strongest position since launch — modern Laravel base, mature multi-provider ESP integration, growing SaaS-builder adoption, and pricing economics that beat SaaS alternatives at scale. The remaining decision points are architectural fit (Laravel team or not, multi-tenant SaaS model or not, full PowerMTA control or shared SES) rather than platform readiness.

Decision framework

Five-question decision tree — should you pick Acelle Mail?

The tree below walks the same logic we use during discovery calls. Five binary questions, four terminal recommendations including a "stay on SaaS" branch when self-hosted Acelle would be premature for your scale, and an honest "MailWizz instead" branch when Acelle is not the right fit despite operator interest.

Two sub-points worth noting. First: the "no PHP capability" branch points to managed hosting, not to self-deployment. Acelle's installer is straightforward but operating it in production at any meaningful scale requires comfort with Laravel artisan commands, Composer dependency management, supervisor process management, and PHP-FPM configuration. Operators without that comfort consistently end up either in production incidents they cannot diagnose or paying for managed hosting eventually anyway. Skip the painful middle step. Second: the "MailWizz instead" branch is honest output, not a sales redirect. We sell both platforms equally; the right answer depends on your team's familiarity with Laravel-vs-Yii, your appetite for Acelle's leaner extensions ecosystem vs MailWizz's richer one, and your specific multi-tenant SaaS requirements. We have no commercial preference between them.

Architecture stack — what runs underneath your Acelle deployment.

The diagram below shows the full production stack we deploy for managed Acelle Mail customers. The stack reflects what experienced PHP/Laravel operators expect: idiomatic PHP-FPM behind Nginx, MySQL 8.0 for persistence, Redis 7 for queues and cache, Supervisor for queue worker process management, and PowerMTA 6.0 as the actual SMTP send-side. Everything is configured, monitored, and patched by us; nothing is hand-rolled.

Three observations from the architecture stack. First: the queue tier is where production Acelle deployments succeed or fail. Acelle's campaign-send model fans out to Laravel queue jobs that the Supervisor-managed workers consume; if queue workers crash silently, campaign sends quietly stall while everything else looks healthy. Our Supervisor configuration includes auto-restart, health checks, and queue depth alerting precisely because this is the single most common failure mode in self-deployed Acelle. Second: PowerMTA's VirtualMTA model maps cleanly to Acelle's multi-tenant SaaS architecture — each tenant gets a dedicated VMTA with its own IP, throttle rules, and accounting log. Bounce parsing flows back from PowerMTA logs into Acelle's per-tenant bounce dashboards via our parser daemon. Third: the observability tier is operationally essential, not optional. Production Acelle generates queue depth, bounce rate, complaint rate, throttle events, and campaign progress metrics that need real-time monitoring; flying blind on these metrics means you discover deliverability problems days late through customer complaints rather than minutes late through alerts.

Deep capability matrix — Acelle vs MailWizz vs Mautic vs Mailchimp.

Most platform comparisons are either marketing-grade ("Acelle is great!") or surface-level feature-checklists. Below is the 16-feature matrix Blue Spirit operators use during platform selection conversations, comparing Acelle Mail against the three most common alternatives: MailWizz (similar self-hosted), Mautic (open-source automation-focused), and Mailchimp (SaaS comparison baseline).

Capability	Acelle	MailWizz	Mautic	Mailchimp
Codebase / framework	✓ Laravel 12 (modern)	⚠ Yii 1.x (older)	✓ Symfony 6 (modern)	✗ proprietary
License / pricing	✓ $64-$199 one-time	✓ $69-$249 one-time	✓ free OSS	✗ $13-$350+/month
Multi-tenant SaaS native	✓ from day one	⚠ via extension	✗ single-tenant	✗ N/A (SaaS)
Plans + subscriptions billing	✓ Stripe/PayPal/Paddle	⚠ via extension	✗ none	✓ Mailchimp billing
Email template builder	✓ visual editor + 100+ templates	✓ visual + EmailEditor extension	✓ Mosaico builder	✓ first-class
Marketing automation workflows	✓ visual workflows	⚠ basic autoresponders	✓ best-in-class	✓ Customer Journeys
Multi-provider sending	✓ SES/SG/MG/SP/PM/MS/Brevo	✓ via delivery server config	⚠ via Symfony Mailer	✗ Mailchimp-only
Direct PowerMTA integration	✓ first-class via SMTP	✓ first-class via SMTP	⚠ requires custom config	✗ N/A
REST API for integration	✓ comprehensive	✓ comprehensive	✓ comprehensive	✓ Marketing API
Built-in IP warmup	✓ structured warmup plans	⚠ via extension	✗ relies on MTA	✓ automatic
Bounce + complaint handling	✓ automatic	✓ automatic	⚠ via plugin	✓ automatic
Extensions / plugin ecosystem	⚠ smaller (~30)	✓ richest (200+)	⚠ medium (~100)	✓ massive marketplace
PHP 8.2+ / modern runtime	✓ required	⚠ PHP 7.4+ supported	✓ PHP 8.1+	✗ N/A
Distributed deployment	✓ official 4.1.5+	⚠ manual config	✓ horizontal scaling	✓ Mailchimp manages
Data ownership	✓ self-hosted	✓ self-hosted	✓ self-hosted	✗ Mailchimp owns
Time to first campaign	✓ 30 min (managed)	✓ 30 min (managed)	⚠ 2-4 hours setup	✓ 5 min (SaaS)

The matrix exposes the structural division between platforms: Acelle wins on multi-tenant SaaS architecture, Laravel 12 modernity, and built-in IP warmup with structured plans. MailWizz wins on extensions ecosystem depth and broader PHP-version compatibility. Mautic wins on automation workflow sophistication and pure open-source license. Mailchimp wins on time-to-first-campaign and zero operational overhead but loses on cost at scale and data ownership. The right choice depends on your specific weight on these dimensions; this programme exists for the operators who weighted "multi-tenant SaaS native + Laravel modernity + dedicated PowerMTA infrastructure" highest, which is a real and growing segment.

Real cost — Acelle managed hosting vs four alternative paths.

The table below normalizes total monthly cost across managed Acelle hosting and the four most common alternatives at three production-realistic volumes. All numbers are 2026 published pricing or Blue Spirit production deployment costs. Acelle license cost is amortized to monthly equivalent ($199 SaaS license over 24 months = ~$8.30/mo).

Volume / scenario	Managed Acelle	Self-deploy Acelle	Mailchimp	Mailjet OEM	SendGrid Pro
100K/mo (small SaaS)	€89 (Starter)	~$50 VPS + $8 license + ops time	$135 (Standard 25K subs)	$105 (Essentials)	$89.95 (Pro)
1M/mo (mid-market)	€169 (Growth)	~$200 VPS + $8 license + ops time	$385 (Standard 50K subs)	$315 (Essentials)	$249.95+ (Pro)
5M/mo (multi-tenant SaaS)	€279 (Scale)	~$600 multi-VPS + $8 + ops	$800+ (250K subs)	$1,250+ (Premium)	$800+ (Premier)

Three observations from the cost matrix. First: managed Acelle on PowerMTA is cost-competitive at every tier while providing full data ownership, dedicated IPs, and multi-tenant SaaS architecture that the SaaS alternatives charge significantly more for. Second: self-deploying Acelle looks cheaper on raw VPS cost ($50-200/mo) but the hidden cost is engineering time. A typical self-deployed Acelle setup requires 8-15 hours/month of senior engineering time for patching, monitoring, queue management, and incident response — at $150/hour that is $1,200-2,250/month of unbilled engineering cost that disappears into "this is just operations". Managed hosting moves that hidden cost into a transparent line item. Third: the SaaS alternatives (Mailchimp, Mailjet, SendGrid) scale poorly at 1M+/month because their pricing model is fundamentally per-subscriber-or-per-email, while managed Acelle scales linearly with infrastructure that you control. The breakeven crossover happens around 100-300K emails/month for most operators.

Five operator profiles where managed Acelle is the right fit

Below five concrete operator profiles where we have repeatedly seen managed Acelle outperform alternatives. If your situation matches one of these, the conversation usually moves quickly during the discovery call:

1. SaaS builder embedding email marketing into a vertical product

A real estate platform, healthcare scheduling tool, or e-commerce platform whose end-customers need to send branded marketing email under the SaaS's domain. Acelle's multi-tenant architecture maps directly to this need — each end-customer gets their own Acelle tenant with their own branded UI, plans, and dedicated IP allocation. The SaaS owns the relationship with the end-customer, monetizes on per-tenant pricing, and keeps the email infrastructure fully managed by us. Time-to-launch typically 5-7 days for the embedded integration plus another 2-3 weeks for end-customer onboarding flows.

2. Agency reselling email-marketing services to 20+ small business clients

A digital agency serving 20-50 small business clients (chiropractors, restaurants, local service companies) who each need basic email marketing but cannot justify their own Mailchimp account. Acelle's per-tenant model lets the agency provision sub-accounts at marginal cost while charging $50-150/month/client retail. Margin economics: Acelle Growth tier €169/month wholesale ÷ 30 active client tenants = €5.63/client wholesale vs $97/client retail = 94% gross margin per active client. The agency operates the platform; we operate the infrastructure underneath.

3. Mid-market e-commerce business graduating off Mailchimp

An e-commerce business with 100K-500K subscribers paying $400-800/month for Mailchimp Standard tier and watching it grow as their list grows. Migrating to managed Acelle on Growth tier (€169/month) immediately saves 60-70% while delivering equivalent functionality — visual template builder, automation workflows, REST API integration with the e-commerce platform (Shopify, WooCommerce, Magento), bounce handling. The catch: migration takes 2-4 weeks and requires reputation transfer planning. We handle both as part of standard onboarding.

4. Compliance-sensitive sender (fintech, healthcare, EU GDPR-heavy) needing data ownership

A fintech, healthcare provider, or EU operator with regulatory requirements that make sending marketing email through US-incorporated SaaS providers operationally difficult. Self-hosted Acelle on EU-hosted infrastructure (Netherlands, Bulgaria, Germany) places the subscriber data and campaign metadata under EU jurisdiction with full data ownership. The compliance auditability of "we own the database, we own the IPs, we operate under EU law" is structurally different from "we trust SendGrid's compliance certifications". For some operators this is the entire reason they migrate.

5. Laravel-shop agency or product team that wants to extend the platform

An engineering team that already runs Laravel apps in production and wants email-marketing capability that extends naturally into their existing codebase. Acelle's Laravel 12 base means the team can write custom Composer packages, integrate with their existing authentication system, embed Acelle UI components into their parent application, and treat the email-marketing layer as a first-class part of their stack rather than as a third-party tool they integrate with via API. The technical fit is excellent; the only question is whether they want to operate the infrastructure themselves or have us do it.

Five mistakes operators make deploying Acelle Mail in production

About a third of Blue Spirit's managed Acelle clients are migrating from a self-deployed Acelle installation that hit operational walls. The five mistakes below recur often enough to be predictable:

1. Skipping the queue worker monitoring setup

Acelle's campaign sends are processed by Laravel queue workers managed by Supervisor. If a worker crashes silently (out-of-memory error, MySQL connection drop, Redis hiccup), campaigns quietly stall while Acelle's UI shows "sending in progress" indefinitely. Operators discover this hours or days later through customer complaints. The fix: Supervisor configuration with auto-restart on failure, queue depth alerting (Redis LLEN monitoring), and Prometheus metrics on worker job processing rate. We include all of this in managed deployments; self-deployers frequently miss it because the Acelle docs assume operational expertise.

2. Running Acelle on shared hosting or under-provisioned VPS

Acelle's multi-tenant SaaS architecture and queue-worker fan-out is bandwidth-heavy on PHP-FPM workers and database connections. Operators running Acelle on $5/month shared hosting or 1GB-RAM VPS hit performance walls at 50K-100K emails/month — slow campaign queue draining, MySQL deadlock errors during high-concurrency sends, web UI timing out for tenant admins. Acelle realistically needs 4 vCPU and 8GB RAM minimum for production workloads, more for multi-tenant scenarios. The fix: provision appropriate hardware from day one rather than discovering the constraint mid-campaign.

3. Pointing Acelle at shared SES without IP isolation strategy

Acelle's first-class SES integration is a feature, but operators frequently configure it as "all tenants send through one shared SES account" without IP isolation. The result: one tenant's complaint rate degrades the shared SES sending IP, all other tenants' deliverability suffers, and the operator is left explaining why their SaaS's email reputation collapsed without obvious cause. The fix: either dedicated IPs per tenant (PowerMTA model) or per-tenant SES configuration sets with rate-limiting and sub-account isolation. Acelle supports both patterns; the operator choice matters.

4. Not configuring the Postfix bounce mailbox + Feedback Loop catcher

Acelle ingests bounces and complaints from feedback loops (FBLs) registered with major ISPs (Yahoo, AOL, Comcast). The FBL emails arrive at a designated mailbox that Postfix delivers and Acelle's bounce processor parses. Operators who skip this setup miss 60-80% of complaint signals because most ISPs use FBL rather than SMTP-bounce for spam complaints. Result: complaint rates appear artificially low in Acelle dashboards, sender reputation degrades silently, and the operator is blindsided by deliverability problems that the metrics did not show. The fix: register FBLs with all major ISPs, configure Postfix to deliver to the bounce mailbox, validate Acelle's bounce processor is consuming the mailbox correctly. Standard part of our onboarding.

5. Upgrading Acelle versions in production without staging validation

Acelle ships frequent point releases (4.1.5-p22, p23, p24, etc.) with bug fixes and security patches. Operators frequently apply these directly to production via the Upgrade Manager dashboard without first testing in staging. Most upgrades work cleanly; occasionally one breaks queue worker behavior, template rendering, or webhook delivery in subtle ways that take hours to diagnose under production load. The fix: maintain a staging environment matching production, apply upgrades to staging first, run a smoke-test campaign through staging, and only then promote to production. We do this for every managed customer; self-deployers frequently skip it because "the upgrade looks small".

How Acelle integrates with the broader email infrastructure stack

A failure mode in platform selection is treating Acelle as the entire email program. It is not. Acelle is the orchestration layer; it sits between your application sending campaigns and the MTA actually delivering email. Understanding where Acelle ends and the rest of the stack begins clarifies many architectural decisions during onboarding.

Upstream — your application or marketing team feeding Acelle

Acelle accepts data inputs through three primary channels: the web UI for marketers building campaigns interactively, the REST API for programmatic integration with your application stack, and CSV import for bulk subscriber list ingestion. Most production deployments use all three: the marketing team uses the UI for campaign design, the application uses the REST API for transactional triggers and subscriber management, and CSV import handles initial migration or periodic large imports.

The REST API is comprehensive — endpoints for lists, subscribers, campaigns, templates, automations, segments, and analytics. Operators integrating Acelle with their existing CRM (HubSpot, Salesforce, Pipedrive) typically wire the API for subscriber sync (CRM contact added → Acelle subscriber created), campaign trigger (CRM workflow event → Acelle campaign send), and analytics flow-back (Acelle delivery/open/click events → CRM activity timeline). The work involved is typical Laravel-style API integration; your engineering team handles it during onboarding or we can scope it as professional services.

The MTA layer — where Acelle hands off to PowerMTA or other senders

Acelle's "delivery server" abstraction lets you configure one or more outbound sending paths. Each delivery server is a named SMTP endpoint (or API endpoint for Amazon SES, SendGrid, Mailgun, etc.) with its own credentials, rate limits, and routing rules. Campaigns can be assigned to specific delivery servers, or Acelle can round-robin or weight-route across multiple servers. This abstraction is where multi-provider routing strategies get implemented.

For our managed Acelle deployments, the default delivery server is a dedicated PowerMTA VirtualMTA pool sized to your tier (Starter: 5 IPs, Growth: 15 IPs, Scale: 50+ IPs). Each tenant can be configured to send through a tenant-specific VMTA (full reputation isolation) or share a tier-default VMTA pool (cost-optimized). The trade-off is reputation isolation vs IP utilization efficiency; we discuss the right pattern during onboarding based on your tenant count and per-tenant volume.

The DNS authentication layer — independent of Acelle

SPF, DKIM, DMARC, and MTA-STS records live in your domain's DNS, not in Acelle. Acelle generates DKIM signing keys per sending domain (each tenant typically has their own sending domain with their own keys), and the operator publishes the corresponding DKIM TXT record in DNS. Acelle's "domain verification" feature checks SPF, DKIM, and DMARC alignment per sending domain and flags issues in the tenant admin UI. This is the layer where tenant-onboarding most frequently breaks; tenants who do not control their own DNS struggle to publish the required records, which delays their first send.

The fix in our managed deployments: a checklist-driven onboarding that walks each tenant through DNS record publishing, validates the records before allowing the first campaign, and provides per-tenant troubleshooting docs for common DNS provider quirks (Cloudflare, Google Domains, Namecheap, etc.). Acelle's domain verification feature is the validation gate; the operational layer around it is what makes tenant onboarding actually work.

Downstream — bounce processing, complaint handling, analytics

After PowerMTA (or Amazon SES, SendGrid, etc.) delivers email, three downstream signals flow back to Acelle: hard/soft bounces, complaint reports from feedback loops, and engagement events (opens, clicks). Each signal arrives via a different mechanism and needs its own integration plumbing.

Bounces from PowerMTA arrive as accounting log entries; our bounce parser daemon consumes the CSV logs and inserts bounce events into Acelle's database via the REST API. Bounces from Amazon SES arrive via SNS topic subscription with HTTP webhook; Acelle ingests them via a dedicated webhook endpoint. Complaints from Yahoo, AOL, Comcast, and other ISPs arrive at a designated Postfix mailbox and our FBL parser ingests them. Open and click events arrive via the tracking pixel and click-redirect URLs that Acelle injects into outbound campaigns; the Acelle web app handles these directly. Each downstream channel needs to be configured correctly during initial deployment; missing any of them creates blind spots in deliverability monitoring.

Acelle vs Mautic — when each open-source platform wins

Both Acelle and Mautic are credible open-source email-marketing platforms with active development communities and production deployments serving millions of messages. The choice between them is not about features at the surface level but about architectural fit and operational philosophy. Below the structural comparison we run during platform-selection conversations:

Acelle wins when multi-tenant SaaS is the primary use case

Acelle's multi-tenant architecture is built into the core — plans, subscriptions, billing, resource quotas, and tenant-level branding are first-class concepts. Mautic's architecture is single-tenant; running Mautic as a multi-tenant SaaS requires either separate Mautic installations per tenant (operationally expensive) or extensive custom development to layer multi-tenancy on top of Mautic's single-tenant data model. For SaaS builders embedding email marketing into their product, Acelle is structurally the right choice; Mautic forces architecture compromises that cost months of engineering.

Mautic wins when marketing automation sophistication is the primary use case

Mautic's automation workflows are best-in-class among open-source platforms — visual drag-and-drop campaign builders, trigger-based sequences with branching logic, lead scoring models, behavioral segmentation, and integration with form builders and landing page tools. Acelle's automation is competent but simpler; Mautic's is comparable to enterprise marketing automation platforms like HubSpot or Marketo at a fraction of the cost. For teams whose primary email-marketing need is sophisticated automation rather than multi-tenant scale, Mautic is structurally the right choice.

Acelle wins on Laravel-friendly extensibility

Acelle is written in Laravel 12 — an idiomatic, modern PHP framework that most PHP developers know well. Mautic is written in Symfony 6 — also modern, but a different framework with different conventions. Engineering teams who already run Laravel applications can extend Acelle naturally; the same teams have to learn Symfony patterns to extend Mautic. The technical debt of "we have to maintain a Symfony fork of Mautic plus our Laravel application stack" is meaningful for small engineering teams. For Laravel shops, Acelle is the right answer; for Symfony shops, Mautic is the right answer.

Mautic wins on pure open-source license clarity

Mautic is GPL-licensed open-source; you can use, modify, and redistribute the source code freely. Acelle is sold via CodeCanyon under a single-installation license ($64-$199 one-time depending on tier); you have full source code access but cannot redistribute. For operators with strict open-source licensing requirements (some compliance environments, some procurement processes), Mautic's GPL license is the right answer. For most commercial operators the licensing distinction does not affect usage.

Both win on data ownership and self-hosted control

The structural advantage of either Acelle or Mautic over SaaS alternatives (Mailchimp, SendGrid, Constant Contact) is data ownership and operational control. Both platforms run on your own infrastructure, store subscriber data on your own servers, and let you choose which sending providers to use. The cost economics improve dramatically at scale (we showed the 60-70% savings vs Mailchimp at mid-market scale earlier in this page), and the regulatory/compliance posture improves for sensitive verticals. The choice between Acelle and Mautic is secondary to the choice of "self-hosted vs SaaS" in the first place.

The hybrid pattern — running both Acelle and Mautic for different purposes

Some operators run both platforms for different segments of their email program. Acelle handles the multi-tenant SaaS side (giving end-customers branded email-marketing capability); Mautic handles the parent company's own marketing automation (sophisticated lead nurturing, behavioral campaigns, sales handoffs). The two platforms operate independently with different databases, different Laravel/Symfony stacks, and different operational conventions; they can share a PowerMTA back-end for actual sending. The hybrid pattern adds operational complexity but matches actual organizational needs better than forcing a single platform to do both jobs poorly.

Acelle Mail hosting — frequently asked questions

What is Acelle Mail and how does it compare to MailWizz?

Acelle Mail is a Laravel-based open-source email marketing platform. Compared to MailWizz, it has a more modern Bootstrap-4 UI, built-in multi-customer / SaaS architecture from day one, and first-class Amazon SES integration. MailWizz is more mature and has more third-party extensions; Acelle is cleaner for SaaS builders and teams who prefer a Laravel codebase they can extend.

Do I need to buy Acelle separately?

Every Acelle plan we sell includes a valid Acelle licence activated on your server. If you own one already, we can migrate it and apply a discount.

Can Acelle handle my monthly volume?

Acelle itself scales well because the heavy lifting is done by the MTA behind it. With our PowerMTA back-end, a Blue Spirit-hosted Acelle deployment will comfortably sustain the same volumes as our equivalent MailWizz plan — Starter 250k/day, Growth 1M/day, Scale 5M/day.

I want SaaS from day one. Is Acelle better than MailWizz for that?

Arguably yes. Acelle ships with native customer management, plans, subscriptions and billing. MailWizz has all of this but bolted on through an extension. If you know you are building a multi-tenant email product, Acelle usually gets you there faster.

What if I want to switch from MailWizz to Acelle (or vice versa)?

We handle migration. Lists, subscribers, campaigns, templates and historical stats — we move them one-way or the other. Budget a 2 to 5 day transition depending on data size.

What version of Acelle is current and what are the system requirements?

Acelle 4.1.5 LTS (released March 15, 2026) is the current stable version. It runs on Laravel 12 with PHP 8.2+ as the minimum requirement. Our managed deployments always run the current LTS with security patches applied within 7 days of release. Self-deployers should plan to migrate from Acelle 4.0 or earlier within Q2-Q3 2026 because security patches will track 4.1.x going forward.

How does Acelle handle multi-provider sending (Amazon SES + PowerMTA + others)?

Acelle supports multiple "delivery server" configurations per installation, and you can route different campaigns or different tenants through different providers. A common pattern: route transactional through Postmark for inbox placement guarantees, route bulk marketing through dedicated PowerMTA for cost economics, route Amazon SES for high-volume but lower-priority sends. Acelle handles the routing logic; the providers handle the actual SMTP. We help configure the routing strategy during onboarding.

Can I extend Acelle with custom code or build new features?

Yes. Acelle is open-source Laravel 12 — you have full source code access and can extend any part of the application. The Laravel framework conventions (service providers, middleware, queue jobs, Eloquent models) all apply. We have customers who have built custom integrations with their CRM, custom analytics dashboards, and entirely new features on top of the Acelle base. The extension model is significantly cleaner than MailWizz extensions because Laravel patterns are more modern than Yii 1.x patterns.

What happens if my Acelle deployment hits a production issue at 3 AM?

For managed deployments, we run 24/7 on-call rotation with response SLA depending on plan tier (Starter: 4-hour response, Growth: 1-hour response, Scale: 15-minute response). Standard issues resolved within the response window; complex issues may require longer investigation but are actively worked. For self-deployed Acelle without managed support, you are on your own — Acelle Inc. provides documentation but not 24/7 production support.

Can I run Acelle in EU jurisdiction for GDPR compliance?

Yes. We operate Acelle deployments in Netherlands and Bulgaria for EU-jurisdiction-required customers. The full stack — Acelle, MySQL, Redis, PowerMTA, backup storage — runs on EU infrastructure under EU law, with no US data flow. This is structurally different from running Acelle in the US and claiming GDPR compliance through contractual terms; the data physically lives in EU jurisdiction. For compliance-sensitive senders this is frequently the deciding factor between Acelle managed hosting and US-incorporated SaaS alternatives.

Let's put Acelle on infrastructure your customers won't complain about.

Request a quote Chat on WhatsApp