Large numbers of active widgets and health checks add network and Node processing, though the app remains lightweight.
Large homelab dashboards.Dashy 하드웨어 요구 사항: RAM, CPU, 디스크 및 Docker
공식 싱글 코어, 256MB RAM 및 약 250MB 디스크 권장 사양과 실용적인 ZimaOS 원클릭 배포 용량을 기준으로 Dashy 하드웨어를 계획하세요.
Dashy requirements at a glance
Dashy's current deployment documentation provides clear lightweight system-resource guidance for the Node server and Docker image.
- CPU
- Official requirement: any single core on x86-64 or ARM.
- RAM
- The Node server idles around 80–120 MB; 256 MB is described as comfortable and Dashy can work with less.
- Disk
- About 250 MB for the image, plus whatever your config, custom icons and other assets require.
- Architecture
- Current pre-built Docker images support amd64 and arm64; 32-bit armv7/armv6 are no longer supported by current images.
- GPU
- No GPU is required. Dashy is a lightweight dashboard/homepage application.
- Best Zima starting point
- ZimaBoard 2 832 is vastly above Dashy's requirements; choose larger Zima hardware only for the services Dashy links to.
From official requirements to the right setup
Dashy itself is lightweight, so size the server for the rest of your homelab and treat Dashy as a small frontend workload.
-
Official requirements
Use Dashy's published baseline: any single x86-64/ARM core, around 80–120 MB idle RAM, 256 MB comfortable, and about 250 MB image storage.
-
Confirm your needs
Persist /app/user-data because conf.yml and custom assets live there and should survive container upgrades.
-
Leave room to grow
Account for optional widgets, status checks and custom assets, but avoid sizing the host around Dashy when the linked services are far heavier.
-
Run it on ZimaOS
Install Dashy through the ZimaOS App Store, map persistent user-data, then size ZimaBoard/ZimaCube for the underlying media, AI, storage and automation services.
Check every playback client
- Number of dashboard pages
- Widgets/status checks
- Custom icons/assets
- Persistent user-data
- Authentication/SSO use
- Reverse proxy/HTTPS
- Linked homelab services
- Other ZimaOS apps
Official minimum requirements
Dashy's current deployment documentation publishes direct CPU, RAM and disk guidance.
Dashy is one of the lightest apps in this hardware directory. The 256 MB RAM and ~250 MB disk figures describe the app itself; Zima hardware selection should usually be driven by the services behind the dashboard.
| Requirement | Official minimum | What this supports |
|---|---|---|
| CPU | Any single core | x86-64 or ARM. |
| RAM idle | Approximately 80–120 MB | Current Node server idle range. |
| RAM comfortable | 256 MB | Dashy documentation says it works in less. |
| Disk | Approximately 250 MB | For the image, plus config/icons/custom assets. |
| Docker architectures | amd64 and arm64 | Current images do not support armv7/armv6. |
| Bare-metal runtime | Node.js 20+ and Yarn | Only needed when not using the pre-built container. |
When to upgrade your hardware
Dashy itself rarely causes a hardware upgrade; the linked services or unusually heavy dashboard customization usually do.
Widgets and status checks become unusually numerous
Custom assets expand
The host runs many heavy applications
Icons, images and custom files increase persistent storage beyond the small base image size.
Highly customized dashboards.Media servers, AI, databases and automation services dominate CPU/RAM long before Dashy itself does.
All-in-one ZimaOS systems.Plan hardware growth with confidence
Scale the services behind Dashy, not Dashy itself.
Keep Dashy on the smallest Zima host
Its official resource needs are far below even ZimaBoard 2 832 capacity.
ZimaBoard 2 832 is already ample.Persist configuration on reliable storage
Protect conf.yml and custom user-data even though the total storage footprint is small.
Any reliable Zima storage is sufficient for Dashy itself.Add RAM for the linked homelab apps
If the server grows, extra memory benefits databases, automation and media services rather than the dashboard.
ZimaBoard 2 1664 provides 16 GB whole-host headroom.Choose ZimaCube for broader storage/server needs
A larger NAS is justified by media, backups and application consolidation, not Dashy alone.
ZimaCube 2 Standard or Pro depending on the wider workload.Can it run on ZimaOS?
Dashy is currently highlighted by ZimaOS as a one-click App Store application in the Automation and Operations category.
Install Dashy from the ZimaOS App Store
Use the ZimaOS one-click Dashy listing, then persist /app/user-data for conf.yml and custom assets.
Open Dashy in the ZimaOS App Store ↗Use Dashy's official Docker deployment model
The current documentation recommends Docker for self-hosting and publishes a simple lissy93/dashy image workflow.
Review Dashy deployment ↗Keep Dashy sizing separate from homelab sizing
ZimaOS positions Dashy as a homelab homepage; the services it links to should drive the real hardware decision.
Review ZimaOS App Store overview ↗Choose Zima hardware for Dashy
Every current ZimaBoard 2 configuration is massively over the app's own CPU/RAM requirements, so choose hardware for the rest of the homelab.
Is Dashy the main workload or just the homepage for a larger server?
Dashy plus lightweight utilities
Use ZimaBoard 2 832; Dashy consumes only a small fraction of its resources.
- Best starting pointZimaBoard 2 832
Dashy fronts a larger homelab
Choose hardware for the linked apps, storage and network requirements rather than Dashy.
- More app headroomZimaBoard 2 1664
- Broader NAS platformZimaCube 2 Standard
These recommendations apply to Dashy itself; linked services can have completely different requirements.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Dashy plus lightweight homelab utilities. | Dashboard, status checks, widgets, reverse proxy and small companion services. |
|
Dashy uses only a small fraction of this hardware; sizing should focus on the other apps. | Get Now |
| ZimaBoard 2 1664 | Dashy as the homepage for a larger self-hosted stack. | Many Docker apps, databases, automation and monitoring services. |
|
The extra RAM is for the wider stack, not Dashy. | Get Now |
| ZimaCube 2 Standard | Dashy on a broader NAS/media/home-server platform. | Dashboard plus storage, backups, media and other multi-drive workloads. |
|
Choose ZimaCube for the services behind Dashy, not for Dashy's own compute needs. | 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
These answers cover Dashy RAM, CPU, disk, Docker and ZimaOS one-click deployment.
How much RAM does Dashy need?
Dashy's Node server idles around 80–120 MB, and the official deployment documentation says 256 MB is comfortable and it can work with less.
How many CPU cores does Dashy need?
Dashy lists any single x86-64 or ARM core as sufficient.
How much storage does Dashy need?
The official deployment guide says roughly 250 MB for the image, plus whatever your configuration, icons and custom assets require.
Which CPU architectures does Dashy support?
Current pre-built images support amd64 and arm64. Current images no longer support 32-bit armv7/armv6.
Does Dashy need a GPU?
No dedicated GPU is required.
Can ZimaBoard 2 run Dashy?
Yes, easily. Even the 8 GB ZimaBoard 2 is vastly above Dashy's published resource requirements.
Is Dashy available in ZimaOS?
Yes. ZimaOS currently highlights Dashy in its App Store Automation and Operations category.
What should determine hardware if Dashy is my homelab homepage?
Size the server for the applications Dashy links to—such as media, AI, storage and databases—not for Dashy itself.
What sources informed this Dashy hardware guide?
The guide uses current Dashy deployment/quick-start documentation, ZimaOS's App Store overview and current Zima product pages.
