homelable
Self-hosted homelab infrastructure visualizer, interactive network diagram with live status monitoring
Runssource: GitHubhomepageTypeScriptMITcommit d656a6a07f4a
TypeScript, MIT licensed. The project labels itself: diagram, homelab, homelab infrastructure observability, network, proxmox ve, self hosted, zigbee and zwave.
homelable runs. An Argusic agent installed it in 1 minute and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Backend FastAPI app starts and responds to health checks, all 1512 backend tests pass, all 532 MCP tests pass; frontend build requires Node 20.19+ which is not available in this container.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 60 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- MCP_API_KEY env var in .env.example is not declared in Settings model, causing pydantic ValidationError on startup1 minute
- Install time
- 1 minutes
- Cold machine to finish
- 58 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- pytest --tb=short -q on backend exited 0 with 1512 passed, 8 skipped; health endpoint curl -s http://127.0.0.1:8000/api/v1/health returned HTTP 200 {'status':'ok'}
- Model tokens used
- 776,124
- Exact commit tested
- d656a6a07f4a
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
1. **Backend (FastAPI/ Python):** Installed deps (`pip install -r requirements.txt`), ran the test …
2. **MCP server:** Installed deps and ran tests.
3. **Frontend (React/Svelte/Vite):** Installed deps, attempted build.
### Error encountered
| Error | Fix |
|---|---|
| `MCP_API_KEY` env var (from `.env.example`) is not recognized by pydantic-settings — `ValidationE…
### Results
- **Backend:** 1512 passed, 8 skipped — all tests green
- **MCP server:** 532 passed, 4 skipped — all tests green
- **Frontend:** `npm install` succeeded, but `npm run build` fails because the container's Node.js …
- **App launch:** `uvicorn app.main:app --port 8000` starts clean; health endpoint returns `{"statu…Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 1 minute.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 1 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.21 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.17 |
Topics (from GitHub)
diagramhomelabhomelab-infrastructure-observabilitynetworkproxmox-veself-hostedzigbeezwavezwave-js
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/homelable)Questions
- Does homelable run?
- Yes. homelable runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test homelable?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d656a6a07f4a. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test homelable?
- The run that produced this verdict cost $0.21: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does homelable take to install?
- 1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does homelable need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing homelable?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for homelable?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.