How to Self-Host Mautic: 2026 Setup Guide

I run open-source implementations at Mith Tech in Bengaluru, and Mautic is one of the tools I reach for when an SMB wants marketing automation without a per-contact subscription treadmill. This guide is the setup I actually follow, in order, with the parts that trip people up called out.

Honest take: Mautic gives you a lot for free, but deliverability and cron are where self-hosters lose weeks — budget real attention there, not on the install itself.

What is Mautic and why self-host it?

Mautic is an open-source marketing automation platform for email campaigns, contact segmentation, landing pages, and lead scoring. Licensed under GPLv3, the software is free — you run it on infrastructure you control, so contact data never sits on a vendor's servers. Self-hosting removes per-contact subscription fees and gives full database access.

For an Indian SMB, that ownership matters. Your lead list is a business asset, and keeping it on your own server sidesteps the escalating per-contact billing that hosted platforms use. The trade-off is real: you own patching, uptime, and deliverability too. If you want the managed-versus-self-hosted reasoning laid out fully, I cover it in our open-source HubSpot alternative piece.

Skimmable summary: Mautic is GPLv3 marketing automation you host yourself — no per-contact fees, but you own the operations.

Which Mautic version should I install in 2026?

Install from the current stable line unless you have a specific reason to pin to long-term support. As of mid-2026 the latest stable line is Mautic 7, which runs on a modern Symfony and PHP 8.x stack. Mautic 6 and Mautic 5.2 are the long-term-support branches, still receiving security and bug fixes on published timelines.

Here is how the branches compare for a self-hoster:

Check the official Mautic releases and requirements pages before you download — supported PHP and database versions move over time, and the installer will refuse to proceed if your stack is too old.

Skimmable summary: Pick Mautic 7 for a fresh install, or a supported LTS branch if you value a longer patch runway over new features.

How do I install self-hosted Mautic step by step?

Installation is a server-preparation phase followed by Mautic's own browser-based installer. Prepare the operating system, PHP extensions, database, and web server first, place the Mautic files in your web root, then walk through the guided setup at your domain. The whole path takes an afternoon on a clean server.

Skimmable summary: Prep OS, PHP, database, and web server, drop in the files, then complete Mautic's browser installer over HTTPS.

How do I configure email sending in Mautic?

Connect an external SMTP service rather than relying on the server's local mail. In Mautic's configuration under Email Settings, choose your transport, enter the SMTP host, port, encryption, and authentication credentials from your delivery provider, then send a test. External relays give you authentication and reputation handling that a raw server cannot.

A critical change arrived in Mautic 5 and carries into 6 and 7: outbound email flows through a Symfony Messenger queue. You choose a spool or immediate mode, but for any real volume you queue messages and let a background worker dispatch them. That keeps campaign sends off the web request and makes throughput predictable.

Skimmable summary: Wire Mautic to an external SMTP relay in Email Settings, test it, and remember that Mautic 5+ dispatches mail through a Messenger queue.

What cron jobs does self-hosted Mautic need?

Mautic automates nothing without cron. Three jobs are mandatory — segment updates, campaign updates, and campaign triggers — and the official documentation insists you stagger them so they never start in the same minute. On Mautic 5 and later you also run a messenger worker to actually send the queued email.

Here are the core commands (run as the web-server user, adjusting the path to your install):

The messenger consumer must be given a bound — --time-limit, --memory-limit, or --limit — so it exits cleanly instead of running forever. Tune --batch-limit on the segment and campaign jobs to match your server's resources. Optional jobs like IP-lookup database downloads and contact imports round things out.

Skimmable summary: Run three staggered cron jobs for segments and campaigns, plus a bounded messenger worker for email — nothing automates without them.

How do I improve Mautic email deliverability?

Deliverability lives mostly outside Mautic, in your sending domain's DNS and reputation. Publish an SPF record authorising your SMTP provider, enable DKIM signing on the provider side, and add a DMARC policy. Warm the sending domain gradually and keep lists clean, because Mautic sends whatever you tell it — inbox placement is the sender's responsibility.

Practical deliverability checklist:

• SPF — authorise your SMTP relay's servers to send for your domain.
• DKIM — turn on signing at the provider and publish the public key in DNS.
• DMARC — start with a monitoring policy, then tighten as you confirm alignment.
• Dedicated sending domain or subdomain — isolate marketing mail from transactional and staff email.
• List hygiene — honour unsubscribes, prune hard bounces, and avoid buying lists.

Mautic's own bounce handling and Do-Not-Contact features help, but they work best on top of authenticated DNS, not instead of it.

Skimmable summary: Set SPF, DKIM, and DMARC, warm your domain, and keep lists clean — Mautic sends, but your DNS and reputation decide the inbox.

How should I back up a self-hosted Mautic instance?

Back up two things on a schedule: the MySQL or MariaDB database and the Mautic file tree, especially the media, config, and any custom theme directories. Automate a nightly database dump plus a file archive, store copies off the server, and periodically test a restore — an untested backup is a hope, not a safeguard.

Because you own the stack, you also own recovery. A simple, reliable pattern is a nightly mysqldump piped to a compressed file, a tar of the Mautic directory, and a sync of both to separate object storage or another host. Keep several dated generations so you can roll back past a bad change, not just the latest state. If you would rather not run this yourself, a managed platform approach can take the operational load — our PaaS platform page explains that route.

Skimmable summary: Automate nightly database and file backups, push them off-server, keep dated generations, and test restores before you need one.

Frequently asked questions

Is Mautic really free to self-host?

Yes. Mautic is open-source software under GPLv3, so the platform itself costs nothing to download and run. Your only spend is infrastructure — server hosting and an email-sending service — plus any time or help you bring in to set it up and maintain it. There is no per-contact licence fee.

Do I need coding skills to self-host Mautic?

You need comfort with a Linux command line, DNS records, and cron more than programming. The install is largely guided, but preparing the server, configuring SMTP, and troubleshooting cron demand sysadmin confidence. Teams without that in-house often bring in an implementation partner for the initial setup and hardening, then run day-to-day themselves.

Why are my Mautic campaigns not sending?

The usual cause is missing or misconfigured cron. If the segment, campaign, and messenger jobs are not running, contacts never enter campaigns and queued email never leaves. Check that all cron jobs execute as the correct user, that the messenger consumer has a limit flag, and that your SMTP credentials pass Mautic's test send.

Can I run Mautic on shared hosting?

Generally no, not well. Mautic needs specific PHP extensions, writable directories, real cron access, and a background worker for email — things shared hosting often restricts. A small VPS or cloud server gives you the control Mautic assumes. Managed Mautic hosting is a middle path if you want the platform without the server administration.

What is the difference between Mautic LTS and stable versions?

The current stable line carries the newest features and gets active development attention. Long-term-support branches trade newer features for a longer window of security and bug fixes, which suits teams that prize stability and predictable maintenance. For a fresh 2026 install, current stable is the usual pick; existing production installs often stay on a supported LTS branch.

Does Mautic integrate with ERPNext?

Mautic and ERPNext are separate open-source tools, but both expose REST APIs, so you can sync contacts, leads, and campaign activity between them with an integration layer. That gives you marketing automation in Mautic feeding a single source of business truth in ERPNext — a common request I handle for SMBs standardising on open-source.

We install, harden, and connect Mautic to your stack — including ERPNext — so you get marketing automation you fully own. See our Frappe and ERPNext platform work or get in touch.