PCHealth
Forty workstations, one sorted table, and the odd one out flagged for you.
Free right now — no account, no card
Preview
1 interface design, then a screenshot of it running. Drag, scroll or use the arrows.
Free while we’re in preview
Get PCHealth
Forty workstations, one sorted table, and the odd one out flagged for you.
The Mac button is for Apple Silicon. On an older Intel Mac, get this one instead.
One file, both ways. Double-click it for the window. Run the same file from a command prompt with arguments and it behaves as the command-line tool, because the engine is inside it. Nothing else to download and nothing to keep beside it.
Early preview. The window has been built and run, but not yet on a real Windows PC or Mac, so expect rough edges. The engine underneath it is fully tested.
- One file — no installer
- Runs on your machine, offline
- Source code published below
Free while in preview. It isn’t signed yet, so Windows or macOS will ask you to confirm the first time you open it. At launch, PCHealth is included in every plan along with the rest of the range.
Read one line instead of forty
Each machine runs pchealth collect and writes a JSON report: the label you give it, hostname, OS and architecture, logical CPU count, and a genuine recursive walk of every path you asked it to watch, with total bytes, file count and how many entries couldn’t be read.
Gather those files however you already move files. pchealth rollup merges them into one table sorted worst first, with fleet totals, mean, median, standard deviation and a z-score per machine. Anything past --stddev-threshold is flagged OUTLIER.
Which standard deviation, and why it matters
It’s the population form, dividing by n, and both the table and the JSON say so. One consequence before you pick a threshold: under population stddev no machine in a fleet of n can exceed a z-score of sqrt(n-1), so the default of 2.0 flags nothing until you have six machines. For small fleets try 1.0 to 1.5, or just read the table.
Not a sensor tool
No temperatures, no fan speeds, no SMART attributes. Those need privileged per-platform APIs and this reads none of them. It measures the size of directory trees you name, not free space on a volume. A corrupt or foreign report is skipped with a stated reason and the rest still roll up.
Reading on the job itself
- How to find out what is inside a computer Every operating system will tell you the model, the processor, the memory and the storage without any extra...
HardwareLens
Simple ReadyOne page describing this computer, honest about everything it cannot see.
SensorDeck
Vertical ReadyLoads your machine for five minutes and shows whether it holds its speed.
DevicePulse
Pro ReadyLogs folder sizes on a schedule and shouts when one jumps more than 25% since last time.
Advanced & technical details Command-line builds, source code, checksums and a recorded session — for developers and IT teams
A working CLI prototype of the fleet-rollup engine: a collect agent per machine, then a rollup that merges every report into one view with mean, median and population standard deviation, flagging the machines that sit beyond a configurable z-score so an admin can see which box is the problem. Statistics independently re-derived and matched exactly. Real hardware sensors and SMART data need privileged OS APIs and are on the roadmap.
Recorded session
Naming status
Working name only — brand verdict **AVOID** (High). Collision: PC Health. Do not use as primary brand.
What it draws on
Existing paid software whose best ideas shaped this program: AIDA64 Extreme, HWiNFO Pro, Hard Disk Sentinel Professional, PassMark PerformanceTest.
Command line
There is nothing extra to install. The program you download is the command-line tool as well: give it arguments instead of double-clicking it and it runs as one, with its output on your terminal. The standalone builds below are the same engine on its own, for machines where you would rather not ship a window at all.
pchealth: no command given
pchealth 1.0.0 - fleet rollup for the Hardware Health Hub
Collect one health report per machine, then roll many reports up into a
single fleet view with statistical outlier detection, so the one bad machine
out of forty is obvious at a glance.
USAGE
pchealth collect --machine <name> --watch <dir> [--watch <dir> ...] --out <report.json>
pchealth rollup <report1.json> [report2.json ...] [--stddev-threshold N] [--json]
pchealth rollup --dir <reports-dir> [--stddev-threshold N] [--json]
pchealth help
COMMANDS
collect Write ONE machine's report: machine name, hostname, timestamp,
OS/arch, logical CPU count (runtime.NumCPU), Go runtime memory
stats, and the recursive on-disk byte usage of each --watch path.
This is the agent you run on every machine.
rollup Merge N reports into one fleet view: a per-machine table, fleet
totals, and the mean, median and population standard deviation of
per-machine disk usage, with machines further than
--stddev-threshold standard deviations from the fleet mean
flagged as OUTLIERS.
COLLECT FLAGS
--machine <name> Machine label recorded in the report (required).
--watch <dir> Directory (or file) to measure; repeat for several.
--out <file> Where to write the JSON report; "-" writes to stdout.
ROLLUP FLAGS
--dir <dir> Ingest every *.json in this directory (repeatable).
--stddev-threshold N Outlier cutoff in standard deviations (default 2.0).
--json Emit the whole rollup as JSON instead of a table.
NOTES
Flags may appear before or after positional arguments.
Unreadable or malformed reports are skipped with a reason; the remaining
reports still roll up. If no report can be read at all, pchealth exits 1.
Standard deviation is the population standard deviation (divide by n).
...Recorded from the shipped binary, not written by hand.
Source
Every file the program is built from:
console.go · console_test.go · guided.go · main.go
SHA-256 checksums · build instructions & scope notes · full build plan