Open-source project
geerlingguy/mini-rack avatar
geerlingguy/mini-rack

geerlingguy/mini-rack: a buying guide for 10-inch half-width rack builds

Miniature rack builds, for portable or compact Homelabs.

4,091 stars105 forksUnknownGPL-3.0

At a glance

What is it?
Project MINI RACK is a documentation site, not a piece of software: it collects 10-inch rack dimensions, gear tables and build notes for compact homelabs. The useful part is the sizing standard and the vendor list; the weak part is regional availability.
Who is it for?
Adopt this as a reference if you are planning a 10-inch rack and want the dimensions and a starting list of rack models before you buy anything. Skip it if you need a software stack for your homelab, or if you are shopping outside the US, since the README itself says the site focuses on gear the maintainer can acquire in the US and that many vendors sell only in the UK or parts of Europe.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository last received commits 3 days ago.
What is it written in?
GitHub does not report a main language for this repository.

Answers come from the project's GitHub data, last synced on November 13, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • geerlingguy/mini-rack4,091 ★ · +121
Star history
Repository2026-09-242026-11-13
geerlingguy/mini-rack4k4.1k

121 Stars in the last 50 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

A documentation project, not an installable tool

The repository is a website. The top-level entries are .github/, CNAME, LICENSE, README.md, _config.yml and assets/, which is the shape of a Jekyll site published to a custom domain rather than a library you add to a project. There is no package manifest at the root, and the repository has no published releases. So the question "should I adopt this" is really "should I read this before I buy rack gear". The README describes the scope plainly: it is a guide for miniature rack builds, for compact homelabs, RF battlestations, and portable network racks. The intended reader is someone assembling a small rack who needs to know what fits and what exists. That is a narrow audience, and the project is honest about it. Jeff Geerling maintains it, and the README says the site is mainly focused on gear he is able to acquire while living in the US, with a note that many vendors sell only in the UK or parts of Europe. If you are outside the US, expect to translate the shopping list into local suppliers yourself.

The 10-inch sizing rule and why it decides your build

The most reusable thing here is the dimensional section. The README states that there is no worldwide standard for a mini rack, but that most of the industry has settled on the same 1U height as a 19-inch rack, 44.45mm or 1.75 inches, with the width between screw holes at 236.525mm (9.312 inches). It then works out the consequence: an absolute maximum of around 220mm (8.75 inches) of horizontal clearance, and, allowing for tolerance, gear should fit within around 210mm (8.45 inches) of horizontal space. Mounting holes should accommodate a few millimeters of width to either side. Screw hardware is not uniform. The README says some manufacturers skip threads and use square holes for cage nuts, while others use standard 10/32 or 12/24 screws, and that the vertical spacing must follow the 19-inch rack specification either way. That last point is the one to check against a product page before ordering, because a rack with the right width and the wrong hole pattern will still not take the shelf you bought. The README points to issue #29 for further discussion of the dimensions.

What the hardware tables actually cover

The README is organized as a catalog with tables, and the rack table is the center of it. Entries include the Delock 10-inch Network Cabinet in 4U, 6U and 8U enclosed locking versions with a glass door; the Delock 10-inch Wallmount Rack at 1U; a Digitus Network Cabinet in 6U, 9U and 12U; a DIY laser-cut mini rack linked from another repository; the DSIT 15U; the Flyht Pro Stage Rack Double Door at 6U, described as a flight case with similar models down to 2U and requiring slight modification; the GeeekPi / DeskPi RackMate family across TT, T0, T1, T2 and TL1 in 3U through 12U open designs; Intellinet and KENUCO enclosed cabinets; L-com and Middle Atlantic open frames; and MikroTik's SolidRACK 5 mini. Beyond racks, the table of contents lists PDUs, UPSes, patch panels, network gear, 3D printable systems, and shelves for mini PCs, SBCs and disks. The useful signal in that list is the split between open and enclosed designs. Open racks like the RackMate line are cheaper and easier to cable, but they expose the gear and offer no locking. Enclosed cabinets with glass doors cost more and constrain airflow and cable routing. The README presents the options without ranking them, so the choice is left to you.

Reading the repository locally

Because this is a static site, there is nothing to install as a dependency, and no build command appears anywhere in the README. The repository root holds _config.yml and an assets/ directory containing the images the README references, such as /assets/images/jeff-geerling-mini-racks-001-002-1200.jpg. The project publishes a site at mini-rack.jeffgeerling.com, and the README also links a video announcing the project. For most readers the published site is the whole product; there is no documented local workflow to follow, and no supported Ruby version, Gemfile or serve command is stated. If you want the tables in a form you can diff or annotate, the practical move is to read the README.md and the assets/ directory directly in the repository rather than trying to run the site generator. The README does not describe a contribution or preview setup, so treat any local rendering you attempt as unsupported.

