Self-hosted Mautic / Listmonk: email marketing without Mailchimp

To run Mautic self-hosted or Listmonk, it is optimal to use a VPS with 2–4 GB RAM, 2 vCPUs, and a 40 GB+ NVMe drive. This allows you to save up to 90% of your budget compared to Mailchimp for databases exceeding 10,000 subscribers.

Mautic self-hosted vs Listmonk hosting: which one to choose for your project?

The choice between Mautic and Listmonk depends on the complexity of your marketing funnels and mailing volume. Mautic is a full-featured Marketing Automation Platform (MAP) that competes with HubSpot and Salesforce. Meanwhile, Listmonk is focused exclusively on high-performance delivery of newsletters and transactional notifications.

Mautic — a marketing automation powerhouse

Mautic is written in PHP and requires significant resources to process queues and segment the database. Its main advantage is the visual campaign builder, where you can build complex logic chains: "if the user opened email A and clicked link B, wait 2 days and send email C." To extend automation capabilities, self-hosted n8n is often used to connect Mautic with CRM systems and messengers.

Listmonk — a lightweight solution for mass mailings

Listmonk is written in Go and uses PostgreSQL as its database. It is an incredibly fast solution: it can send up to 10,000 emails per minute on minimal hardware. If your goal is a newsletter own server for weekly digests or simple promotions without multi-level conditions, Listmonk is the better choice due to its simplicity and low RAM consumption (less than 500 MB in standby mode).

System requirements and VPS choice for a newsletter own server

For the stable operation of mautic self hosted and Listmonk, disk subsystem performance and CPU stability are critical. Mautic actively uses the database to track every click and email open, which creates a high IOPS load.

Minimum and recommended server specifications

Below are the requirements for various usage scenarios. When choosing a plan, keep in mind that Mautic requires more resources due to PHP-FPM and Cron jobs.

Parameter	Listmonk (up to 50k emails)	Mautic (up to 50k contacts)	Mautic (100k+ contacts)
CPU (Cores)	1 vCPU (2.5+ GHz)	2 vCPU (3.0+ GHz)	4-8 vCPU
RAM	1 GB	4 GB	8-16 GB
Disk (NVMe)	20 GB	50 GB	100 GB+
OS	Ubuntu 22.04 / 24.04	Ubuntu 22.04	Debian 12 / Ubuntu 24.04

OS optimization for high-load email systems

When working with email marketing selfhost solutions on Linux, it is necessary to increase open file limits and optimize the TCP stack. Edit the /etc/sysctl.conf file, adding the following parameters to improve network connection handling:

net.core.somaxconn = 1024
net.ipv4.tcp_max_syn_backlog = 2048
net.ipv4.tcp_fin_timeout = 15
fs.file-max = 100000

After making changes, run the command sysctl -p. This will prevent "Too many open files" errors during mass mailings via Listmonk or intensive tracking in Mautic.

How to deploy your own Mailchimp: step-by-step Listmonk and Mautic installation

You can create your own Mailchimp on a VPS in 30-40 minutes using Docker. This isolates application dependencies from the main system and simplifies the update process.

Installing Listmonk via Docker Compose

Listmonk is provided as a ready-to-use Docker image. To run it, you will need a docker-compose.yml file that includes the application itself and a PostgreSQL database.

version: '3.7'
services:
  db:
    image: postgres:14-alpine
    container_name: listmonk_db
    volumes:
      - listmonk_data:/var/lib/postgresql/data
    environment:
      - POSTGRES_PASSWORD=secure_password
      - POSTGRES_USER=listmonk
      - POSTGRES_DB=listmonk

  app:
    image: listmonk/listmonk:latest
    container_name: listmonk_app
    ports:
      - "9000:9000"
    environment:
      - LISTMONK_db__host=db
      - LISTMONK_db__user=listmonk
      - LISTMONK_db__password=secure_password
      - LISTMONK_db__database=listmonk
    restart: unless-stopped
volumes:
  listmonk_data:

After starting with docker-compose up -d, the interface will be available on port 9000. Don't forget to configure Nginx as a Reverse Proxy with an SSL certificate from Let's Encrypt for secure access.

Setting up Mautic on a LAMP/LEMP stack

For Mautic, it is recommended to use PHP 8.0 or 8.1 (check the compatibility of the current version). It is important to configure PHP limits in php.ini:

memory_limit = 512M
max_execution_time = 300
upload_max_filesize = 64M
date.timezone = UTC

The key to Mautic's operation is Cron jobs. Without them, the system will not update segments or send emails. A minimal set of tasks in crontab -e:

# Update segments every 15 minutes
*/15 * * * * php /var/www/mautic/bin/console mautic:segments:update
# Update campaigns every 15 minutes
*/15 * * * * php /var/www/mautic/bin/console mautic:campaigns:update
# Trigger campaign events
*/5 * * * * php /var/www/mautic/bin/console mautic:campaigns:trigger
# Send emails from queue
*/5 * * * * php /var/www/mautic/bin/console mautic:emails:send

