Docmost's real-time editor relies on WebSockets, so active collaboration creates a different workload from occasional personal note viewing.
Teams editing shared documentation concurrently.متطلبات أجهزة Docmost: ذاكرة الوصول العشوائي ووحدة المعالجة المركزية وPostgreSQL وRedis
تعرّف على متطلبات Docmost من حيث وحدة المعالجة المركزية وذاكرة RAM وPostgreSQL وRedis والتخزين والتعاون الفوري، ثم اختر أجهزة ZimaOS المناسبة.
Docmost requirements at a glance
Docmost does not publish a numerical CPU or RAM minimum. Its current recommended Docker Compose stack runs three persistent services: Docmost, PostgreSQL 18 and Redis 8. The real-time editor depends on WebSockets, and file attachments use local storage by default with optional S3 or Azure Blob Storage.
- CPU
- No numerical official minimum. Normal wiki editing is light; simultaneous collaboration, imports, exports and larger database work raise CPU demand.
- RAM
- No numerical official minimum. Size the full stack—Docmost, PostgreSQL and Redis—not the app container alone.
- Database
- Current official Compose uses PostgreSQL 18.
- Redis
- Current official Compose uses Redis 8 with AOF persistence and noeviction policy.
- Storage
- Local file storage is the default; S3 and Azure Blob Storage are optional. Attachments/imports can dominate disk usage.
- Best Zima starting point
- ZimaBoard 2 832 is a strong small-team Docmost host. ZimaBoard 2 1664 or ZimaCube is more useful when the workspace grows, attachments accumulate or Docmost shares the server with more applications.
From official requirements to the right setup
Docmost sizing starts with the full collaboration stack and stored workspace data.
-
Official requirements
Account for Docmost, PostgreSQL and Redis together. The current official Compose deploys all three services.
-
Confirm your needs
Estimate workspace size, active editors and attachment volume. Real-time editing depends on WebSockets, while page/file data creates database and storage growth.
-
Leave room to grow
Choose local, S3 or Azure Blob Storage for files based on attachment size, backup model and long-term capacity.
-
Run it on ZimaOS
Install Docmost from ZimaOS, create representative spaces/pages/attachments and monitor PostgreSQL, Redis, WebSocket activity and storage before upgrading.
Check every playback client
- Workspace/page count
- Concurrent editors
- PostgreSQL
- Redis
- WebSocket reverse proxy
- Attachment/import volume
- Local vs object storage
- Database/file backups
Official minimum requirements
Docmost's current installation docs require Docker for the recommended path but do not publish a universal host CPU/RAM minimum.
Do not manufacture a one-container RAM figure. Docmost's official deployment is an app + PostgreSQL + Redis stack.
| Requirement | Official minimum | What this supports |
|---|---|---|
| CPU | No numerical minimum published | Concurrency and database workload determine practical demand. |
| RAM | No numerical minimum published | Full-stack memory includes Docmost, PostgreSQL and Redis. |
| Database | PostgreSQL 18 | Current official Compose image. |
| Redis | Redis 8 | Current official Compose image with AOF/noeviction. |
| App port | 3000 | Current default Compose mapping. |
| GPU | Not required | Core collaboration and database workloads are CPU/RAM/storage oriented. |
When to upgrade your hardware
Upgrade Docmost when database, concurrency or storage—not simple page viewing—becomes constrained.
More simultaneous editors increase database/WebSocket activity
PostgreSQL and Redis compete with other services for RAM
Attachments and imports grow rapidly
The official stack keeps persistent PostgreSQL and Redis services alongside Docmost, so shared hosts need headroom for all three.
Multi-container ZimaOS servers.Large files, images and content imports can make storage capacity and backup time the main scaling concern.
Documentation teams with media-heavy spaces.Plan hardware growth with confidence
Scale Docmost by separating database/cache and file-storage concerns where appropriate.
Keep PostgreSQL on responsive local storage
Page metadata, collaboration state and application data live in PostgreSQL, so low-latency persistent storage helps as workspaces grow.
Use SSD/NVMe for database/appdata.Keep Redis persistent and avoid eviction surprises
Current official Compose enables AOF and noeviction, so give Redis enough memory for the actual workload instead of relying on cache eviction.
Monitor Redis memory as team usage grows.Move file storage to S3 or Azure Blob when local capacity is limiting
Docmost officially supports local, S3 and Azure Blob storage backends.
Useful for large attachment-heavy workspaces.Use a reverse proxy with WebSocket support
Official docs explicitly require WebSocket support for the real-time editor.
This is a deployment requirement rather than a reason to buy more CPU.Can it run on ZimaOS?
Docmost is currently available in the ZimaOS App Store under Productivity.
Install Docmost from ZimaOS
Use the packaged collaborative wiki/documentation platform and keep app/database/cache data persistent.
Open Docmost in the ZimaOS App StoreAccount for PostgreSQL and Redis
Current official Compose deploys PostgreSQL 18 and Redis 8 with Docmost.
Read Docmost installationPreserve WebSocket support and choose a storage backend
Official docs require WebSockets for real-time editing and support local/S3/Azure file storage.
Read Docmost self-hosting configurationChoose Zima hardware for Docmost
Docmost itself is not a heavy compute app, but the full collaboration stack includes PostgreSQL, Redis and persistent file storage.
Personal/small-team wiki or larger collaboration/storage workspace?
Personal or small team
ZimaBoard 2 832 provides ample headroom for Docmost, PostgreSQL and Redis.
- Normal Docmost serverZimaBoard 2 832
- More users/apps headroomZimaBoard 2 1664
Large attachment-heavy workspace
Use ZimaCube when multi-drive storage and broader app/database workloads justify it.
- Integrated collaboration/storage serverZimaCube 2 Standard
- Larger app/database stackZimaCube 2 Pro
No fixed users, pages or attachments-per-server guarantee is implied.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Personal/small-team Docmost. | Docmost + PostgreSQL + Redis with normal collaboration. |
|
Large attachment/database growth may justify more storage. | Get Now |
| ZimaBoard 2 1664 | Larger team or broader productivity stack. | More database/cache and container headroom. |
|
Storage may still be the main long-term limit. | Get Now |
| ZimaCube 2 Standard | Attachment-heavy Docmost workspace. | Docmost plus multi-drive files and backups. |
|
Choose mainly for storage consolidation. | Get Now |
| ZimaCube 2 Pro | Larger collaboration/database/application platform. | More CPU/RAM and multi-drive storage. |
|
Not required for normal Docmost alone. | 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
FAQ topics cover RAM, PostgreSQL, Redis, WebSockets, storage and small-team sizing.
How much RAM does Docmost need?
Docmost does not publish a host RAM minimum. Size the full Docmost + PostgreSQL + Redis stack.
Does Docmost require PostgreSQL?
Yes in the current official Docker Compose deployment; the current template uses PostgreSQL 18.
Does Docmost require Redis?
Yes in the current official Compose; Redis 8 is configured with AOF persistence and noeviction.
Why does my reverse proxy need WebSocket support?
Docmost's real-time page editor depends on WebSocket connections.
Can Docmost use S3 storage?
Yes. Current docs support local storage by default plus S3 and Azure Blob Storage.
Does Docmost need a GPU?
No for the core app. The normal workload is collaboration, database/cache and file storage.
Can ZimaBoard 2 832 run Docmost?
Yes for personal and small-team use with the standard PostgreSQL/Redis stack.
When is ZimaCube 2 useful?
When attachments, imports, backups and other apps make multi-drive storage the main requirement.
What sources and further reading informed this Docmost hardware guide?
Current Docmost installation, Compose and reverse-proxy documentation define the PostgreSQL 18, Redis 8, file-storage and WebSocket architecture; ZimaOS confirms the current app.
