Mautic: self-hosted marketing automation for teams that want to own the contact database

What Mautic replaces, and for whom

Mautic is marketing automation software that you install on your own infrastructure. The README describes it as open source software for delivering integrated marketing campaigns, and the project's stated aim is to be privacy-focused, accessible and extendable. The practical consequence is that contacts, campaign history and email sending stay inside systems you operate rather than inside a vendor's account.

The audience is narrower than the tagline suggests. The GitHub repository is a development tree, not a distribution artefact. The installation section carries a warning that installing from GitHub is only for people comfortable with the command line, that various CLI commands are needed to get Mautic working and keep it working, and that if the source or database schema drifts out of sync with a release, the release updater may stop working and require manual updates. For production the README points to Composer installation or to the pre-packaged download at mautic.org/download.

So the realistic adopter is an organisation with someone who can run a PHP application: an agency hosting campaigns for clients, a company with a sysadmin and a data-protection reason to keep contact records in-house, or a team already running other self-hosted services. A two-person marketing team with no server experience is not the target, and the README does not pretend otherwise.

How Mautic is put together: PHP application, Composer, plugins

The repository is a PHP application. The top-level layout shows app/, bin/, config/, plugins/, themes/, translations/, templates/, media/, var/ and tests/, with index.php as the web entry point. Composer manages PHP dependencies, and composer.json sits at the root alongside composer.lock. Front-end assets are built with webpack: package.json declares webpack-cli and patch-package as devDependencies, and the dependency list is dominated by CKEditor 5 packages, which is the editor used for building emails and landing page content.

Extensibility is the part that distinguishes Mautic from a hosted tool. There is a plugins/ directory, and the README lists creating any integration you need as a benefit. That is the mechanism by which Mautic connects to other systems: rather than a fixed catalogue of connectors controlled by the vendor, the integration surface is code you can write or install. The same applies to the interface, which the README says is fully customisable on both the frontend and backend.

The project also exposes an API, and the repository carries an importmap.php file alongside the webpack configuration, reflecting a PHP application that has been incrementally modernised rather than rewritten. The presence of UPGRADE-3.0.md through UPGRADE-7.0.md, plus UPGRADE-PHP-TO-TWIG-TEMPLATES.md, is a useful signal about how the codebase has evolved and how much migration documentation exists for anyone moving between major versions.

Installing Mautic and running a first campaign

The README recommends installing via Composer and points to the command-line documentation for the full procedure. You need Composer available on the machine before you start, because the GitHub version is a development release and Composer is what pulls in the vendor packages. The three-step path for the zip route is: download and extract the repository zip into your web root, run composer install, then open the site in a browser and complete the web installer.

composer install

After that command finishes, the vendor dependencies are present. Opening the site in a browser then hands over to the web installer, which walks through the database and administrator configuration. The README does not reproduce the installer's screens, so treat the linked installation documentation as the source of truth for the fields it asks for.

If DDEV is installed, the repository ships a DDEV configuration, so you can skip the manual sequence. The README gives two variants: running ddev config followed by ddev start, or, if a DDEV project configuration is already present, running ddev start directly. Either way the first-run process installs dependencies and configures Mautic for use.

ddev config
ddev start

Once the installer completes and you log in, the first genuinely useful exercise is a campaign rather than an email blast. Mautic's model is contacts plus segments plus campaigns, and the README advertises unlimited segmentation and automation. Build a segment from a small set of test contacts, attach a campaign with a send-email action, and confirm the message leaves your infrastructure. That single loop proves the database, the cron or worker path and your mail configuration are all wired correctly, which is where most self-hosted installs fail first.

Where Mautic is the wrong tool

The most important limitation is stated by the project itself. Source code outside a tagged release should be considered alpha, may contain bugs, may cause unexpected results or data corruption or loss, and is not recommended for production. If you clone the default branch rather than installing a tagged release, you are running alpha software by the project's own definition. That is not a formality; it is the difference between a supported configuration and one where you are on your own.

