Measure CPU, storage latency and concurrent operations using realistic photos and documents before moving to a larger server.
Bulk inventory imports or multiple editors.Homeboxのハードウェア要件：RAM、CPU、ストレージ、SQLite、在庫添付ファイル
現在のコンテナ導入環境の詳細と、実用的なZimaOSの容量選びの目安を参考に、HomeboxのRAM、CPU、SQLiteストレージ、在庫写真、書類のバックアップを計画しましょう。
APP
Homebox hardware requirements at a glance
The active sysadminsmedia/Homebox continuation uses SQLite and embedded web assets. Its reported idle usage below 50 MB is an observation, not an official RAM minimum. Inventory photos, documents, backups and concurrent use determine practical host sizing.
- RAM
- No numerical official minimum published. The upstream README reports generally less than 50 MB idle container usage; this does not include workload peaks, OS or companion apps.
- CPU
- No numerical official minimum published. Image/document uploads, search, imports and concurrent requests matter more than the number of empty inventory records.
- Storage
- Persist /data, including SQLite and uploaded inventory assets. Photos, receipts, manuals and backup retention can outweigh structured item metadata.
- Database / runtime
- SQLite and embedded web assets are part of the lightweight application design; a separate PostgreSQL/MySQL service is not required for the standard deployment.
- Current container
- Use ghcr.io/sysadminsmedia/homebox from the active continuation, not an assumed-maintained historical image. Container port 7745 is mapped to the chosen host web port.
- Best Zima starting point
- ZimaBoard 2 832 is a practical shared-home inventory host. Choose more memory or storage for actual uploads and other services, not because of a fabricated app minimum.
From official requirements to the right setup
Plan the complete Homebox workload before selecting a server.
-
Official requirements
Confirm the active sysadminsmedia project and stable image rather than an obsolete historical namespace. Treat the README idle-memory observation separately from a formal minimum.
-
Confirm your needs
Estimate users, simultaneous edits/imports and the number/size of photos, manuals and receipts. Test representative uploads and search rather than using item count alone as a hardware metric.
-
Leave room to grow
Persist /data and keep a recoverable backup of SQLite plus attachments. Preserve deployment secrets such as the documented API-key pepper alongside the configuration needed for recovery.
-
Run it on ZimaOS
In ZimaOS Custom Install, use the current official image, a durable writable /data mount and an unused host mapping to container port 7745. Follow the selected image user/permission requirements, particularly for rootless variants.
Check every playback client
- Active sysadminsmedia image and stable tag
- Concurrent users and import size
- Photo/document count and average size
- Persistent /data location
- SQLite plus attachment backup
- API-key pepper and configuration recovery
- Container user and data ownership
- Unused host port mapped to 7745
Official minimum requirements
Checked on October 23, 2026 against official documentation and the project repository. Latest stable release observed: v0.27.0 (sysadminsmedia continuation). Numerical requirements below retain their original scope.
The under-50-MB figure is an upstream idle-container observation, not an official server minimum. Whole-host sizing and attachment retention require additional capacity. Confirm the selected image platform before deployment; do not assume old and current project images are interchangeable.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Host RAM | No numerical official minimum published. | Reported idle usage below 50 MB is not a minimum or peak-memory guarantee. |
| CPU cores | No numerical official minimum published. | Upload/import activity and concurrency affect practical demand. |
| Disk capacity | No numerical official minimum published. | Inventory attachments, SQLite, logs and backups determine capacity. |
| Database | SQLite | The standard application does not require an external SQL server. |
| Official current image | ghcr.io/sysadminsmedia/homebox | Use the active project continuation and a tag with a matching host architecture. |
| Persistent data / port | /data; container TCP port 7745 | The host port may differ; keep the data directory writable to the selected image user. |
| Deployment recovery material | Preserve configuration and documented secrets | The current quick start includes HBOX_AUTH_API_KEY_PEPPER; retain what is needed for a consistent restore. |
When to upgrade your hardware
Use observed Homebox workload pressure to decide when an upgrade is warranted.
Uploads or imports cause slow responses
The shared host starts swapping or killing containers
Attachments and backups dominate storage
Identify whether Homebox, another app or the database/file cache is responsible, then choose host memory for the combined workload.
Inventory running alongside media and automation services.Measure photo/document growth and retained backup versions. Structured item counts alone understate the space used by manuals and receipts.
Large household archives and long backup retention.Plan hardware growth with confidence
Address storage, memory, compute and deployment limits separately.
Persist the complete application data
Back up SQLite and attachments consistently and verify recovery; do not preserve only an empty container configuration.
Reliable ZimaBoard 2 storage or SATA SSD.Choose RAM for co-hosted applications
Move to 16 GB only when combined services create measured memory pressure.
ZimaBoard 2 1664.Expand attachment capacity
Size additional storage from photo/manual uploads and backup retention, leaving room for exports and restores.
SATA/PCIe SSD; multi-drive storage only if the broader archive warrants it.Improve storage or compute after measurement
Check database/file I/O and import concurrency before assuming a higher CPU tier is necessary.
Keep a modest host for ordinary family inventory.Can it run on ZimaOS?
No specific public official one-click Homebox ZimaOS app page was verified. Use Custom Install with the active sysadminsmedia continuation and verify image platform, persistence and permissions.
Custom install Homebox in ZimaOS
Use ghcr.io/sysadminsmedia/homebox, persist /data, preserve documented secrets and map an available host port to 7745. Match directory ownership to the selected regular/rootless image.
Custom install Homebox in the ZimaOS app ↗Use the official Homebox deployment instructions
Keep the selected stable release, persistent paths and companion services aligned with upstream documentation.
Review Homebox official installation ↗Confirm the active Homebox continuation
Review the maintained repository, current image namespace and quick-start configuration rather than relying on an obsolete project image.
Review Homebox deployment details ↗Which Zima hardware fits Homebox?
Start with the lowest reasonable host for the actual workload. Product specifications were checked against the current product pages.
Which workload best matches your Homebox deployment?
Family inventory with modest attachments
Start with a modest host and a complete recoverable data backup.
- Workload optionZimaBoard 2 832
Inventory alongside more server services
Choose memory for the combined workload and storage for actual attachments.
- Workload optionZimaBoard 2 1664
These are practical workload recommendations, not official app requirements, compatibility certification, measured capacity limits or performance guarantees. Include all co-hosted services and independent backups.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Household inventory | SQLite, photos/receipts and modest concurrent use with durable storage. |
|
8 GB is a practical shared-host choice, not an official Homebox minimum; attachments need their own capacity budget. | Get Now |
| ZimaBoard 2 1664 | Inventory in a broader app stack | More RAM headroom alongside other self-hosted services. |
|
The N150 CPU stays the same, and extra RAM does not replace a consistent SQLite/attachment backup. | 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
Answers to Homebox RAM, CPU, storage, Docker, database and ZimaOS sizing questions.
Does Homebox require only 50 MB RAM?
The active upstream README reports generally less than 50 MB at idle for the container. That is an observation, not a formal minimum, peak-memory guarantee or complete server RAM budget.
How many CPU cores does Homebox need?
No numerical official minimum published. is published for core count in the reviewed setup. Imports, search, image/document handling and concurrent users determine practical load.
Does Homebox need an external database?
The standard application uses SQLite with embedded web assets. A separate PostgreSQL or MySQL container is not required by the documented lightweight setup.
How much storage should I allocate?
Include SQLite, item photos, receipts, manuals, exports, logs and backup versions. A small number of items with large scanned manuals can need more space than many text-only inventory entries.
Does Homebox need a GPU or a special CPU platform?
No GPU is required for normal inventory functions. Select an image manifest compatible with the host; use linux/amd64 on Zima hardware rather than assuming every historical image supports the same platforms.
Can ZimaBoard 2 host Homebox?
It is a practical option for family inventory with durable data and backups. Choose host capacity for all services sharing the machine; the application alone does not justify a high-end server.
What should I preserve before changing the container?
Persist /data and back up SQLite plus uploaded assets consistently. Retain required configuration and secrets, including the API-key pepper if configured, and follow rootless data-ownership rules when using that image variant.
When should I choose ZimaCube 2?
Choose a larger storage platform only when the broader household archive or other apps need multiple drives or stronger compute. Homebox itself is lightweight and has no universal numerical host minimum in the reviewed sources.
What sources informed this Homebox hardware guide?
Official project requirements, installation/configuration documentation, repository/release information and the current Zima product pages were checked on October 23, 2026. Practical hardware recommendations are editorial sizing guidance rather than upstream minimums.
