Zulip's official RAM guidance rises from 4 GB at 25+ DAU to 8 GB at 100+ DAU and much more beyond that.
Growing organizations.Zulip Hardware Requirements: RAM, CPU, PostgreSQL & Storage
Plan Zulip hardware using its official 2 GB RAM baseline, plus CPU, PostgreSQL, swap, storage and active-user scaling for ZimaOS deployments.
Zulip requirements at a glance
Zulip publishes clear small-server and active-user scaling guidance, and strongly prefers a dedicated machine, VM or Docker environment.
- Small deployment
- For fewer than 100 users, official guidance says 1 CPU and 2 GB RAM are sufficient, with 2 GB swap when the machine has under 5 GB RAM.
- 100+ users
- Official minimum: 2 CPUs and 4 GB RAM.
- Disk
- At least 10 GB dedicated free space; Zulip notes this is roughly a 25 GB total disk after OS requirements.
- Larger active-user guidance
- 25+ daily active users: 4 GB RAM; 100+ DAU: 8 GB; 400+ DAU: 16 GB app server plus 16 GB database.
- Storage/database
- PostgreSQL is part of the standard stack and SSD storage is strongly recommended for the database.
- Best Zima starting point
- ZimaBoard 2 832 can fit a small Zulip deployment; ZimaBoard 2 1664 is the safer choice for 100+ active-user growth, while very large Zulip should split the database.
From official requirements to the right setup
Use Zulip's official user-count tiers and keep swap/database guidance intact.
-
Official requirements
For fewer than 100 users, allocate 1 CPU, 2 GB RAM and 2 GB swap on low-memory systems; for 100+ users, use at least 2 CPUs and 4 GB RAM.
-
Confirm your needs
Provide at least 10 GB dedicated free disk and prefer SSD-backed storage because the database drives much of the I/O.
-
Leave room to grow
As daily active users grow, follow Zulip's memory scaling guidance and move PostgreSQL to a dedicated server when hundreds of daily active users are expected.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App only with the Docker deployment path and enough reserved resources; for production, a dedicated VM/host aligns better with Zulip's upstream guidance.
Check every playback client
- Expected users
- Daily active users
- 2 GB+ RAM
- Swap configuration
- PostgreSQL storage
- 10 GB+ free disk
- HTTPS/domain
- Email credentials
Official minimum requirements
Zulip 12.1 publishes explicit server and scalability guidance.
The 2 GB figure is a real small-server baseline, but larger deployments scale RAM aggressively with daily active users and may require a separate PostgreSQL host.
| Requirement | Official minimum | What this supports |
|---|---|---|
| <100 users | 1 CPU / 2 GB RAM | 2 GB swap recommended when system RAM is below 5 GB. |
| 100+ users | 2 CPUs / 4 GB RAM minimum | Current official baseline. |
| Disk free space | 10 GB dedicated free space | Approximately 25 GB total disk including OS needs. |
| 25+ daily active users | 4 GB RAM | Current scaling guidance. |
| 100+ daily active users | 8 GB RAM | Current scaling guidance. |
| 400+ daily active users | 16 GB app + 16 GB DB | Separate database recommended at this scale. |
| Architecture | x86-64 or aarch64 | Current supported CPU architectures. |
When to upgrade your hardware
Zulip should scale when daily active users, message history or uploaded files increase.
Daily active users reach larger tiers
PostgreSQL history grows
File uploads grow
Message history and public-channel fanout can increase database RAM and SSD requirements substantially.
Long-running chat servers.At scale, Zulip recommends an S3-style upload backend rather than relying only on local disk.
File-heavy teams.Plan hardware growth with confidence
Scale Zulip around memory, PostgreSQL and dedicated-host isolation.
Use ZimaBoard 2 832 for small Zulip deployments
8 GB is well above the official 2 GB small-server baseline.
ZimaBoard 2 832.Use 16 GB for larger single-host deployments
This provides more room for PostgreSQL, queue workers and 100+ active-user growth.
ZimaBoard 2 1664.Use SSD-backed PostgreSQL
Zulip explicitly recommends SSD storage for the database.
Use SATA/NVMe with ZimaBoard 2 or SSD tiers on ZimaCube 2.Split database/app roles at higher scale
At around 400+ DAU, Zulip's guidance allocates 16 GB each to app and DB, beyond a simple single-box profile.
Use multiple hosts/VMs rather than forcing the workload onto one device.Can it run on ZimaOS?
No public official ZimaOS one-click Zulip App Store detail page was verified for this guide. Zulip supports Docker, but upstream strongly recommends a dedicated machine, VM or fresh environment for production.
Custom install Zulip in the ZimaOS app
Use Install Custom App only with the Zulip Docker deployment and reserved resources; for production, a dedicated VM is closer to upstream guidance.
Custom install Zulip in the ZimaOS app ↗Follow Zulip's production requirements
Current docs define explicit RAM/CPU/disk baselines and strongly recommend a dedicated or fresh system.
Review Zulip requirements ↗Use Docker when direct installation is unsuitable
Zulip supports Docker as an alternative to direct Ubuntu/Debian installation.
Review Zulip self-hosting options ↗Choose Zima hardware for Zulip
Zulip's official small-server baseline fits ZimaBoard 2, but larger organizations should follow Zulip's multi-tier memory and database guidance.
Is this a small self-hosted Zulip or a larger active-user deployment?
Small / fewer than 100 users
Use ZimaBoard 2 832 with SSD-backed storage and swap configured if needed.
- Best starting pointZimaBoard 2 832
100+ active-user growth
Use 16 GB for more headroom, but split app/database roles once daily actives reach larger scales.
- More single-host headroomZimaBoard 2 1664
- Stronger VM/app hostZimaCube 2 Pro
These recommendations map official user-scale guidance to Zima hardware; they do not replace Zulip's recommendation for dedicated production infrastructure.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Small Zulip organizations. | Single-host Zulip with modest users and PostgreSQL. |
|
8 GB is above the small-server baseline, but production isolation is still recommended. | Get Now |
| ZimaBoard 2 1664 | Larger single-host Zulip deployments. | More users, PostgreSQL cache and queue-worker headroom. |
|
At larger DAU counts, Zulip recommends splitting database resources. | Get Now |
| ZimaCube 2 Pro | Stronger Zulip VM/app host. | More CPU, 16 GB RAM and broader storage/network services. |
|
16 GB alone is not enough for the 400+ DAU app+DB combined guidance. | 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 Zulip RAM, CPU, disk, PostgreSQL, swap and ZimaOS deployment.
How much RAM does Zulip need?
For fewer than 100 users, Zulip says 2 GB RAM is sufficient; for 100+ users, the official minimum is 4 GB.
How many CPU cores does Zulip need?
Small deployments can use 1 CPU; 100+ users need at least 2 CPUs.
How much disk does Zulip need?
Zulip requires at least 10 GB dedicated free space, roughly a 25 GB total disk including OS requirements.
Does Zulip need swap?
If the server has less than 5 GB RAM, Zulip requires swap and recommends 2 GB.
How much RAM is recommended for 100+ daily active users?
Zulip's current scaling guidance recommends 8 GB RAM at 100+ daily active users.
Does Zulip need a GPU?
No dedicated GPU is required.
Can ZimaBoard 2 run Zulip?
Yes. The 8 GB model can handle a small deployment; the 16 GB model offers more room for larger single-host use.
When should PostgreSQL move to a separate server?
Zulip recommends a remote PostgreSQL database for installations with hundreds of daily active users.
What sources informed this Zulip hardware guide?
Current Zulip 12.1 requirements and self-hosting documentation plus current Zima product pages.
