HoloPlay Hardware Requirements: RAM, CPU, Storage & Invidious API
Plan HoloPlay hardware for RAM, CPU, Node.js, Invidious API traffic, Docker, and practical ZimaOS deployment recommendations.
HoloPlay hardware requirements at a glance
Size HoloPlay from verified upstream requirements first, then add headroom for the real workload and persistent data.
- RAM
- No numerical official minimum published
- CPU
- No numerical official minimum published
- Storage
- Small application footprint
- Runtime
- Node.js 18+ for local setup
- Dependency
- Uses an Invidious API endpoint
- Best Zima starting point
- ZimaBoard 2 832
From official requirements to the right setup
Treat HoloPlay as a lightweight web app with an external Invidious dependency, not as a local video-transcoding server.
-
Official requirements
-
Confirm your needs
-
Leave room to grow
-
Run it on ZimaOS
Check every playback client
- Node.js or Docker path
- Invidious API URL
- Concurrent users
- Data sync use
- Persistent app data
- Reverse proxy/TLS
- Internet connectivity
- Other containers
Official minimum requirements
Upstream publishes Node.js and Docker requirements but no numerical whole-host CPU, RAM, or disk minimum.
Do not size HoloPlay like Plex or Jellyfin. It is primarily a web/PWA workload using Invidious.
| Requirement | Official minimum | What this supports |
|---|---|---|
| No numerical official minimum published | Web/PWA workload. | |
| No numerical official minimum published | Depends on runtime and other services. | |
| 18 or higher | Required for local setup. | |
| spout8301/holoplay:latest | Documented by project. | |
| 3000 | Docker example maps port 3000. | |
| Configured through REACT_APP_API_URL | Endpoint affects functionality and latency. | |
| Not required | No local transcoding GPU requirement. |
When to upgrade your hardware
More users
Host consolidation
API latency
Plan hardware growth with confidence
Persistent app data
Keep local state on persistent storage.
SSD or persistent volumeRAM headroom
Useful mainly on a busy multi-app host.
More RAMReverse proxy
Use stable TLS when exposing remotely.
Existing ZimaOS proxy/network stackCPU only when needed
Upgrade only after local utilization shows CPU pressure.
Higher-throughput CPUCan it run on ZimaOS?
Install HoloPlay from the ZimaOS App Store
A specific public HoloPlay App Store page is verified.
Open HoloPlay in the ZimaOS App Store โUse the upstream Docker image
The project documents spout8301/holoplay on port 3000.
Open HoloPlay source โConfigure a reliable Invidious API
HoloPlay depends on an Invidious endpoint.
Review HoloPlay setup โZima hardware for HoloPlay
HoloPlay is light enough that hardware should usually be chosen for the other services on the ZimaOS host.
Choose by workload
Use the smallest reasonable Zima host.
Choose hardware for the combined workload.
Zima product guidance is a practical workload mapping, not an upstream hardware certification.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Light self-hosted services and small persistent workloads | Single-app or small multi-app home-server deployments |
|
8 GB RAM and a 4-core N150 limit heavier CI, databases, and high-concurrency work | Get Now |
| ZimaBoard 2 1664 | More containers and memory-heavier services on a low-power CPU | Moderate multi-app workloads |
|
CPU throughput is unchanged from the 832 model | Get Now |
| ZimaCube 2 Pro | CPU-heavy, higher-concurrency, and database-heavy workloads | Builds, indexing, many connections, or demanding containers |
|
16 GB RAM can still limit very large builds, databases, or local AI | 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
How much RAM does HoloPlay need?
Upstream does not publish a numerical whole-host RAM minimum.
How many CPU cores does HoloPlay need?
No numerical official CPU minimum is published.
Which Node.js version does HoloPlay require?
The upstream setup instructions require Node.js 18 or higher.
Does HoloPlay have a Docker image?
Yes. The project documents spout8301/holoplay:latest.
Does HoloPlay transcode YouTube video locally?
It is built around Invidious and a web playback workflow, not documented as a local transcoding server.
Can ZimaBoard 2 832 run HoloPlay?
Yes as a practical small-instance starting point.
Does HoloPlay need a GPU?
No GPU requirement is documented.
When should I use a larger Zima system?
When heavier co-located apps or measured CPU/RAM pressure justify it.
