Thank you to u/PierroDuv for sharing a homelab that fits beneath a television in less than 14 cm of height. The setup separates a Proxmox mini PC from a custom ZimaOS NAS, giving virtual machines and household photo and movie storage different physical homes.
The original Reddit post describes a project assembled over two years, largely because space was limited. Its photograph includes a tape measure beside the equipment, making the constraint visible rather than leaving “small homelab” as an abstract label.
The Shelf Height Comes Before the Equipment List
A narrow shelf sets a different starting point from a server rack. The builder has to consider the height of the case, the cables behind it and the ability to reach the machine after installation. Here, the owner reports keeping the setup below 14 cm, or about 5.5 inches.
The photograph places the Proxmox mini PC to the left, the NAS in the middle and the internet router to the right. These are three separately identified roles in one small household location. The server does not need to occupy a dedicated room to have a recognizable architecture.

The image establishes placement, not a thermal test. The post does not include temperatures collected inside the shelf during sustained operation. That distinction matters when comparing the same case installed in a different cabinet or with different clearance around it.
Proxmox and ZimaOS Have Different Jobs
The Proxmox machine is identified as a Beelink SER5 Pro with a Ryzen 7 PRO 5850U, 32 GB of RAM and 1 TB of storage. The creator uses it for a pfSense firewall, Home Assistant, WireGuard and a Linux VM for personal projects managed with Portainer.
The NAS is a separate custom computer running ZimaOS for pictures and movies, including Jellyfin and related library-management tools. Keeping those roles on different computers makes the intended division easy to understand: one machine provides a place for virtualized services, while the other carries the household storage role.
| Part of the setup | Reported configuration or job |
|---|---|
| Proxmox mini PC | Ryzen 7 PRO 5850U, 32 GB RAM and 1 TB storage |
| Virtualized services | pfSense, Home Assistant, WireGuard and personal-project Linux VM |
| ZimaOS NAS case | Jonsbo N10 |
| NAS motherboard and CPU | Gigabyte H610I DDR4 and a used Intel Core i5-12500T |
| NAS memory | One 8 GB DDR4 module |
| NAS storage | Four used 1.92 TB Samsung SATA SSDs and a reused NVMe drive |
| Household applications | Pictures, movies, Jellyfin and library-management services |
The owner mentions other VMs that are not finished. They remain experiments in progress, rather than additional completed services to add to the machine’s achievements.
The NAS Build Reuses Parts Around a Compact Case
The parts list combines a second-hand i5-12500T and used SATA SSDs with an NVMe drive reused from a previous laptop. The creator also specifies a low-profile Thermalright AXP90-X36 cooler and a SilverStone 350 W Flex power supply. Those choices belong to the reported assembly; the post does not provide a general compatibility guide for every variation of the case.
Four 1.92 TB SSDs describe the installed devices, but not the usable capacity of the final storage arrangement. The source does not identify a RAID level, filesystem or reserved space. A reader should therefore keep the drive inventory separate from a claim about available or protected storage.
The creator gives approximate historical budgets of €600 for the Proxmox machine and €700 for the NAS. These are the owner’s figures at the time of the build, not current market prices or a verified checkout list. Reused and second-hand parts also make a direct replacement-cost comparison difficult.
Our budget i3 family-server story offers another example of assigning existing hardware to household media and photos. This build takes a different route by separating the storage computer from the virtualization host.
A Virtualized Firewall Adds a Networking Dependency
pfSense is listed among the Proxmox workloads, while a separate internet router remains on the shelf. The post does not provide the interface assignments or a complete routing diagram. It would be premature to describe exactly which household connections pass through the firewall VM.
Netgate’s official Proxmox virtualization guide explains the need to assign the firewall’s network connections deliberately. It provides technical context for the application named here, without revealing the configuration used by this contributor.
For a similar owner, the useful operating question is what remains reachable while the Proxmox host reboots. Keeping NAS data on another computer can separate one physical dependency, but the network path to that NAS still matters. Physical separation alone does not answer the routing question.
WireGuard is the creator’s stated way to reach the home network remotely. Its official quick-start guide provides a separate configuration reference for readers exploring that role. The post establishes that purpose without publishing keys, tunnel rules or a security audit. Its role can be described accurately without expanding it into an undocumented promise about every service.
Quiet Operation Is a Goal with Several Moving Parts
The parts list includes a power-supply fan modification intended to reduce noise. The creator supplies comparative fan figures, but no measurement of the complete installed homelab. Those figures should not be presented as a tested room-noise reduction for the entire setup.
The useful lesson is that sound comes from several parts of a compact system: the computer’s cooling, the NAS cooler, the power supply and the way equipment sits in furniture. The post shows one owner working through that problem; it is not a power-supply modification tutorial.
Someone evaluating a similar shelf arrangement would need to consider the actual workload and installation together. A system that fits physically still needs room to manage cables, move air and be serviced. These are consequences of the visible space constraint rather than measurements supplied for this machine.
Separate Storage Still Needs Its Own Recovery Plan
Keeping a NAS beside a virtualization host makes it tempting to think the two machines automatically protect each other. The source does not describe a backup relationship between them. Photos and movies on the ZimaOS NAS should therefore not be described as independently backed up on the Proxmox machine.
Protecting a virtual machine and protecting a separate NAS collection are different jobs. For readers planning a similar arrangement, the destination and restore method need to match what is being preserved. A copy that exists only on the same NAS is still dependent on that NAS remaining available.
The HP ProDesk ZimaOS homelab story is a useful comparison for the relationship between a small computer and its storage. Readers comparing a custom SSD NAS with an integrated system can also consult the ZimaCube 2 product page as a separate hardware reference.
FAQ
Which machine runs ZimaOS?
The custom NAS in the middle of the shelf runs ZimaOS. The separate Ryzen-based mini PC runs Proxmox and the listed virtualized services.
How much height does the setup use?
The creator reports less than 14 cm, about 5.5 inches. The original photograph includes a tape measure beside the equipment.
Do four SSDs prove that the NAS has redundant storage?
No. The post lists the drives but does not specify the redundancy configuration or usable capacity.
Has the planned network-segmentation upgrade been completed?
The creator describes a possible future custom-router purchase after moving to a larger place. It is a plan, not a completed upgrade in this story.
Conclusion
PierroDuv’s homelab works around a concrete household limit: the space below a television. Its separate Proxmox host and ZimaOS NAS give applications and storage clearly described homes, while used parts and a low-profile enclosure shape the physical build. The original post is most useful as a record of those choices, with unfinished VMs, networking plans and unreported storage policies kept distinct from completed work.
Welcome to the ZimaSpace community! Share your setup, ask questions, and explore practical build guides, real user stories, and product updates with fellow self-hosters.
Zima Campaign Hub
More to Read

A ZimaBoard 2 Prototype with Two 22 TB Drives on the Test Bench
Explore sabitech2k’s early ZimaBoard 2 drive test, the reported power conditions, and the existing ZimaBoard used for Proxmox backups.

A Quiet ZimaCube and ZimaBoard Homelab with Debian and Docker
A ZimaCube and ZimaBoard split everyday applications from smart-home services, with Debian, Docker, Pi-hole and a Homepage dashboard.

A LEGO Rack for a First ZimaBoard 2 Home Server
See how a first-time builder organized a ZimaBoard 2 and two SSDs in a LEGO rack, with Home Assistant and home-office storage planned next.



