Images and other attached assets are persistent node data. A long-running family/community server can become storage-bound even while CPU and RAM remain light.
For active groups that exchange many images/files or keep long backup histories.متطلبات الأجهزة لتطبيق Databag: ذاكرة الوصول العشوائي، ووحدة المعالجة المركزية، والتخزين، والمراسلة
تعرّف على متطلبات أجهزة Databag من حيث ذاكرة RAM ووحدة المعالجة المركزية وSQLite وأصول الرسائل وWebSockets ومكالمات WebRTC وأجهزة ZimaOS.
Databag hardware requirements at a glance
Databag is deliberately designed as a low-resource self-hosted messenger. Current upstream documentation proves it can run on very small consumer hardware, including a Raspberry Pi Zero v1.3, but it does not publish one universal CPU or RAM minimum.
- CPU
- No universal official CPU minimum is published. Upstream maintains a Raspberry Pi Zero v1.3 installation path, showing that the core server is designed for low-end hardware. Faster CPUs mainly help with larger active communities, asset handling, encryption/signing work and other services sharing the host.
- RAM
- No universal official RAM minimum is published. The current ZimaOS Databag manifest does not set a memory reservation or hard limit. Do not treat third-party Docker limits such as Marius Hosting's 2 GB mem_limit as a Databag requirement.
- Storage
- Databag persists both its database and message assets under /var/lib/databag. Upstream's Raspberry Pi Zero guide uses roughly a 16 GB microSD as a practical tiny-device setup, but real capacity should follow message attachments, images, other assets and backup retention.
- Database
- Databag uses SQLite for its node database, while assets are stored alongside the persistent node data. SQLite is appropriate for the project's intended family/small-community scale; very large unknown-user hosting should be treated as a separate scale question rather than assumed from 'unlimited accounts' wording.
- Calls and network
- Messaging uses REST plus WebSockets. Audio/video calling is WebRTC-based and needs a STUN/TURN relay for NAT traversal. The relay can be separate from the Databag node, so call bandwidth and relay sizing should not be confused with ordinary message-server CPU/RAM.
- Best Zima starting point
- ZimaBoard 2 832 is far more powerful than the tiny hardware upstream Databag targets and is the natural ZimaOS starting point. Upgrade for attachment storage, a larger all-in-one app stack or independent NAS workloads—not because Databag alone needs a large server.
From official requirements to the right setup
Databag sizing starts with the lightweight node itself, then adds account/activity scale, persisted message assets, WebSocket connections, WebRTC relay design and the other ZimaOS services sharing the machine.
-
Official requirements
Use upstream's low-resource design as the baseline: Databag explicitly targets limited consumer hardware and documents a Raspberry Pi Zero v1.3 installation path. Do not invent a modern 2-GB or 4-GB RAM minimum.
-
Confirm your needs
Estimate persistent data from message assets and retention rather than from the container image. The current ZimaOS package maps /var/lib/databag as the database and asset store.
-
Leave room to grow
Separate normal messaging from audio/video calls. REST and WebSockets terminate on the Databag node, while WebRTC NAT traversal requires a STUN/TURN service that can create its own bandwidth and infrastructure requirement.
-
Run it on ZimaOS
Run the intended family/community workload and monitor container RAM, CPU, SQLite/database latency, storage growth and WebSocket stability. Upgrade only after the actual node or wider home-server stack shows a sustained bottleneck.
Check every playback client
- Number of accounts and simultaneously connected clients
- Text-only usage versus frequent image/file assets
- Persistent /var/lib/databag capacity and backup retention
- SQLite database growth and local-storage latency
- WebSocket connection count and Internet upload quality
- WebRTC calls and separate STUN/TURN relay plan
- HTTPS/domain/reverse-proxy requirements for remote clients
- Other ZimaOS containers sharing the host
Official minimum requirements
Databag upstream does not publish a fixed CPU/RAM requirements table. Instead, the project repeatedly describes itself as lightweight, says it is designed for limited consumer hardware and provides a Raspberry Pi Zero v1.3 installation route.
The strongest safe conclusion is that Databag can run on extremely modest hardware, not that a specific RAM number is the official minimum. The current ZimaOS package has no memory reservation/limit in its manifest, so Zima hardware should be chosen from storage, activity and co-hosted workloads.
| Requirement | Official minimum | What this supports |
|---|---|---|
| CPU minimum | No universal official minimum published | The upstream project demonstrates operation on Raspberry Pi Zero v1.3 rather than defining a processor floor. |
| RAM minimum | No universal official minimum published | Neither the design overview nor current ZimaOS manifest provides a Databag RAM minimum. |
| Low-end reference device | Raspberry Pi Zero v1.3 supported by upstream manual-install guide | This proves low-resource capability but should not be converted into a universal production sizing formula. |
| Small-device storage example | About 16 GB microSD in the Raspberry Pi Zero guide | This is a practical installation assumption for that guide, not a universal Databag disk minimum. |
| ZimaOS persistent path | /var/lib/databag | The current App Store manifest describes this mount as the database and asset store. |
| ZimaOS architectures | amd64 and arm64 | Current ZimaOS Databag 0.1.18 supports these two architectures. The upstream Pi Zero manual path uses a different ARMv6 build route and should not be conflated with the ZimaOS package. |
When to upgrade your hardware
Databag upgrades are more likely to be triggered by assets, wider server consolidation or call infrastructure than by the basic chat process.
Message assets and backups outgrow the current disk
Many other ZimaOS apps create system-wide memory pressure
Calls and remote use require stronger network infrastructure
Databag is deliberately lightweight, but databases, media servers, automation and other containers can consume most of the host RAM. Upgrade based on total host pressure rather than Databag alone.
For all-in-one home servers with a growing Docker stack.WebRTC calls need STUN/TURN for NAT traversal. If a self-hosted TURN relay carries substantial call traffic, Internet upload and relay bandwidth can matter more than Databag node CPU.
For remote families or communities that use frequent audio/video calls.Plan hardware growth with confidence
Databag scales cleanly when node data, bulk assets, backups and WebRTC relay responsibilities are planned separately.
Keep Databag data on reliable persistent storage
The database and assets share the /var/lib/databag data path. Protect that directory with persistent local storage and backups.
Use SSD-backed AppData on ZimaBoard 2 when the node becomes important.Add capacity for growing message assets
Text messages are small, while images and files dominate long-term capacity. Size storage from retained assets rather than user count alone.
Add SATA SSD/HDD capacity as attachment history grows.Keep the TURN relay separate when call traffic grows
Databag's WebRTC call feature relies on STUN/TURN for NAT traversal. A separate relay keeps call-bandwidth planning independent from the messaging node.
Use a separate relay/VPS when WAN call traffic justifies it.Upgrade the Zima host only for broader workload growth
Moving from 8 GB to 16 GB or to ZimaCube 2 is usually about more applications or storage, not the lightweight Databag server itself.
Choose ZimaBoard 2 1664 or ZimaCube 2 only when total workloads require it.Can it run on ZimaOS?
Databag is currently available in the ZimaOS App Store under Social. The current package is version 0.1.18 and maps its database/assets to persistent AppData.
Install Databag from the ZimaOS App Store
The current ZimaOS package uses balzack/databag:0.1.18, exposes port 7000 and supports amd64 and arm64.
Open Databag in the ZimaOS App StorePreserve the database and asset store
ZimaOS binds /DATA/AppData/databag/data to /var/lib/databag. This is the important backup target for the Databag node.
Review the ZimaOS Databag manifestPlan HTTPS and WebRTC separately
Upstream recommends a DNS name/certificate for normal remote use, while audio/video calls additionally need STUN/TURN relay service for NAT traversal.
Read Databag installation and call guidanceChoose Zima hardware for your Databag workload
Databag is one of the lightest applications in this catalog. ZimaBoard 2 832 is the default choice; larger Zima hardware should be justified by attachments, backups and the rest of the home-server stack.
Is Databag mainly a family/private messenger, or one service inside a much larger storage and self-hosting system?
Family/private messaging and light self-hosting
Start with ZimaBoard 2 832. Its N150 and 8 GB RAM are vastly above the extremely small hardware Databag upstream targets. Choose 1664 only if other containers need the additional RAM.
- Databag plus lightweight home appsZimaBoard 2 832
- Larger multi-app Docker hostZimaBoard 2 1664
Large attachment archive or broader NAS workload
Choose ZimaCube 2 from storage requirements rather than Databag compute. Standard is enough for storage-first use; Pro only makes sense for heavier unrelated services. Creator Pack has no Databag-specific GPU benefit.
- Multi-drive message/file archive and backupsZimaCube 2 Standard
- Broader heavy home-server stackZimaCube 2 Pro
- Only when unrelated GPU/AI workloads require itZimaCube 2 Creator Pack
This is a workload guide, not a fixed account-count or message-throughput benchmark. Upstream says accounts/participants are not artificially capped, but that wording is not a guarantee of unlimited hardware capacity.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | The default and best-value current Zima option for Databag and a lightweight family self-hosting stack. | Databag, reverse proxy, notifications and several ordinary lightweight ZimaOS apps. |
|
Onboard eMMC is more likely to constrain a long attachment history than CPU or RAM. Add persistent SSD/HDD storage as assets and backups grow. | Get Now |
| ZimaBoard 2 1664 | Databag on a compact server with a much larger co-hosted application stack. | Databag plus more databases, automation, sync and other always-on containers. |
|
Do not imply Databag needs 16 GB. Upgrade only when the complete host needs more memory. | Get Now |
| ZimaCube 2 Standard | A storage-first NAS where Databag is one small social service among backups and files. | Databag, multi-drive household storage, backups and moderate self-hosted services. |
|
Choose Standard for storage capacity, not because messaging requires a Core i3-class processor. | Get Now |
| ZimaCube 2 Pro | A larger all-in-one NAS/app server where Databag shares the machine with heavier workloads. | Databag plus many containers, databases, backups, storage services and high-speed LAN workloads. |
|
Pro is unnecessary for Databag alone. | Get Now |
| ZimaCube 2 Creator Pack | A Databag-accessible server already required for unrelated GPU/AI/creator workloads. | Databag plus separate AI, GPU compute or creator services. |
|
Extreme overkill for Databag; never recommend it for more chat accounts or WebRTC calls 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
The supplied sources mix Databag-specific evidence with generic server-buying advice. These answers keep those evidence levels separate.
How much RAM does Databag need?
Databag does not publish one universal RAM minimum. Upstream deliberately targets constrained hardware and provides a Raspberry Pi Zero v1.3 installation path, while the current ZimaOS manifest sets no memory reservation or hard limit.
Is 2 GB RAM the Databag requirement?
No. Marius Hosting's Synology Compose example sets mem_limit: 2g. That is the author's container ceiling for that tutorial, not an upstream Databag minimum or recommendation.
Can Databag really run on Raspberry Pi Zero?
Yes, upstream has a dedicated Raspberry Pi Zero v1.3 manual-install guide and describes the server as lightweight. The guide assumes a minimal DietPi setup and roughly a 16 GB microSD. That is evidence of low-resource capability, not a production sizing guarantee.
How much storage does Databag need?
There is no universal disk minimum. The current ZimaOS package stores the database and assets under /var/lib/databag, so actual capacity depends mainly on retained images/files and backup history.
Does Databag need a separate database server?
No for the normal upstream design. Databag uses SQLite inside its persistent node data, which fits the project's intended low-resource family/community model.
Do audio/video calls require a powerful Databag server?
Not in the same way as a media transcoder. Databag uses WebRTC and requires STUN/TURN for NAT traversal. The relay's network bandwidth is a separate sizing problem from ordinary messaging.
Can ZimaBoard 2 832 run Databag?
Yes. The current ZimaOS package supports amd64, and ZimaBoard 2 832 provides an Intel N150 and 8 GB RAM—far beyond the low-end devices demonstrated by upstream. Use persistent SSD/HDD capacity if message assets become important.
Is the generic BlueHill server-buying guide useful for Databag sizing?
Only at a very general level. It discusses broad server CPU, RAM, storage and networking considerations rather than Databag. It should not be used to override Databag's own low-resource architecture or create application-specific minimums.
What sources and further reading informed this Databag hardware guide?
The upstream Databag design overview is the highest-value supplied source: it says Databag targets inexpensive consumer devices with limited resources and is designed to be efficient. The Giz Computer app listing independently describes Databag as lightweight and says the server can run on Raspberry Pi Zero v1.3, consistent with upstream. Marius Hosting's Synology guide sets a 2 GB Docker memory limit and maps /var/lib/databag, but that limit is tutorial configuration rather than a Databag requirement. The BlueHill article is generic server-purchasing guidance and provides no Databag-specific evidence. Current upstream README/Pi Zero documentation and the current ZimaOS App Store manifest were additionally checked to verify low-end support, persistent storage, architectures and package version.
