Check API reachability and endpoint response time before assuming the host CPU is too weak.
Busy dashboards with multiple viewers.Hardwarevereisten voor Homarr: RAM, CPU, opslag en appgegevens en live-integraties
Plan Homarr-hardware op basis van de officiële vereisten van 500 MB RAM en opslagruimte voor containerimages, persistente appdata, databasekeuzes en implementatierichtlijnen voor ZimaOS.
APP
Homarr hardware requirements at a glance
Homarr documents 500 MB RAM, 600 MB free disk space for its container image, linux/amd64 or linux/arm64, and persistent writable /appdata. These app-level requirements exclude ZimaOS, other containers, appdata growth and backups.
- RAM
- Official documented app requirement: 500 MB RAM. Budget host operating system and other services separately; 500 MB is not a whole-ZimaOS-host specification.
- CPU
- linux/amd64 or linux/arm64 is required; linux/arm/v7 is unsupported. No numerical CPU-core minimum is published in the reviewed requirements.
- Storage
- Official requirement: 600 MB free disk for the container image. Add persistent /appdata, database growth, custom assets, logs and backups.
- Database / secrets
- The standard local setup uses SQLite under /appdata. Preserve SECRET_ENCRYPTION_KEY with your backup; external PostgreSQL needs its own backup and resource budget.
- Live integrations
- Widget API requests and Docker integrations add activity. Container port 7575 must map to an available host port; Docker socket access is optional.
- Best Zima starting point
- ZimaBoard 2 832 is a practical starting point. Select extra RAM or a larger server for the monitored applications, not merely for a dashboard.
From official requirements to the right setup
Plan the complete Homarr workload before selecting a server.
-
Official requirements
Apply the official 500 MB RAM, 600 MB image-space and supported-architecture requirements. These describe the application rather than the entire ZimaOS stack.
-
Confirm your needs
Estimate simultaneous viewers and the number/frequency of live widget integrations. Differentiate Homarr workload from the services the board monitors or controls.
-
Leave room to grow
Persist the complete /appdata directory and keep SECRET_ENCRYPTION_KEY with recovery material. Include the database, configuration and custom data, not only the container image.
-
Run it on ZimaOS
In ZimaOS Custom Install, use ghcr.io/homarr-labs/homarr with a persistent writable /appdata mount and available port mapping for 7575. Add the Docker socket only if its discovery or management integration is needed.
Check every playback client
- linux/amd64 or linux/arm64 image
- 500 MB application RAM plus host headroom
- 600 MB image space plus appdata growth
- Persistent writable /appdata
- SECRET_ENCRYPTION_KEY backup
- Container-reachable integration URLs
- Unused host port mapped to 7575
- Pre-upgrade database restore plan
Official minimum requirements
Checked on October 23, 2026 against official documentation and the project repository. Latest stable release observed: v2.8.1. Numerical requirements below retain their original scope.
The 500 MB and 600 MB figures are official application requirements. Do not present them as total ZimaOS RAM or total disk capacity. Extra drive bays or GPU hardware are not justified by ordinary dashboard operation.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Application RAM | 500 MB | Official Homarr requirement; host OS and companion containers need additional memory. |
| Container image space | 600 MB free disk | This is not the total application-data or whole-server storage requirement. |
| CPU architecture | linux/amd64 or linux/arm64 | linux/arm/v7 is explicitly unsupported. |
| CPU core count | No numerical official minimum published. | Widget activity and concurrent viewers affect practical CPU demand. |
| Persistent storage | Writable /appdata required | Contains the application database and configuration. |
| Official image / port | ghcr.io/homarr-labs/homarr; port 7575 | Use a stable image matching the host architecture and a non-conflicting port mapping. |
| Database / encryption | Local SQLite; SECRET_ENCRYPTION_KEY must persist | External PostgreSQL deployments require their own database backup and sizing. |
When to upgrade your hardware
Use observed Homarr workload pressure to decide when an upgrade is warranted.
Widgets are slow with many active integrations
Memory pressure affects the shared server
Appdata cannot be restored after an upgrade
Monitor Homarr separately from the database, media apps and other containers; increase host memory only for demonstrated contention.
Consolidated home-server setups.Preserve the database, complete appdata and matching encryption key before migrations. An image-only rollback is not a database rollback.
Major-version upgrades and customized dashboards.Plan hardware growth with confidence
Address storage, memory, compute and deployment limits separately.
Persist appdata reliably
Use a durable writable path and verify a complete backup with the encryption key.
Existing ZimaBoard 2 storage or a small SSD.Add RAM for the actual shared workload
Select 16 GB when the apps behind Homarr need more headroom.
ZimaBoard 2 1664; no CPU-core increase.Expand linked-app data storage
Size downloads, photo libraries and databases according to their own requirements rather than Homarr image size.
SATA/PCIe storage; ZimaCube only if those services need multiple drives.Tune live integrations
Reduce unnecessary updates and repair unreachable API endpoints before upgrading hardware.
ZimaBoard 2 remains appropriate for a normal dashboard.Can it run on ZimaOS?
No specific public official one-click ZimaOS app page was verified. Use Custom Install with the current upstream image and configuration; third-party store presence is not the same as an official one-click listing.
Custom install Homarr in ZimaOS
Use the official Homarr image, a writable /appdata mount, persistent SECRET_ENCRYPTION_KEY and an unused host mapping for port 7575. Mount Docker access only for the integrations you use.
Custom install Homarr in the ZimaOS app ↗Use the official Homarr deployment instructions
Keep the selected stable release, persistent paths and companion services aligned with upstream documentation.
Review Homarr official installation ↗Review deployment and upgrade instructions
Follow appdata/database backup guidance and preserve the encryption key before major-version migrations.
Review Homarr deployment details ↗Which Zima hardware fits Homarr?
Start with the lowest reasonable host for the actual workload. Product specifications were checked against the current product pages.
Which workload best matches your Homarr deployment?
Dashboard with light integrations
Use a modest host and preserve appdata plus the encryption key.
- Workload optionZimaBoard 2 832
Dashboard alongside more applications
Choose additional host memory for co-hosted services.
- 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 | Home dashboard | Homarr with a local database and modest live integrations. |
|
8 GB is a practical shared-host choice, not Homarr's official app RAM requirement. | Get Now |
| ZimaBoard 2 1664 | Dashboard plus companion apps | More memory for the actual services monitored by Homarr. |
|
A dashboard alone does not require the 16 GB tier; CPU stays N150. | 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 Homarr RAM, CPU, storage, Docker, database and ZimaOS sizing questions.
What is the official Homarr RAM requirement?
Homarr documents 500 MB RAM. Add memory for ZimaOS, any external database and other apps before choosing host hardware.
How many CPU cores does Homarr require?
The reviewed getting-started requirements do not publish a numerical core minimum. They do require linux/amd64 or linux/arm64; linux/arm/v7 is unsupported.
Which database does Homarr use?
The standard local setup stores SQLite in /appdata. The documentation also discusses external PostgreSQL; that database needs separate resources and native backup procedures.
Is 600 MB enough storage for Homarr?
600 MB is the documented free space for the container image. Add writable appdata, database growth, custom content, logs, upgrade headroom and backups.
Does Homarr require a GPU?
No dedicated GPU is required for the normal dashboard and integration workload. Use the image architecture matching your host; Zima hardware uses amd64.
Can ZimaBoard 2 run Homarr?
It is a practical starting point for a home dashboard with suitable persistent storage. Size media, automation, databases and other services displayed by the dashboard separately.
What must I back up before a major upgrade?
Stop Homarr before copying the complete local appdata and retain its configuration and encryption key. Back up an external database separately. Restore the pre-upgrade database for rollback; changing only the image can leave incompatible migrated data.
When should I choose ZimaCube 2?
Choose it when the services behind the board require multi-drive capacity or stronger compute. Homarr itself does not justify a high-end storage or GPU tier.
What sources informed this Homarr 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.
