HardwareLens
One page describing this computer, honest about everything it cannot see.
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 HardwareLens
One page describing this computer, honest about everything it cannot see.
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, HardwareLens is included in every plan along with the rest of the range.
Run it, read it, send it to whoever is helping you
HardwareLens prints one page in plain English. Hostname, operating system, processor family, how many logical CPUs exist and how many this program may actually use. A short speed check with a rating in words. What’s inside any folders you named with --watch. Then a diagnostic section where every remark is printed alongside the number it was derived from, on an “evidence:” line.
The speed check does fixed work
The default run performs exactly 189,235,200 operations on one core and 378,470,400 across all of them, every single time. Those counts are compile-time constants, so only the elapsed time varies. That’s what makes it a measurement rather than a printed constant, and it’s why a busy machine scores lower.
What it refuses to guess
No CPU model name, no clock speed, no physical core count. No total RAM, no GPU, no temperatures, no fan speeds, no SMART health, no battery cycles, no free disk space. The Go standard library cannot read any of that portably, so the report omits them and ends with a section naming every one, rather than leaving a silence that reads like a clean bill of health.
The memory section is this program’s own usage, and labels itself that way.
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...
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.
PCHealth
Team ReadyForty workstations, one sorted table, and the odd one out flagged for you.
Advanced & technical details Command-line builds, source code, checksums and a recorded session — for developers and IT teams
A working prototype of the one-command system report card: what this machine is, a real CPU speed check, what is filling the folders you name, and plain-English observations derived from those measurements. Every fact was cross-checked against nproc, uname, hostname and go version. Crucially it omits rather than guesses — CPU model, total RAM, GPU, temperatures and SMART are listed as things it cannot see without native OS APIs, and a source audit confirms no invented hardware strings.
Naming status
Working name only — brand verdict **RENAME** (High). Collision: Hardware Lens. Rename before launch.
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.
hardwarelens: no command given
hardwarelens 1.0.0 - plain-English system report card
One command, one readable page: what this computer is, how fast it measured,
what is filling up the folders you point it at, and anything about those
numbers worth mentioning. Written for people who are not sysadmins, and
exportable with --out so you can hand it to whoever is helping you.
USAGE
hardwarelens report [--watch <dir> ...] [--out <file>] [--json]
hardwarelens inventory [--json]
hardwarelens bench [--seconds N] [--json]
hardwarelens help
COMMANDS
report The report card. Machine facts, a short CPU speed check, this
tool's own memory use, the contents of every --watch path, and a
plain-English diagnostic section in which every remark is
derived from a number printed elsewhere in the same report.
inventory The static facts only - hostname, OS, architecture, logical CPU
count, GOMAXPROCS, Go runtime. No benchmark, so it is instant.
bench The CPU speed check on its own.
REPORT FLAGS
--watch <dir> Directory (or single file) to measure; repeat for several.
Measures total bytes, file count and the largest file.
--out <file> Also write the report to this file. "-" means stdout.
This is the ONLY file hardwarelens ever writes.
--json Emit machine-readable JSON instead of the printed page.
BENCH FLAGS
--seconds N Run the timed variant for about N seconds (0 < N <= 60)
instead of the fixed workload. Optional.
--json Emit JSON instead of text.
WHAT THE SPEED CHECK MEASURES
Rounds of 64-bit integer mixing over a 64.0 KiB buffer: 270,336 mix operations per
round, 700 rounds single-threaded and 1,400 rounds spread over all
...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