Best VPS for Listmonk in 2026: Requirements & Costs
Listmonk is a fast, self-hosted manager for newsletters, mailing lists, campaigns, and transactional messages. It suits creators, publishers, clubs, and businesses that want control of subscriber data without paying a software fee per contact. A VPS keeps the application and its PostgreSQL database under your administration while giving you predictable storage, backups, and hosting costs.
There is one crucial boundary: Listmonk is not an SMTP mail server. It prepares campaigns and hands messages to an SMTP provider, which has its own fees, limits, reputation, and deliverability rules. The complete budget therefore includes both VPS infrastructure and email delivery. This guide compares five Listmonk VPS hosting options and provides a production-minded Docker deployment for Ubuntu 24.04 LTS.
Checked November 18, 2026. Listmonk v6.2.0 is the latest verified stable release. v7.0.0-beta.2 is a prerelease, and nightly tracks changing code; neither is used below. Prices exclude tax and optional extras. No purchased-server benchmarks are claimed. The LightNode links are affiliate links; we may earn a commission at no additional cost to you.
What Is Listmonk?
Listmonk is an AGPLv3-licensed mailing-list and newsletter application. It manages subscribers and custom attributes, public or private lists, imports, opt-in flows, reusable templates, scheduled campaigns, analytics, media, an HTTP API, and transactional messages. Its bounce tools can scan a POP3 mailbox or accept supported provider webhooks, helping operators blocklist addresses after hard bounces and apply rules to soft bounces.
The application is narrower than a full customer-journey suite. It is strong at list management, segmentation, campaigns, and integrations, but it does not replace every CRM or multichannel automation workflow. It also requires PostgreSQL 12 or newer and an external SMTP relay.
Listmonk fits technical teams that value data control and can maintain Linux, Docker, PostgreSQL, DNS authentication, backups, and upgrades. A hosted service may be safer for an organization without that operational capacity.
Listmonk VPS Requirements
Listmonk does not publish these three use-case tiers as official minimums or benchmarks. They are conservative editorial starting points; measure your own database, imports, concurrent sends, and admin traffic.
| Use Case | CPU | RAM | SSD |
|---|---|---|---|
| Personal Newsletter | 1 vCPU | 2 GB | 20–40 GB |
| Small Business | 2 vCPU | 4 GB | 40–80 GB |
| Growing Newsletter | 4 vCPU | 8 GB | 80–160 GB+ |
The Listmonk binary is efficient, but it is only one part of the machine. PostgreSQL needs memory for connections, query work, indexes, and cache. Linux and Docker consume additional headroom. Subscriber attributes, campaign events, link tracking, bounce history, and database indexes make storage grow over time; attachments and locally stored media can dominate it. Image layers, logs, temporary imports, database dumps, and at least one safe upgrade copy also need free space.
Sending concurrency affects CPU, memory, database connections, and SMTP rate limits. It does not create a fixed “emails per VPS” capacity. Start below the relay's allowed rate, monitor errors, then tune.
Can Listmonk run with 1 GB or 2 GB RAM?
A 1 GB VPS can run a very small, carefully controlled installation, but PostgreSQL and the operating system leave little safety margin. Imports, upgrades, backups, or simultaneous campaign work can trigger swapping or an out-of-memory kill. Treat 1 GB as a test or hobby allocation, not the default recommendation.
Two GB is the practical starting point for a personal newsletter with modest activity, external SMTP, limited local media, and off-host backups. Choose 4 GB for a business list, larger imports, multiple administrators, or other containers. Move toward 8 GB when the database and campaign history are growing, sends overlap with imports or analytics, or monitoring shows sustained memory pressure. Subscriber count alone cannot determine RAM.
How Much Does Listmonk Hosting Cost?
Separate the bill into two categories. VPS infrastructure includes compute, SSD, a domain, HTTPS, backup storage, snapshots, monitoring, and the administrator's time. PostgreSQL can run in the same Compose stack without a separate license, but it still consumes resources and needs backups. Email delivery includes the SMTP relay, message volume, overages, possible dedicated-IP fees, and the work required for domain authentication and bounce processing.
| Scenario | Reference infrastructure | Verified VPS example | Other likely costs | Practical fit |
|---|---|---|---|---|
| Personal Newsletter | 1 vCPU, 2 GB, 20–40 GB | LightNode 2 GB: $7.71/month reference | Domain, off-host backup, SMTP usage | One modest, consent-based list |
| Small Business Newsletter | 2 vCPU, 4 GB, 40–80 GB | DigitalOcean 4 GB: $24/month | Backups plus paid relay volume | Regular campaigns and multiple admins |
| Growing Mailing List | 4 vCPU, 8 GB, 80–160 GB+ | DigitalOcean 8 GB: $48/month | Larger backups, relay volume, perhaps dedicated IP | Measured growth and concurrent operations |
These are planning examples, not complete mailing costs. Amazon SES, Mailgun, SendGrid, and Postmark use different subscriptions, included volumes, overage rules, and eligibility checks. Obtain a quote for your recipient volume and sending pattern. A cheap VPS can still have a large SMTP bill; a larger VPS does not improve inbox placement by itself.
Best VPS Providers for Listmonk in 2026
The table uses comparable 2 GB entry points where a dependable public quote was available. Inventory, location surcharges, taxes, backups, IPv4, and transfer can change the checkout total.
| Provider | CPU | RAM | Storage | Price | Best For | Visit Website |
|---|---|---|---|---|---|---|
| LightNode | 1 vCPU | 2 GB | 50 GB SSD | $7.71/month reference | Hourly billing and broad regions | Visit |
| DigitalOcean | 1 vCPU | 2 GiB | 50 GiB SSD | $12/month | Clear developer workflow | Visit |
| Vultr | 1 vCPU | 2 GB | 55 GB SSD | $10/month base | Regional choice | Visit |
| Akamai Cloud / Linode | 1 vCPU | 2 GB | 50 GB | $12/month base | Conventional Linux hosting | Visit |
| Hetzner | CPX12: 1 vCPU | 2 GB | 40 GB NVMe | Current quote required | Available EU capacity | Visit |
1. LightNode: Flexible Hourly Listmonk Hosting
LightNode recommendation
Recommended configuration: 2 vCPU, 4 GB RAM, 50 GB SSD, $13.70/month reference. A personal deployment can begin at 1 vCPU/2 GB for $7.71; 4 vCPU/8 GB is $26.70.
LightNode provides hourly-billed KVM Linux VPS instances, a static public IP, SSD plans, and locations across several continents. Root access and standard Linux images make Docker deployment straightforward. The company describes an infrastructure history beginning in 2002 and a VPS platform launched in 2020; these are company claims, not an independent longevity ranking.
Pros: Hourly billing is useful for evaluations, and the 50 GB entry storage is comfortable for a small database. Global locations include markets that some larger providers cover less densely. Cons: The current checkout price and available capacity must be confirmed, cryptocurrency payment was not verified as available, and the outbound SMTP-port policy could not be verified publicly. Best for: Operators who value hourly accounting and a nearby listed region. Ask support about ports 25, 465, 587, and 2525 before buying; do not assume unrestricted SMTP.
2. DigitalOcean: Clear Plans and Documentation