If you plan to migrate a project from other platforms, study the migration from Vercel/Netlify to your own VPS to understand the principles of infrastructure management in an isolated environment.

SMTP setup and integration with Postmark, SendGrid, and Amazon SES

Using listmonk hosting doesn't mean you should send emails directly from your VPS IP address. Most hosting provider IP addresses have a neutral or low reputation in the eyes of Gmail and Outlook.

Why you shouldn't send emails directly from a VPS

Direct sending via Sendmail or Postfix often leads to landing in the "Spam" folder. Email providers block entire subnets if they notice suspicious activity. Using an external SMTP relay solves the deliverability problem and provides detailed analytics on bounces.

Configuration of relay services

The following services are best suited for integration with Mautic or Listmonk:

• Amazon SES: The cheapest option ($0.10 per 1000 emails). Requires identity verification and account warm-up.
• Postmark: Best deliverability for transactional emails. Higher price, but impeccable IP reputation.
• SendGrid/Brevo: Good free limits (up to 100-300 emails per day) for small databases.

In Listmonk settings (Settings -> Messenger), select the SMTP type, specify the host (e.g., email-smtp.us-east-1.amazonaws.com), port 587, and your credentials. Be sure to enable TLS. To protect passwords for these services, we recommend using self-hosted Vaultwarden to keep access keys secure.

Email marketing selfhost and Deliverability issues

Deliverability is the main metric in email marketing selfhost. To prevent your emails from being blocked, you must correctly configure DNS records on your domain's side.

Technical configuration of DNS records

There are three mandatory records without which mailing will be ineffective:

1. SPF (Sender Policy Framework): Specifies which servers are allowed to send mail on behalf of your domain. Example: v=spf1 include:amazonses.com ~all.
2. DKIM (DomainKeys Identified Mail): A digital signature for the email, confirming it wasn't modified during transmission. Generated on the SMTP provider's side.
3. DMARC: A policy telling the receiving server what to do if SPF or DKIM fails. Start with a soft policy: v=DMARC1; p=none; rua=mailto:[email protected].

Domain warm-up and IP reputation management

If you've just launched your newsletter own server, don't send 50,000 emails on the first day. Start with 500 emails to your most loyal subscribers, gradually increasing the volume by 20% daily. Monitor the Spam Rate — it should not exceed 0.1%. To analyze user behavior on the site after clicking from an email, it is useful to implement self-hosted analytics (Plausible or Umami), which is not blocked by browsers as aggressively as Google Analytics.

Economics and cost comparison: self-hosted vs SaaS

The main incentive for implementing mautic self hosted is a radical reduction in operating costs. SaaS platforms like Mailchimp or ActiveCampaign increase subscription costs exponentially as your database grows.

Subscriber Base	Mailchimp (Standard)	Self-hosted (VPS + SES)	Monthly Savings
2,500	$60	$10 (VPS) + $1 (SES) = $11	$49
10,000	$135	$15 (VPS) + $5 (SES) = $20	$115
50,000	$350	$25 (VPS) + $20 (SES) = $45	$305
100,000	$700+	$40 (VPS) + $40 (SES) = $80	$620+

Hidden infrastructure maintenance costs

It must be taken into account that a self-hosted solution requires system administrator time. Updating Mautic can sometimes be painful due to database migrations. However, when using Docker containers and regular backups, maintenance time is reduced to 1-2 hours per month.

Security and backups of your subscriber base

Your email database is your most valuable asset. Unlike cloud services, in a self-hosted setup, the responsibility for data safety lies entirely with you.

Data protection and GDPR compliance

Ensure that access to the Mautic or Listmonk control panel is protected by two-factor authentication (2FA). Also, restrict access to database ports and Docker sockets using a Firewall (UFW). Allow incoming connections only for ports 80, 443, and SSH.

Database backup strategy

For Listmonk, a PostgreSQL dump is sufficient. For Mautic, you need to back up both the database (MySQL/MariaDB) and the folder with media files (assets). Use a script for daily data copying to remote storage (e.g., S3-compatible):

# Example of Listmonk database backup
docker exec listmonk_db pg_dump -U listmonk listmonk > backup_$(date +%F).sql

Regularly check the integrity of backups by restoring them on a test VPS instance. This ensures that in case of disk failure or a failed update, you can restore marketing operations in minutes.

Conclusions

To launch professional email marketing on your own server, it is optimal to use Listmonk if you only need newsletters, or Mautic for complex automation chains. Switching to a self-hosted model allows you to reduce marketing costs by 5–10 times and fully control your subscriber data without the risk of being blocked by foreign SaaS services.