Check widget count, timeouts and upstream response times before upgrading CPU; failed endpoints can create avoidable work.
Large boards with many live integrations.ホームページのハードウェア要件：RAM、CPU、ストレージ、ウィジェット、Docker連携
Docker連携の制限を踏まえ、ホームページのRAM、CPU、構成ストレージ、ウィジェットのポーリング要件を計画し、ZimaOSホームサーバーのハードウェア選びに役立つ実践的なガイダンスを提供します。
APP
Homepage hardware requirements at a glance
Homepage is a dashboard, so the applications behind its tiles usually determine server size. The reviewed official Docker guide and repository do not publish a numerical host minimum. Widget polling, concurrent viewers and Docker integrations drive its own load.
- RAM
- No numerical official minimum published. Budget the running dashboard and other containers together; increasing widget count or active viewers can change observed usage.
- CPU
- No numerical official minimum published. API polling, service checks and simultaneous dashboard requests drive activity; a GPU does not accelerate ordinary widgets.
- Storage
- Persist /app/config and custom assets. Do not count media, databases or downloads belonging to linked services as Homepage storage.
- Database / runtime
- The standard Docker deployment is configuration-file based and does not require a separate SQL server. The official container supplies the app runtime.
- Integrations / access
- Use reachable service URLs and the required HOMEPAGE_ALLOWED_HOSTS setting. Docker discovery is optional; a restricted socket proxy is preferable to unrestricted socket access.
- Best Zima starting point
- ZimaBoard 2 832 is a practical starting point for Homepage and light services. Choose the rest of the hardware for the apps that the dashboard links to.
From official requirements to the right setup
Plan the complete Homepage workload before selecting a server.
-
Official requirements
Use the official ghcr.io/gethomepage/homepage image and match its architecture to the host. Keep application runtime requirements separate from build-from-source dependencies.
-
Confirm your needs
Count active viewers, polling widgets and monitored services. Test dashboard loading with integrations enabled; slow upstream APIs can make a fast host appear slow.
-
Leave room to grow
Persist /app/config, any custom assets and a configuration backup. Keep API credentials and environment configuration available for a restore, while sizing linked services independently.
-
Run it on ZimaOS
Custom install the official container in ZimaOS, map port 3000 to a free host port and set HOMEPAGE_ALLOWED_HOSTS. Connect integrations using container-reachable URLs and add Docker access only if required.
Check every playback client
- Active dashboard viewers
- Number of API widgets
- Widget refresh intervals
- Service URLs reachable from container
- HOMEPAGE_ALLOWED_HOSTS hostname and port
- Persistent /app/config path
- Optional Docker socket proxy
- Linked-app resource budgets
Official minimum requirements
Checked on October 23, 2026 against official documentation and the project repository. Latest stable release observed: v2.6.0. Numerical requirements below retain their original scope.
Do not convert an anecdotal small idle-memory reading into an official minimum. Homepage is a presentation and integration layer; it does not run Plex, databases or other linked applications inside its own resource budget.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Host RAM | No numerical official minimum published. | The Docker guide does not define a universal numeric RAM floor. |
| CPU cores | No numerical official minimum published. | Polling and concurrent viewers determine observed load. |
| Disk capacity | No numerical official minimum published. | Configuration, custom assets, logs and backups need durable space. |
| Container | ghcr.io/gethomepage/homepage | Official prebuilt image; use an appropriate stable tag. |
| Architecture | AMD64 and ARM64 images | ZimaBoard 2 and ZimaCube 2 use x86-64/amd64. |
| Database | No separate SQL database in the standard setup | Configuration files are persisted in /app/config. |
| HTTP configuration | Port 3000 and HOMEPAGE_ALLOWED_HOSTS | Host validation must match the hostname/port you actually use. |
When to upgrade your hardware
Use observed Homepage workload pressure to decide when an upgrade is warranted.
Polling makes the dashboard busy
The shared host runs short of RAM
Configuration or custom assets become hard to recover
Measure the whole host and identify which linked service consumes memory instead of assuming the dashboard is responsible.
Homepage alongside media, AI or database services.Back up config and credentials and verify restore procedures; a dashboard does not justify a multi-bay NAS by itself.
Heavily customized boards and multiple environments.Plan hardware growth with confidence
Address storage, memory, compute and deployment limits separately.
Persist configuration on reliable storage
Keep /app/config and assets on durable storage with a small recoverable backup.
Existing ZimaBoard 2 persistent storage is sufficient for a modest board.Increase RAM for companion apps
Choose more RAM when the services shown on the dashboard need it, after checking actual usage.
ZimaBoard 2 1664 for multi-container headroom.Add capacity for linked services
Expand media/database storage according to the linked app requirements, not the count of dashboard tiles.
SATA SSD or ZimaCube 2 only when the underlying workload needs it.Tune integrations before buying compute
Reduce unnecessary polls and investigate slow endpoints; choose stronger hardware for verified host saturation.
Keep ZimaBoard 2 for ordinary dashboard use.Can it run on ZimaOS?
No specific public official one-click ZimaOS app page was verified, so this guide uses the fixed Custom Install route. Community-store availability is separate from an official catalog listing.
Custom install Homepage in ZimaOS
Use the official image, persist /app/config, map a free host port to container port 3000 and configure allowed hosts. Use a restricted Docker socket proxy if Docker integration is needed.
Custom install Homepage in the ZimaOS app ↗Use the official Homepage deployment instructions
Keep the selected stable release, persistent paths and companion services aligned with upstream documentation.
Review Homepage official installation ↗Review Docker integration permissions
Use the documented restricted proxy approach and reachable integration endpoints rather than granting unnecessary Docker access.
Review Homepage deployment details ↗Which Zima hardware fits Homepage?
Start with the lowest reasonable host for the actual workload. Product specifications were checked against the current product pages.
Which workload best matches your Homepage deployment?
Dashboard and light services
Choose a modest host with durable configuration storage.
- Workload optionZimaBoard 2 832
Dashboard on an existing multi-app server
Size the underlying services first, with more RAM if they need it.
- 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 | Dashboard and modest integrations | Homepage, configuration files and light companion services. |
|
No numerical upstream minimum is claimed; linked applications can require far more resources. | Get Now |
| ZimaBoard 2 1664 | Dashboard on a multi-container host | Homepage alongside a broader light application stack. |
|
The extra memory is for co-hosted services; it is not a Homepage requirement or a CPU upgrade. | 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 Homepage RAM, CPU, storage, Docker, database and ZimaOS sizing questions.
How much RAM does Homepage require?
No numerical official minimum published. Measure the container with your widgets and viewers active, then include all co-hosted apps in the server budget.
Does Homepage require a powerful CPU?
The official Docker guide gives no numerical core minimum. Ordinary dashboards fit a modest host; API polling, widget failures and simultaneous requests can increase work.
Does Homepage need PostgreSQL or MySQL?
The standard Docker deployment persists configuration files under /app/config and does not require a separate SQL server. External services displayed by widgets may have their own databases.
How much disk space should I plan?
Budget the image, configuration, custom assets, logs and backups. A tile linking to a multi-terabyte photo library does not make that library part of Homepage storage.
Does Homepage need a GPU or a specific CPU architecture?
No dedicated GPU is required for ordinary dashboard operation. Official images are available for AMD64 and ARM64; use AMD64 on ZimaBoard 2 or ZimaCube 2.
Can ZimaBoard 2 run Homepage?
It is a practical dashboard host. Start with the 8 GB version for light services and choose additional hardware based on the actual apps you will run behind the dashboard.
Why do widgets fail even when the page opens?
Widget API calls are made from the server/container. Verify routes, hostnames, ports and API credentials from that environment, and distinguish browser-facing URLs from container-reachable URLs.
Should I buy ZimaCube 2 for Homepage?
Homepage alone is not a reason to buy a higher storage tier. Consider ZimaCube when linked workloads need multiple drives, more CPU capacity or a broader consolidated server.
What sources informed this Homepage 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.
