Docker image
Mautic in Docker. Marketing automation, cron solved.
Mautic is open source marketing automation: email campaigns, landing pages, contacts, segments, forms and lead scoring, without per-contact SaaS pricing.
Prefer not to run it yourself? Managed Mautic from $13.33/mo
# Mautic in Docker, base pinned by digest docker pull ghcr.io/remarkablecloud/mautic:5.2.11-r1 docker compose up -d
- Current build
5.2.11-r1, updated Sep 12, 2026- Base
- Mautic 5 official, digest-pinned
- What's inside
- Built-in cron loop, headless install, generated admin, MySQL 8 pairing
- Upstream license
- Mautic: GPL-2.0-or-later.
The image
What our image adds.
What changes from upstream Mautic, and why it matters in production.
Built-in cron loop
Segment updates, campaign triggers and email queue processing run inside the container on a sane schedule; no separate cron container, no host crontab.
Headless install with a generated admin
The installer runs and the administrator exists before Apache serves its first request; the install wizard is never reachable by a visitor.
Persisted secret key and config
The application secret and local configuration live on volumes, so recreating the container never invalidates sessions or webhooks.
Migrations on boot
Later versions migrate the database automatically when the container starts on a new tag.
Digest-pinned base
The PHP and Apache underneath change only when we rebuild, scan and promote.
Run it yourself, or not
Same image either way.
Pull it and run it anywhere, or let us run Mautic for you on a managed server with updates, monitoring and snapshots.
Run Mautic yourself
- Pull it from GHCR and run it on any Docker host
- The guide below: compose, environment, backups, upgrades
- You patch, back up and watch it
Mautic on a managed server
- Installed for you from this same image, $0 for the app
- Updates with a snapshot first, monitoring and a managed firewall
- A 4 GB server from $13.33/mo billed annually, with room for more apps
The guide
Run it in production.
Compose file, environment reference, hardening, backups and upgrades, written by the people who build the image.
On this page
Architecture at a glance
Two containers: mautic (Apache + PHP + cron loop) and db (MySQL 8). Volumes persist the database, Mautic configuration and media. The app serves HTTP on 80 behind your TLS proxy, with MAUTIC_SITE_URL driving generated links.
Docker Compose walkthrough
Set DB_PASSWORD, DB_ROOT_PASSWORD and SITE_URL, bring the stack up, and read the generated admin credentials from the container log on first boot. Then the two settings that make Mautic actually useful: configure the email transport (SMTP relay or provider API) in Configuration, and set the tracking script on your sites.
Environment variable reference
| Variable | Purpose |
|---|---|
| MAUTIC_DB_HOST / _PORT / _NAME / _USER / _PASSWORD | MySQL connection |
| MAUTIC_SITE_URL | Public https URL; drives tracking, links and webhooks |
| SMTP configuration | Set in the UI or env; nothing sends without it |
Hardening notes
The install wizard never runs in the browser, which removes the most common Mautic takeover path. Keep the DB on the internal network, keep 80 behind the proxy, and treat the config volume as sensitive; it holds the secret key.
Backups
The MySQL database plus the config and media volumes are the whole system. Dump the database on schedule; media matters if you host campaign images and assets locally.
Upgrades
Pull the new tag and recreate; migrations run on boot. Mautic majors occasionally change plugin compatibility, so read the changelog entry before a major jump, and test campaigns after.
Changelog
Each build is pinned by digest and recorded here, so you can see what changed before you pull a new tag.
-
5.2.11-r1Current Sep 12, 2026
Mautic and other product names are trademarks of their respective owners. RemarkableCloud is not affiliated with or endorsed by them.
FAQ
Mautic in Docker, answered.
Short answers from the people who build and run this image.
Does email sending work out of the box?
The machinery does; the transport is yours to configure. Point Mautic at your SMTP relay or provider and send a test before launching a campaign.
Where do the cron jobs run?
Inside the container, on a loop tuned for single-server installs. You can see the schedule in the container log.
Can I use MariaDB instead of MySQL?
The stack ships MySQL 8, which is Mautic 5's best-tested pairing; stay on it unless you have a reason not to.
Where are the admin credentials?
Generated on first boot and printed once to the container log; store them, then change the password in your profile.
Pull it, or let us run it.
The same image runs Mautic on our managed servers, updates and monitoring included.