DigitalOcean recommendation
Recommended configuration: Basic Regular, 2 vCPU, 4 GiB RAM, 80 GiB SSD, $24/month. The 1 vCPU/2 GiB plan is $12/month.
DigitalOcean offers Linux Droplets, cloud firewalls, snapshots, APIs, and extensive tutorials. Pros: Predictable sizes and a familiar developer interface. Cons: Backups add cost, and DigitalOcean documents SMTP restrictions for new accounts; contact support or use a relay endpoint and port permitted for your account. Best for: Developers who value documentation and already use the platform. Never design a campaign around direct-to-recipient port 25 delivery.
3. Vultr: Broad Location Selection

Vultr recommendation
Recommended configuration: regular cloud compute vc2-2c-4gb, 2 vCPU, 4 GB RAM, 80 GB SSD, $20/month base. The 1 vCPU/2 GB plan is $10/month base.
Vultr supplies Linux instances in many regions with snapshots, firewalling, and API management. Pros: Region choice and a sensible 4 GB step. Cons: some locations carry a surcharge, and outbound SMTP can require account review or support approval. Best for: Teams choosing infrastructure close to their administrators or application users. Confirm the selected region's price and SMTP policy in writing.
4. Akamai Cloud / Linode: Familiar Linux Operations

Akamai Cloud recommendation
Recommended configuration: Linode 4 GB, 2 vCPU, 80 GB storage, $24/month base. Linode 2 GB is $12/month in base regions.
Linode instances provide standard Linux administration, Cloud Firewall, backups, and an API. Pros: Straightforward plan ladder and mature Linux documentation. Cons: regional pricing differs, backups are extra, and SMTP restrictions may apply to new accounts. Best for: Administrators who want a conventional VPS workflow. Use an authenticated relay and verify allowed ports before launch.
5. Hetzner: Quote Current Capacity

