Increasing batch size improves throughput but explicitly increases memory usage.
Large newsletter lists.listmonkのハードウェア要件：RAM、CPU、PostgreSQL、ストレージ
RAM、CPU、PostgreSQL、購読者リスト、キャンペーン処理量、アップロードを考慮し、実用的なZimaOSカスタムインストールのサイズを含むlistmonkハードウェア構成を計画します。
listmonk requirements at a glance
listmonk's application binary is compact, but a real deployment also needs PostgreSQL and enough memory for campaign batching and large subscriber lists.
- RAM
- No numerical official minimum published. Larger campaign batch sizes explicitly use more memory.
- CPU
- No numerical official core minimum. Campaign sending, templating and database work determine practical CPU use.
- Database
- PostgreSQL is required; current installation docs require PostgreSQL 12 or newer.
- Storage
- No universal official minimum. PostgreSQL data, uploaded media, logs and backups determine capacity.
- Docker
- Official image: listmonk/listmonk:latest; current Compose example pairs it with PostgreSQL.
- Best Zima starting point
- ZimaBoard 2 832 is a strong small-to-medium host; use 16 GB when subscriber lists, batching and other services grow.
From official requirements to the right setup
Size listmonk from subscriber volume, campaign batching and PostgreSQL rather than the single Go binary alone.
-
Official requirements
Start with the official Docker Compose stack or binary installation and a PostgreSQL 12+ database.
-
Confirm your needs
Estimate subscriber count and campaign batch size. Upstream notes that larger batch sizes increase memory use while reducing database round trips.
-
Leave room to grow
Persist PostgreSQL plus any uploads directory used for campaign media, and keep independent database backups.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App with the official listmonk image and PostgreSQL, map port 9000, and monitor database latency plus campaign memory use before scaling.
Check every playback client
- Subscriber count
- Campaign frequency
- Batch size
- PostgreSQL size
- Media uploads
- SMTP provider limits
- Backup retention
- Other ZimaOS services
Official minimum requirements
listmonk's current documentation defines PostgreSQL and deployment requirements but does not publish numerical host CPU, RAM or disk minimums.
Do not invent a 1 GB or 2 GB official minimum. Memory depends on subscriber/campaign batching, while PostgreSQL and media determine persistence requirements.
| Requirement | Official minimum | What this supports |
|---|---|---|
| RAM minimum | No numerical official minimum published | Campaign batch size can materially change memory use. |
| CPU minimum | No numerical official minimum published | Campaigns, templates and database activity drive load. |
| Database | PostgreSQL 12+ | Current installation requirement. |
| Storage minimum | No numerical official minimum published | PostgreSQL, uploads and backups determine capacity. |
| Default web port | 9000 | Current official Docker/binary examples. |
| Official container | listmonk/listmonk:latest | Current official Docker image. |
When to upgrade your hardware
listmonk should scale when campaign throughput, subscriber volume or PostgreSQL activity becomes the bottleneck.
Campaign batches consume more memory
PostgreSQL grows or becomes I/O-bound
Uploads and logs grow
Subscriber history, campaigns and analytics increase database size and query activity.
Long-running high-volume installations.Campaign media and retained logs/backups can become the main disk driver.
Media-heavy newsletters and long retention.Plan hardware growth with confidence
Scale listmonk around PostgreSQL responsiveness and campaign memory before adding unnecessary hardware.
Use SSD-backed PostgreSQL storage
Campaign queries and list operations benefit from low-latency durable storage.
Use SATA/NVMe with ZimaBoard 2 or SSD tiers on ZimaCube 2.Use 8 GB for small-to-medium deployments
Provides generous whole-host room for listmonk plus PostgreSQL.
ZimaBoard 2 832.Move to 16 GB for large lists or larger batches
Extra RAM helps PostgreSQL cache and campaign batching coexist with other apps.
ZimaBoard 2 1664.Use stronger storage/networking for very large workflows
Large subscriber databases and media assets can justify a broader platform.
ZimaCube 2 Pro.Can it run on ZimaOS?
listmonk is not currently confirmed as a public official one-click ZimaOS App Store page in the sources checked for this guide. It can be deployed through Install Custom App using listmonk's official Docker image.
Custom install listmonk in ZimaOS
Use Install Custom App with listmonk/listmonk plus PostgreSQL, persist the database and uploads, and map container port 9000 to an available host port.
Custom install listmonk in the ZimaOS app ↗Use listmonk's official Compose stack
The current repository provides a Compose file with listmonk and PostgreSQL plus persistent uploads/database storage.
Review listmonk Docker installation ↗Tune campaign batching carefully
Upstream documents that larger campaign batch sizes use more memory while reducing database round trips.
Review listmonk performance settings ↗Choose Zima hardware for listmonk
listmonk itself is efficient; PostgreSQL, campaign batch size and subscriber volume determine the meaningful hardware tier.
Is this a small newsletter server or a larger campaign/database workload?
Small or medium lists
Use ZimaBoard 2 with SSD-backed PostgreSQL.
- Best starting pointZimaBoard 2 832
- More campaign headroomZimaBoard 2 1664
Large database / broader marketing stack
Use stronger storage/networking and more system headroom.
- Higher-headroom platformZimaCube 2 Pro
These are workload recommendations, not official subscriber-count or mail-throughput guarantees.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Small and medium listmonk deployments. | listmonk, PostgreSQL, normal campaigns and uploads. |
|
Add SSD-backed PostgreSQL storage; campaign batch size changes memory use. | Get Now |
| ZimaBoard 2 1664 | Larger subscriber lists and campaign batches. | More PostgreSQL cache, batching and co-hosted marketing services. |
|
16 GB is practical headroom, not an official listmonk minimum. | Get Now |
| ZimaCube 2 Pro | Larger listmonk plus broader data/service consolidation. | Large PostgreSQL data, media, backups and other services. |
|
SMTP-provider limits and network reputation may matter more than local CPU at high send volumes. | Get Now |
What the Press Says
Highlights from trusted reviewers worldwide.
“ZimaCube 2: Not just another NAS, tested with 25TB storage, local AI agents, 4K transcoding, and real homelab workflows.”Read full review
“The ZimaBoard 2 is a compact x86 server board that can be turned into a mini NAS, home server, media box, or self-hosting hub.”Read full review
“ZimaCube 2: A modern, high-performance NAS with plenty of room to grow—built for users who want more than basic storage.”Read full review
“Coverage focused on ZimaCube 2's open hardware foundation, no monthly fee, and self-hosting flexibility.”Read full review
Loved by the Community
Stories and reviews from people who build with Zima every day.
★★★★★
Zima Blade Little yet Powerful
Maybe I am not digital natives but I live with PCs since 12 years old in 1984 when IBM PC clone come to my home. Many years have passed and many operating system I've tried. For me Zima blade and CasaOS was a quantum leap for home PC enthusiast and server lab machine to make me stay curious and relevant for this era.
★★★★★
Very good!!
I use ZimaCube Pro as 5th Proxmox cluster node. It runs several VMs and containers, including a VM with GPU passthrough to run a self-hosted LLM. A specific LXC container runs a Samba server for NAS capabilities using four of six RAID 6 SATA HDDs with ZFS.
★★★★★
Great innovation for mini server!
It is very useful and makes a powerful mini server for many purposes, including university and college students in engineering and electronics. Thank you so much for making this server.
★★★★★
Avaliação ZimaBoard 2
Construí um servidor de uso pessoal. O desempenho está muito bom e funciona perfeitamente onde quer que eu esteja. A surpresa é não dependermos de grandes estruturas para termos nosso próprio servidor de dados. Como iniciante, estou gostando bastante do ZimaOS, pois ele é simples e eficiente.
Frequently asked questions
These answers cover listmonk RAM, CPU, PostgreSQL, campaign batching, Docker and ZimaOS deployment.
How much RAM does listmonk need?
listmonk does not publish a numerical official server RAM minimum.
How many CPU cores does listmonk need?
No numerical official core minimum is published.
Which database does listmonk require?
listmonk requires PostgreSQL; current installation docs require PostgreSQL 12 or newer.
Does campaign batch size affect RAM?
Yes. Upstream states that increasing batch size uses more memory while reducing database round trips.
How much storage does listmonk need?
No universal minimum is published; PostgreSQL data, uploads, logs and backups determine capacity.
Does listmonk need a GPU?
No dedicated GPU is required.
Can ZimaBoard 2 run listmonk?
Yes. The 8 GB model is a strong small-to-medium host when paired with suitable PostgreSQL storage.
Does listmonk have an official Docker image?
Yes. The official image is listmonk/listmonk:latest.
What sources informed this listmonk hardware guide?
The guide uses listmonk's current installation/configuration documentation and current Zima product pages.
