← Directory

RackPeek

RackPeek is a lightweight, opinionated CLI tool + Web UI for documenting and managing homelab and small-scale IT infrastructure.

  • Infrastructure
  • Network Services
  • Productivity
  • Tools & Utilities
RackPeek is a lightweight, opinionated CLI tool + Web UI for documenting and managing homelab and small-scale IT infrastructure.

Platform availability

Available on 2 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

15/100 Low

Maintained
0GitHub repository no longer exists
Popular
No data
Easy to install
452 install platforms, install notes, Docker image
Light to run
No data

Based on 2 of 4 factors.

Availability: platform listings confirmed today, links checked 10 days ago

No GitHub repository data collected yet.

Checked 17 days ago - source: GitHub (BigBearTechWorld/rackpeek)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 17 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Start RackPeek with Docker Compose Run docker compose up -d to start RackPeek quietly in the background. Without this, the app is not running yet, so you cannot open its web interface. source
  • Save RackPeek settings on your computer In Docker Compose, map a folder from your machine to /app/config, for example /path/on/host/rackpeek:/app/config. This keeps your RackPeek settings on your computer instead of only inside the container, so they are not lost if the container is rebuilt. source
  • Add your gear to the YAML config file Put your devices under the top-level resources list in the config file, giving each item a kind and a unique name. RackPeek reads this list to build your rack, so if it is empty or formatted incorrectly, your setup may not appear. source

Fetched today - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does RackPeek keep its data on the same infrastructure it documents?

The GitHub README states that what runs on your infrastructure stays on your infrastructure.

Is RackPeek positioned for enterprise CMDB use?

No, the README says the project is optimized for home labs and self-hosted environments, not enterprise CMDBs or corporate environments.

Do the RackPeek guides assume Docker experience?

The Substack how-to notes that it assumes some basic experience with Docker and self-hosting.

Can I manage rack documentation with Git and YAML?

The VirtualizationHowTo article describes documenting a home lab as code using RackPeek, YAML, and Git for version-controlled rack layouts and infrastructure documentation.

Answers sourced from github.com, jaredheinrichs.substack.com, www.virtualizationhowto.com

Community

Collected 16 days ago - public community threads