Hetzner recommendation
Recommended configuration: CPX22 or the closest currently available 4 GB shared-vCPU plan. Price: obtain a live order quote; the checked catalog did not expose a dependable purchasable price.
Hetzner Cloud offers Linux VMs, private networks, firewalls, snapshots, and hourly billing with a monthly cap. Pros: strong European infrastructure options and useful automation. Cons: inventory, IPv4 charges, currency, VAT, and 2026 price changes complicate old comparisons. Hetzner restricts SMTP ports for new accounts and may require an eligibility period or support process. Best for: cost-conscious operators who can obtain a current quote and satisfy account requirements.
How to Install Listmonk on an Ubuntu VPS
This tutorial targets Ubuntu 24.04 LTS, Docker Compose v2, Listmonk v6.2.0, and PostgreSQL 17. It adapts the official v6.2.0 Compose file but pins versions and binds the application to loopback. Replace every example domain and secret.
Step 1. Prepare an Ubuntu VPS
Create a normal sudo user through the provider console, use SSH keys, point listmonk.example.com to the server, then update and enable a firewall:
sudo apt update && sudo apt upgrade -y
sudo apt install -y ca-certificates curl ufw
sudo ufw allow OpenSSH
sudo ufw allow 80/tcp
sudo ufw allow 443/tcp
sudo ufw enableDo not open PostgreSQL 5432. Port 9000 will remain loopback-only.
Step 2. Install Docker Engine and Docker Compose
Use Docker's official Ubuntu repository:
sudo install -m 0755 -d /etc/apt/keyrings
sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.asc
sudo chmod a+r /etc/apt/keyrings/docker.asc
sudo tee /etc/apt/sources.list.d/docker.sources > /dev/null <<EOF_DOCKER
Types: deb
URIs: https://download.docker.com/linux/ubuntu
Suites: $(. /etc/os-release && echo "${UBUNTU_CODENAME:-$VERSION_CODENAME}")
Components: stable
Architectures: $(dpkg --print-architecture)
Signed-By: /etc/apt/keyrings/docker.asc
EOF_DOCKER
sudo apt update
sudo apt install -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
sudo docker run --rm hello-world
sudo docker compose versionStep 3. Create the Listmonk Project Directory
sudo install -d -m 0750 -o "$USER" -g "$USER" /opt/listmonk
cd /opt/listmonk
umask 077Step 4. Prepare Docker Compose Configuration
Generate secrets with openssl rand -base64 32, then create .env:
POSTGRES_PASSWORD=REPLACE_WITH_A_LONG_RANDOM_PASSWORD
LISTMONK_ADMIN_USER=admin
LISTMONK_ADMIN_PASSWORD=REPLACE_WITH_ANOTHER_LONG_RANDOM_PASSWORDCreate compose.yaml:
services:
db:
image: postgres:17-alpine
restart: unless-stopped
environment:
POSTGRES_USER: listmonk
POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
POSTGRES_DB: listmonk
healthcheck:
test: ["CMD-SHELL", "pg_isready -U listmonk -d listmonk"]
interval: 10s
timeout: 5s
retries: 6
volumes:
- listmonk_db:/var/lib/postgresql/data
app:
image: listmonk/listmonk:v6.2.0
restart: unless-stopped
depends_on:
db:
condition: service_healthy
ports:
- "127.0.0.1:9000:9000"
environment:
LISTMONK_app__address: 0.0.0.0:9000
LISTMONK_db__host: db
LISTMONK_db__port: 5432
LISTMONK_db__user: listmonk
LISTMONK_db__password: ${POSTGRES_PASSWORD}
LISTMONK_db__database: listmonk
LISTMONK_db__ssl_mode: disable
LISTMONK_ADMIN_USER: ${LISTMONK_ADMIN_USER}
LISTMONK_ADMIN_PASSWORD: ${LISTMONK_ADMIN_PASSWORD}
command: ["sh", "-c", "./listmonk --install --idempotent --yes --config '' && ./listmonk --upgrade --yes --config '' && ./listmonk --config ''"]
volumes:
listmonk_db:The named volume persists PostgreSQL data. The database has no published host port. v6.2.0 avoids silently adopting beta or nightly code; review releases before changing it. Protect .env with chmod 600 .env.
Step 5. Configure PostgreSQL
The official requirement is PostgreSQL 12 or newer. This stack uses PostgreSQL 17 and a health check. Validate the rendered configuration without printing .env elsewhere:
chmod 600 .env
sudo docker compose config --quietStep 6. Initialize and Start Listmonk
The pinned official startup pattern performs an idempotent install, applies migrations, and starts the app:
sudo docker compose pull
sudo docker compose up -d
sudo docker compose ps
sudo docker compose logs --tail=100 app dbCheck locally with curl -I http://127.0.0.1:9000. A database authentication error usually means .env, the existing volume, and Compose no longer agree; do not delete the volume to hide the problem.
Step 7. Create the Administrator Account
The environment variables bootstrap the super administrator on first installation. Sign in through a private SSH tunnel until HTTPS is ready:
ssh -N -L 9000:127.0.0.1:9000 ubuntu@YOUR_SERVER_IPOpen http://127.0.0.1:9000, verify the account, store the password in a manager, and remove the two admin bootstrap variables from .env after confirming access.
Step 8. Configure SMTP
In Settings → SMTP, enter the relay host, port, username, password, authentication method, and sender address supplied by Amazon SES, Mailgun, SendGrid, Postmark, or another provider. Use TLS/STARTTLS exactly as documented—commonly STARTTLS on 587 or implicit TLS on 465—and send a test.
The From domain must be authorized by the provider. A VPS host may block outbound SMTP even when the relay account is valid; verify ports 25, 465, 587, and 2525 before deployment. Never disable certificate verification to work around a hostname or TLS error.
Step 9. Configure SPF, DKIM, and DMARC
Publish the exact SPF include and DKIM records generated by the SMTP provider. Add a DMARC record in monitoring mode, review reports, and strengthen policy only after legitimate sources align. Avoid multiple SPF TXT records for the same hostname. DNS authentication proves authorization and alignment; it does not guarantee Gmail or Outlook inbox placement.
Step 10. Create a Mailing List and Test a Campaign
Create a list, choose the appropriate opt-in mode, and import only recipients who consented. Build a template with a visible identity, postal details where legally required, and Listmonk's unsubscribe link. Send first to authorized test addresses across several mailbox providers, check rendering and headers, then begin with a controlled segment.
Step 11. Configure Bounce Processing
Listmonk supports a dedicated POP3 bounce mailbox and webhook processing for supported services, including Amazon SES. Follow the official bounce guide for the chosen relay. Map hard bounces, repeated soft bounces, and complaints into suitable blocklisting rules. Protect webhook endpoints with the provider's verification mechanism and test with documented events rather than fabricated addresses.
Step 12. Configure HTTPS and a Reverse Proxy
Install Caddy, keep 9000 on loopback, and create /etc/caddy/Caddyfile:
listmonk.example.com {
reverse_proxy 127.0.0.1:9000
encode zstd gzip
}Run sudo systemctl reload caddy after validation. Caddy obtains certificates when DNS, ports 80/443, and the domain are correct. Consider IP or identity-aware restrictions for the admin area without breaking public subscription endpoints.
Step 13. Back Up Listmonk
Create a consistent logical database backup and copy it off the VPS:
mkdir -p backups
sudo docker compose exec -T db pg_dump -U listmonk -d listmonk -Fc > backups/listmonk-$(date +%F).dumpAlso back up compose.yaml, securely escrow .env, and copy any external media directory or object-storage configuration. Encrypt backup storage, define retention, and regularly restore a dump into a separate PostgreSQL instance. A snapshot is useful, but it is not a tested database restore.
Step 14. Update Listmonk Safely
Read the stable release notes, take and verify a backup, change the image to a reviewed stable version, then run the documented migration:
sudo docker compose pull app
sudo docker compose run --rm app ./listmonk --upgrade --yes --config ''
sudo docker compose up -d
sudo docker compose logs --tail=100 appVerify login, lists, a test SMTP message, unsubscribe, and bounce processing. Keep the prior image reference and restore plan until checks pass. Never use docker compose down -v for a normal upgrade; -v deletes the database volume.
Listmonk SMTP and Email Deliverability
Deliverability depends primarily on the SMTP provider's reputation, your sending domain and history, recipient consent, engagement, bounce and complaint rates, authentication alignment, content, and consistent list hygiene. The relay's sending limits and Listmonk's concurrency should be aligned so temporary rejections are handled rather than amplified.
Use confirmed opt-in where appropriate, make unsubscribe immediate and obvious, suppress hard bounces and complaints, remove persistently inactive or invalid addresses, and warm a legitimate new domain gradually. Monitor DMARC reports and relay dashboards. Do not purchase lists or attempt to bypass spam controls.
A faster 8 GB VPS may prepare campaigns more quickly, but it does not grant a trusted IP or domain. For most self-hosters, a reputable authenticated SMTP relay with provider-managed delivery infrastructure is safer than operating a direct-to-MX mail server from a new VPS address.
Listmonk vs Mailchimp vs Mautic
| Area | Listmonk | Mailchimp | Mautic |
|---|---|---|---|
| Hosting model | Self-hosted application | Vendor-hosted SaaS | Self-hosted or partner-hosted |
| Self-hosting | Yes | No | Yes |
| Newsletter management | Strong list, template, campaign, and analytics tools | Full hosted campaign workflow | Campaigns within a broader automation suite |
| Marketing automation | Limited compared with full suites | Built-in journeys vary by plan | Extensive segments, campaigns, scoring, and plugins |
| SMTP requirement | External SMTP required | Delivery included within plan limits | External transport commonly required |
| Maintenance | You maintain app, PostgreSQL, security, and backups | Vendor maintains platform | You maintain a larger PHP/database stack when self-hosted |
| Pricing model | Free AGPL software plus VPS and delivery | Contact/send/features subscription | Free software plus infrastructure, delivery, and operations |
| Best for | Technical newsletter operators prioritizing control | Teams wanting managed convenience | Teams needing self-hosted marketing automation |
Mailchimp pricing and features change by plan, while self-hosting costs depend on labor and delivery volume. Listmonk wins on simplicity for many newsletter workloads, not on every automation feature.
Common Listmonk Hosting Problems
| Problem | Likely cause and safe checks |
|---|---|
| Container not starting | Run docker compose ps and logs; validate YAML, image architecture, disk space, and permissions. Fix the reported cause rather than recreating volumes. |
| PostgreSQL connection failed | Confirm db hostname, credentials, health status, and that an old volume was initialized with a different password. Keep 5432 internal. |
| Port 9000 already in use | Check `sudo ss -ltnp |
| SMTP authentication failed | Recheck relay username, password/API credential, authorized sender, account status, and TLS mode. Rotate exposed credentials. |
| SMTP timeout | Test DNS and TCP reachability; ask both providers about outbound restrictions and use an officially supported relay port. |
| Emails going to spam | Inspect authentication results, complaints, bounces, consent, content, domain history, and relay reputation. More VPS RAM is not a remedy. |
| SPF/DKIM errors | Compare live DNS with the relay's exact records, remove duplicate SPF policies, wait for TTL, and verify From/Return-Path alignment. |
| Bounce processing failure | Check POP3 credentials or webhook verification, provider event delivery logs, Listmonk rules, and time synchronization. |
| Reverse proxy 502 | Confirm the app is healthy on 127.0.0.1:9000, then check proxy target, logs, firewall, and container restarts. |
| Missing data after recreation | The wrong or missing volume was mounted. Stop writes, identify volumes with docker volume ls/inspect, and restore a verified backup; do not initialize over evidence. |
For adjacent self-hosting choices, see our guides to NocoDB, Appwrite, Coolify, Dokploy, and Beszel.
Frequently Asked Questions
What is the best VPS for Listmonk?
Choose a reliable Linux VPS with persistent SSD storage, backups, and a clear SMTP policy. LightNode suits hourly regional deployments; DigitalOcean and Linode emphasize documented workflows; Vultr offers broad location choice; Hetzner is worth a current European quote.
How much RAM does Listmonk need?
Use 2 GB for a modest personal deployment, 4 GB for a small business starting point, and consider 8 GB when measured database, import, and concurrent work justify it. These are editorial recommendations, not official benchmarks.
Can Listmonk run on a 1GB VPS?
Yes, for testing or a very small workload, but PostgreSQL, Docker, and Linux leave little headroom. Two GB is a safer practical baseline.
Is Listmonk free and open source?
Yes. Listmonk is licensed under AGPLv3. You still pay for infrastructure, SMTP delivery, backups, domains, and administration.
Does Listmonk require PostgreSQL?
Yes. Current official documentation requires PostgreSQL 12 or newer.
Does Listmonk include an SMTP server?
No. It connects to an external SMTP service to deliver messages.
How much does Listmonk hosting cost?
A small VPS can begin around $8–$12 monthly, while typical 4 GB examples are $20–$24. Add domain, backup, SMTP volume, optional dedicated IP, and operational labor.
Can Listmonk send 100,000 emails?
Listmonk can manage large campaigns, but no fixed capacity should be promised. The SMTP provider's approval, rate limits, recipient consent, database size, concurrency, and reputation determine whether a 100,000-message campaign is responsible and feasible.
Is Listmonk better than Mailchimp?
It is better for some technical teams seeking self-hosting and control. Mailchimp is easier for teams that prefer a managed service and its integrated feature set.
How do I back up Listmonk?
Take consistent PostgreSQL dumps, save Compose and configuration securely, copy media, store backups off-host, and test restoration into a separate environment.
Final Verdict
For a personal newsletter, start with 2 GB and external SMTP; LightNode's hourly 2 GB option is flexible where its location and SMTP policy fit. A small business should favor 4 GB, tested backups, monitoring, and a reputable relay—DigitalOcean, Vultr, or Linode are clear candidates. Developers may prefer DigitalOcean or Linode documentation and APIs.
For a budget deployment, compare LightNode and a live Hetzner quote after including IPv4, backups, tax, and regional pricing. A growing mailing list should move to 8 GB only when metrics justify it and should prioritize database maintenance, off-host recovery, consent, bounce controls, and relay reputation over raw VPS size.