The second limitation is operational. The README's warning is explicit that the GitHub route requires CLI commands not just to install Mautic but to keep it working, and that schema drift between source and database can break the release updater, forcing manual updates. A self-hosted marketing automation instance is a service with a database, scheduled jobs and an outbound mail reputation. Someone has to own that.

The third is scope confusion. Mautic is marketing automation, not a CRM in the sales-pipeline sense. If your real need is deal stages, quotes and account management, Mautic will not cover it, and the README makes no claim that it will. Teams that buy Mautic expecting a CRM usually end up running two systems.

Finally, deliverability is not something the software solves. Mautic gives you the sending mechanism and the data ownership; it does not give you sending reputation, and the README does not claim otherwise.

Mautic compared with hosted marketing automation

The honest comparison is not feature-by-feature against a specific vendor, because the difference is structural. A hosted marketing automation platform gives you an account, a sending domain they manage, a support contract and a monthly bill that scales with contact count. Mautic gives you a PHP application, a database you own, and the operational work that comes with both.

The trade shows up in three places. Cost model: Mautic is free to use, and the README frames this as no vendor lock-in and no third-party SaaS dependency. That is true at the licence level, but the cost moves to hosting, mail infrastructure and the person who maintains the install. Data location: with Mautic the contact records sit in your database, which is the reason many teams choose it and also the reason you inherit the compliance obligations that come with holding that data. Extensibility: a hosted platform offers what its integration catalogue offers, while Mautic offers a plugins/ directory and the ability to write the integration yourself. That is a real advantage for unusual requirements and a real disadvantage if you wanted something that works on day one.

There is also a middle path the README itself mentions: the project offers trials that deploy in minutes for evaluation, and a pre-packaged download for production. Trying Mautic through a trial before committing to self-hosting is the lowest-risk way to find out whether the campaign builder fits how your team thinks.

Maintenance, releases and licence questions

Release cadence is visible from the tags. Mautic Community 7.2.0, subtitled Lynx Edition, was released on 2026-09-02, following 7.1.3 on 2026-07-07 and a 7.2.0 release candidate on 2026-06-02. The repository's last push was on 2026-09-18, so the default 7.x branch is receiving commits. That is a healthy signal, but it is a statement about activity, not about whether any particular commit is stable.

Upgrade cost is the thing to budget for. The repository carries UPGRADE-3.0.md, UPGRADE-4.0.md, UPGRADE-4.3.md, UPGRADE-5.0.md, UPGRADE-6.0.md and UPGRADE-7.0.md, plus UPGRADE-PHP-TO-TWIG-TEMPLATES.md. The existence of that last file is the important detail: if you have customised templates, a PHP-to-Twig migration is a distinct piece of work on top of the version upgrade. Custom themes and custom plugins are the two places where a Mautic upgrade stops being a routine operation.

On licensing, GitHub reports the licence as NOASSERTION, which means the platform could not classify the LICENSE.txt file into a standard identifier. The README describes Mautic as open source and free to use, and the project carries a Digital Public Goods verification badge dated 2024. None of that tells you what your obligations are if you modify and redistribute Mautic or bundle it into a product. Read LICENSE.txt in the repository and, if redistribution is on your roadmap, get your own legal review; this article is not legal advice. The same applies to the CKEditor 5 packages in package.json, which are separate dependencies with their own terms.

Editorial conclusion

Adopt Mautic if you can run a PHP application with Composer, a database and a mail path you control, and if owning the contact records is the reason you are looking. Do not adopt it if you need a managed service with no server work, or if a CRM with sales pipeline management is what you actually need. Before committing, verify the supported PHP and database versions on the requirements page, check that your chosen release is a tagged release rather than a branch checkout, and confirm that the 7.x upgrade documents cover your current version.

Frequently asked questions

Official sources

1. Issues
2. mautic/mautic on GitHub
3. Project website
4. README
5. Releases