Persistent chat data includes more than text. Images/files and backup copies can become the dominant capacity requirement over time.
For active family/community servers that exchange and retain many files.Wymagania sprzętowe VoceChat: pamięć RAM, procesor, pamięć masowa i liczba użytkowników
Poznaj wymagania sprzętowe VoceChat dotyczące pamięci RAM, procesora, pamięci masowej, Dockera, Raspberry Pi, liczby użytkowników, plików oraz sprzętu ZimaOS.
VoceChat hardware requirements at a glance
VoceChat is a compiled self-hosted chat server designed to run on ordinary servers, NAS devices and Raspberry Pi-class hardware. Current official documentation does not publish one universal CPU, RAM or disk minimum.
- CPU
- No universal official CPU minimum is published. Official shell-install guidance explicitly says VoceChat works well on Raspberry Pi and NAS devices, showing that the server is intended to be lightweight.
- RAM
- No universal official RAM minimum is published. The current ZimaOS VoceChat package sets only a 64 MB memory reservation and no matching hard limit. This is package scheduling/resource metadata, not proof that every real deployment needs only 64 MB.
- Storage
- VoceChat persists server data under /home/vocechat-server/data. Text chat is small, but images, files, logs and backups can dominate capacity. Official Docker examples mount the data directory for persistent deployments.
- Architecture
- Official shell installation supports Linux x86_64, Arm32 and Aarch64. Official Docker docs provide amd64 and arm64 image paths. The current ZimaOS package, however, is specifically marked amd64.
- Users and licensing
- VoceChat's current FAQ says the free community tier is limited to no more than 20 members; larger servers require a license. That is a licensing boundary, not a hardware concurrency benchmark.
- Best Zima starting point
- ZimaBoard 2 832 is already a very large hardware margin for a private VoceChat server. Upgrade primarily for a larger attachment archive, more co-hosted apps or broader NAS workloads.
From official requirements to the right setup
VoceChat sizing starts with its lightweight server process, then adds member count, message/file retention, persistent data, Internet access and the other ZimaOS applications sharing the host.
-
Official requirements
Do not invent a numeric RAM floor from third-party Compose settings. Official docs say VoceChat works well on Raspberry Pi/NAS and support low-end Linux architectures, but do not publish a universal CPU/RAM minimum.
-
Confirm your needs
Plan persistent storage for /home/vocechat-server/data. Text messages are compact, while uploaded images/files and backup retention become the main long-term storage variables.
-
Leave room to grow
Separate licensing from hardware. The free tier's 20-member ceiling is a product/license rule; it does not mean 21 users suddenly require more RAM or CPU.
-
Run it on ZimaOS
Install the current ZimaOS amd64 package, test real message/file activity and monitor memory, CPU, disk and Internet upload. Upgrade the host only when measured workload or other services require it.
Check every playback client
- Number of registered members and concurrent active clients
- Free community tier versus licensed larger server
- Text-only use versus frequent image/file uploads
- Persistent /home/vocechat-server/data capacity
- Backup retention and restore requirements
- HTTPS/domain/reverse-proxy or built-in TLS deployment
- ZimaOS package architecture: current manifest is amd64
- Other ZimaOS containers sharing CPU, RAM and storage
Official minimum requirements
Current VoceChat documentation provides Docker and shell deployment paths and explicitly targets Raspberry Pi/NAS devices, but it does not publish a universal production CPU/RAM/disk requirements table.
The safe hardware conclusion is that VoceChat is intended for modest hardware, not that 64 MB, 6 GB or any other number is the official server minimum. Size real deployments from users, attachments, persistent data, backups and co-hosted services.
| Requirement | Official minimum | What this supports |
|---|---|---|
| CPU minimum | No universal official minimum published | Official shell documentation says the binary works well on Raspberry Pi and NAS devices without specifying one processor floor. |
| RAM minimum | No universal official minimum published | Official docs do not define a fixed whole-server memory floor. |
| Shell architectures | Linux x86_64, Arm32 and Aarch64 | These are explicitly listed by the current shell-install documentation. |
| Docker architectures | amd64 default; separate arm64 image path documented | Official Docker instructions distinguish the default amd64 image from the arm64 image. |
| ZimaOS memory reservation | 64 MB | The current ZimaOS v0.5.17 manifest reserves 64 MB but does not set a 64 MB hard limit. This is not an upstream minimum. |
| ZimaOS architecture | amd64 | The current ZimaOS manifest lists only amd64 even though upstream VoceChat supports additional architectures outside this package. |
When to upgrade your hardware
VoceChat hardware growth is driven mainly by retained files, a larger community and the other applications on the server.
Uploaded files and backups begin consuming significant storage
A larger licensed community increases active connections
Other services make the ZimaOS host memory- or CPU-bound
Moving beyond the free 20-member tier may increase simultaneous WebSocket/HTTP activity and storage writes, but the correct upgrade point must be measured rather than inferred from the license boundary itself.
For larger private communities and teams.VoceChat is lightweight, but media, AI, automation, databases and other containers can dominate the host. Upgrade based on total system pressure.
For consolidated all-in-one home servers.Plan hardware growth with confidence
VoceChat scales cleanly when persistent chat data, backups and the broader server stack are sized independently.
Keep VoceChat data on persistent SSD-backed storage
Official Docker guidance mounts /home/vocechat-server/data so server state survives container replacement. Back up this directory.
Use persistent SATA/NVMe AppData storage on ZimaBoard 2.Add storage for file-heavy communities
Text is small, but images and files can create sustained growth. Increase storage before replacing a perfectly adequate CPU.
Add SSD/HDD capacity as file retention grows.Use 16 GB only when the complete app stack needs it
VoceChat itself has no 16-GB requirement. More RAM is useful when databases, automation, media or many other apps share the machine.
Choose ZimaBoard 2 1664 for system-wide memory headroom.Move to ZimaCube 2 for NAS-scale storage
A six-bay platform is useful for a broader private cloud, backups and large file archives, not because the VoceChat server process needs a NAS-class CPU.
Choose ZimaCube 2 when multi-drive storage is independently justified.Can it run on ZimaOS?
VoceChat is currently listed in the ZimaOS App Store under Social. The package uses privoce/vocechat-server:v0.5.17 and currently targets amd64.
Install the current ZimaOS VoceChat app
The current manifest exposes the VoceChat WebUI from container port 3000 to host port 3009 and persists the server data directory.
Open VoceChat in the ZimaOS App StoreTreat 64 MB as a reservation, not a minimum or cap
The current ZimaOS manifest places memory: 64M under resource reservations and does not define a hard memory limit. Real usage can therefore exceed that reservation.
Review the ZimaOS VoceChat manifestBack up persistent VoceChat data
The current package maps /home/vocechat-server/data into ZimaOS AppData. Official VoceChat Docker documentation also uses this directory for persistence.
Read the official Docker installationChoose Zima hardware for your VoceChat workload
VoceChat is lightweight enough that ZimaBoard 2 832 is the default choice. Larger Zima hardware should follow file retention, co-hosted applications and broader NAS requirements.
Is VoceChat a small private community server, or one application inside a much larger storage/self-hosting platform?
Private family/small-community server
Start with ZimaBoard 2 832. Its Intel N150 and 8 GB RAM provide enormous headroom compared with the 64 MB ZimaOS reservation and Raspberry Pi/NAS class targeted upstream.
- VoceChat plus lightweight home appsZimaBoard 2 832
- Larger co-hosted Docker stackZimaBoard 2 1664
Large file archive or broader NAS/app platform
Choose ZimaCube 2 for the storage and wider workload. Pro is for heavier unrelated services; Creator Pack has no VoceChat-specific GPU advantage.
- Storage-first private community/NASZimaCube 2 Standard
- Heavier all-in-one app/NAS stackZimaCube 2 Pro
- Only when separate GPU/AI workloads require itZimaCube 2 Creator Pack
This is a workload guide, not a user-count benchmark. The official 20-member free-tier boundary is licensing, not a guaranteed capacity figure.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | The best-value current Zima option for a private VoceChat server and lightweight self-hosted stack. | VoceChat, reverse proxy, backups and several ordinary lightweight ZimaOS apps. |
|
Onboard eMMC can become a storage constraint if the community retains many uploaded files; add SSD/HDD storage as data grows. | Get Now |
| ZimaBoard 2 1664 | VoceChat with a larger collection of co-hosted services and databases. | VoceChat plus automation, databases, sync, monitoring and more always-on containers. |
|
Do not claim VoceChat requires 16 GB. | Get Now |
| ZimaCube 2 Standard | A storage-first private community server with a larger file archive and backups. | VoceChat, multi-drive storage, backups and moderate family/home-server services. |
|
Choose Standard for storage needs, not because VoceChat requires an i3-class host. | Get Now |
| ZimaCube 2 Pro | A larger all-in-one NAS/app server where VoceChat is one service among many. | VoceChat plus databases, backups, storage, media and many other containers. |
|
Pro is unnecessary for VoceChat alone. | Get Now |
| ZimaCube 2 Creator Pack | A VoceChat server on hardware independently needed for GPU/AI/creator workloads. | VoceChat plus unrelated local AI, GPU compute or creator applications. |
|
Extreme overkill for VoceChat; never recommend it merely for more chat members or files. | 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
The supplied sources are broadly relevant, but numeric Compose limits and the 20-member free-tier rule must not be mistaken for hardware minimums.
How much RAM does VoceChat need?
VoceChat does not publish one universal RAM minimum. The current ZimaOS package reserves 64 MB but does not cap the container at 64 MB; actual usage depends on members, activity, files and the host environment.
Is 64 MB RAM enough for VoceChat?
The current ZimaOS manifest contains a 64 MB resource reservation, not a 64 MB hard limit or official upstream minimum. It is evidence that the package is expected to be lightweight, but it is not a safe whole-system sizing number.
Why does the Marius Hosting guide allocate 6 GB?
Its Synology Compose example sets mem_limit: 6g. That is a tutorial-specific container ceiling, not evidence that VoceChat consumes or requires 6 GB. It conflicts with upstream's explicit Raspberry Pi/NAS positioning and the much smaller ZimaOS reservation.
Can VoceChat run on Raspberry Pi?
Yes. Official shell documentation explicitly says VoceChat works well on devices such as Raspberry Pi and NAS, and supports x86_64, Arm32 and Aarch64 for direct binary installation.
Does the ZimaOS VoceChat package support ARM64?
Not in the current manifest. Upstream documents an arm64 Docker image and Aarch64 shell binary, but the current ZimaOS package specifically lists amd64. Keep upstream architecture support separate from package-level support.
Does VoceChat need a GPU?
No dedicated GPU requirement is published for the chat server. Text, images, files and normal messaging are CPU/storage/network workloads; Zima GPU hardware is unnecessary unless another application independently needs it.
Does 20 members mean the server only supports 20 users?
No. The current FAQ says the free community server is limited to no more than 20 members and that larger servers require a license. This is a license/tier rule, not a hardware-capacity statement.
Can ZimaBoard 2 832 run VoceChat?
Yes. The current ZimaOS package targets amd64, and ZimaBoard 2 832 provides an Intel N150 and 8 GB RAM. For a normal private chat server, storage and the rest of the app stack are more likely to determine future upgrades.
What sources and further reading informed this VoceChat hardware guide?
The official FAQ establishes the current free-tier limit of no more than 20 members but provides no CPU/RAM minimum. The official shell-install page says VoceChat works well on Raspberry Pi and NAS devices and supports Linux x86_64, Arm32 and Aarch64. Marius Hosting's Synology guide sets a 6 GB Docker mem_limit, which is treated only as that tutorial's ceiling rather than a requirement. The official installation landing page recommends Docker with HTTPS and confirms that both Docker and direct shell deployment are supported. Current official Docker docs and the ZimaOS App Store manifest were additionally checked for persistence, architecture and the current v0.5.17 package.