Regional availability is the real limitation

The README is unusually direct about its own blind spot. It says mini rack gear is often only available in specific regions, gives the example that many vendors sell only in the UK or parts of Europe, and states that the site is mainly focused on gear the maintainer is able to acquire while living in the US. That is a sourcing constraint, not a technical one, and it changes how you should use the tables. A rack model listed here may be unobtainable where you live, and the reverse is also true: local 10-inch gear may exist that never appears in the list. The README does allow that the scope could broaden over time, but as written the catalog reflects one person's purchasing reach. There is a second limitation worth naming. The site carries affiliate links, and the README says so: some links are affiliate links and the maintainer earns for qualifying purchases, which helps fund maintenance. That does not make the recommendations wrong, but it does mean the list is shaped by what is linkable and shippable, not by an exhaustive survey. If a category looks thin, it may be thin because the maintainer has not bought into it yet.

Where to take the questions the tables cannot answer

The README routes discussion to GitHub Issues and to Reddit's r/minilab. Issues are categorized with labels: "help me find" for locating a particular piece of equipment, "build showcase" for complete or nearly complete builds, and "website issues" for problems with the site itself. That structure matters if you are deciding whether to file something. A question about whether a specific 6U cabinet will take a specific shelf belongs under "help me find", and the answer will come from whoever has already tried that combination. For broader discussion of mini homelabs that may or may not involve a rack, the README points to r/minilab. The repository is not archived, and the last push was on 2026-08-31, so the issue tracker is the live part of the project. What you will not find there is a compatibility matrix. Nothing in the README claims that any listed shelf has been fitted to any listed rack, so cross-vendor fit remains something you confirm case by case.

Alternatives: a full 19-inch rack or a bare shelf

The obvious alternative is a standard 19-inch rack, and the difference is not just size. A 19-inch rack has decades of mounting hardware, rails, shelves and secondhand supply behind it, and the README's own dimensional section uses 19-inch spacing as the reference point it deviates from. If you have floor or closet space, the 19-inch path gives you more choice per U and usually lower prices on accessories. The cost is footprint and weight, which is exactly what the 10-inch format is trying to avoid. The other alternative is no rack at all: stack the mini PCs, switch and disks on a shelf and skip the mounting hardware. That is cheaper and more flexible, and it fails only when you need cable management, airflow separation or something that can be moved as a unit. The 10-inch format sits between those two positions. It buys you tidy mounting and portability at the price of a smaller and more regionally fragmented market, which is the trade the README's tables are trying to make navigable.

Editorial conclusion

Adopt this as a reference if you are planning a 10-inch rack and want the dimensions and a starting list of rack models before you buy anything. Skip it if you need a software stack for your homelab, or if you are shopping outside the US, since the README itself says the site focuses on gear the maintainer can acquire in the US and that many vendors sell only in the UK or parts of Europe. Verify two things first: the exact screw type and hole pattern of the specific rack you plan to order, because the README notes some manufacturers use square holes for cage nuts while others use 10/32 or 12/24 screws, and the horizontal clearance you actually need, since the stated 236.525mm between screw holes leaves around 220mm of absolute maximum clearance and the README suggests staying within roughly 210mm.

Frequently asked questions

What is the purpose of a mini rack?

The README describes the project as a guide for miniature rack builds aimed at compact homelabs, RF battlestations and portable network racks. The 10-inch format is meant to fit where a full 19-inch rack will not.

What is the smallest rack size in geerlingguy/mini-rack?

The rack table lists 1U as the smallest height, in the Delock 10-inch Wallmount Rack, and the Flyht Pro Stage Rack Double Door is noted as having similar models available down to 2U. Heights in the table otherwise run from 3U up to 15U.

How does a mini rack compare to a full rack in geerlingguy/mini-rack?

The README states that mini racks keep the same 1U height as a typical 19-inch rack, 44.45mm or 1.75 inches, but set the width between screw holes at 236.525mm. That leaves an absolute maximum of around 220mm of horizontal clearance, against the far wider 19-inch format.

What is the best mini server rack according to geerlingguy/mini-rack?

The README does not rank the racks it lists. It presents them in a table with unit height and notes such as enclosed and locking, wall-mountable, open design, or flight case, and leaves the choice to the reader.

Official sources

  1. geerlingguy/mini-rack on GitHub
  2. Issues
  3. License: GPL-3.0
  4. Project website
  5. README
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/geerlingguy-mini-rack.svg)](https://hysenlabs.com/projects/geerlingguy-mini-rack)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/geerlingguy-mini-rack.svg)](https://hysenlabs.com/projects/geerlingguy-mini-rack)

Was this useful?