A 7-Inch Homelab with Networking, Offline Resources, and Battery Backup

Thank you to u/matteozenchit for sharing a project that makes the decisions behind a small homelab visible. This build puts networking, a small server and battery backup into a 7-inch RackMate TT. Its value is the way those parts work together: better connectivity in one room, local resources on a mini PC and a power arrangement that travels with the rack.

The story began with poor bedroom Wi-Fi. In the original Reddit build, the creator explains how adding a router to an existing wired connection gradually became a complete desktop system. The account includes equipment choices, power distribution, cost details and the limits of the finished project. Figures below are the contributor's own reports, rather than measurements by ZimaSpace.

From a Bedroom Network Problem to a Small Rack

The most revealing starting point is a household task rather than a shopping list. A wired switch already served devices behind the desk; wireless coverage was the part that needed improvement. A travel router joined the setup, leaving more cables and power adapters to organize.

Adding the router left more cables, power supplies and networking equipment on the desk. The creator decided to organize them into a single compact rack.

That explanation gives the rack a concrete purpose. It brings an existing set of devices together instead of beginning with an empty enclosure and finding equipment to fill it. The eventual server addition expanded the scope, but the original networking problem remains easy to identify.

What Each Part of the Rack Does

The creator provides a useful top-to-bottom inventory:

Keeping the roles visible is more helpful than treating every device as interchangeable. The mini PC runs the local workload. The router and switches provide the paths clients need to reach it. Battery backup supports that group of equipment.

Why the Creator Chose Seven Inches

The smaller format was a deliberate constraint. The author already had a larger rack elsewhere and wanted this one to sit on a desk. RackMate TT supports a 7-inch configuration, which provided the desired footprint while reducing compatibility with conventional rack equipment.

Custom printed mounting parts helped make the chosen devices fit. The important distinction is between the rack format and the equipment inside it: a compact enclosure does not automatically make an arbitrary router, power supply or server compatible. In this project, the creator worked through that fit as part of the build.

For readers comparing approaches, u/jc-21's small homelab story explores another way to give a small installation clear responsibilities. The two projects have different hardware and priorities, but each explains why the system has the shape it does.

Power Distribution Became Part of the Project

The author describes the power arrangement in unusually useful detail:

The W150 uses an external DC power supply, while the rack devices require different input voltages. A SlimQ power-distribution hub brings those connections together, leaving the completed rack with one external AC cable.

These statements describe the contributor's particular installation. They are not a universal wiring recipe: reproducing a power chain requires checking each device's input specification, connector and the distribution hardware being used. The story's practical contribution is showing why power deserves attention alongside the network diagram.

Offline Resources Give the Server a Defined Job

The mini PC hosts Project N.O.M.A.D., giving the rack a local resource role beyond networking. This is the part that makes the installation a small self-hosted service rather than simply an organized collection of switches.

The creator presents battery backup and locally available resources as reasons the rack can remain useful when the main infrastructure or internet connection is unavailable. That is a project goal and reported configuration, not an independently tested guarantee of outage coverage. The contents actually available locally determine what a user can retrieve without an external connection.

Read the Cost and Runtime Figures in Context

The original post includes an initial cost estimate and a more detailed bill of materials in the replies. Those figures should remain attached to the author's purchases and the items included in each calculation; they are not a current retail quote for reproducing the system.

The same distinction applies to battery life. The post reports idle consumption and discusses an expected runtime using a manufacturer's load figure. An expectation calculated from a specification is different from a completed discharge test of this assembled rack. The estimated runtime should be distinguished from a completed discharge test.

FAQ

Does this build use ZimaBoard hardware?

The reported compute device in this particular 7-inch rack is a GMKtec G10. That is the compute hardware used in this particular installation.

Is a seven-inch rack easier to build than a ten-inch rack?

This account does not establish that. The author chose the smaller format for the desk and used custom mounts to accommodate it. Reduced size came with compatibility tradeoffs.

Can the rack work without the internet?

The creator describes a local resource workload intended to support that use. Which resources remain available depends on what is stored locally and which connected clients can reach the system.

Are the topology drawings original photographs?

No. In the replies, the creator says ChatGPT helped produce the topology illustration. It must be identified separately from the project's hardware photographs.

Conclusion

This project is worth sharing because the builder explains the decisions as well as the finished rack. A room's connectivity problem led to organized networking, a small local server and an integrated battery arrangement. The compact enclosure is the visible result of those choices.

Readers starting a different household project can also explore u/2Hard4Him's family server story. Its priorities differ, which is precisely why a useful community story should keep the original person's needs, equipment and unfinished work intact.