DevicePulse
Logs folder sizes on a schedule and shouts when one jumps more than 25% since last time.
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 DevicePulse
Logs folder sizes on a schedule and shouts when one jumps more than 25% since last time.
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, DevicePulse is included in every plan along with the rest of the range.
A snapshot is three things at once
devicepulse snapshot --watch /var/lib/docker --watch /home --history vitals.jsonl records the logical CPU count, this process’s own Go heap and sys bytes, and the real recursive on-disk size of each watched tree, then appends the lot as one JSON line.
The point is what happens on the second run. For each path, it finds that same path’s figure in the previous snapshot and computes the change. Above --warn-growth-pct (25 by default) you get a WARNING with the exact percentage and both byte counts. Below it, a normal line with the same real numbers. First run for a path says so rather than inventing a comparison. Growing from exactly zero warns and admits the percentage is undefined.
Exit code is 2 when any warning fired, so cron can act on it without parsing anything.
trend reads back the last N snapshots with min, max and latest per path. status takes the same measurements and writes no history at all.
Compared to DiskWatch
DiskWatch fits a regression and projects the date you run out. DevicePulse flags a jump between two consecutive samples. Different questions.
No temperatures, no fan speeds, no SMART, and no OS-level free-space figures. Those need privileged APIs.
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...
Advanced & technical details Command-line builds, source code, checksums and a recorded session — for developers and IT teams
A working CLI prototype of the persistent vitals-trend engine: snapshot disk usage across multiple watched paths on a schedule, get warned when any one path's growth crosses a configurable threshold since its last snapshot, and query min/max/latest trends over a JSON-lines history file. Real hardware sensors (temperature, fan speed, SMART data) need OS-privileged APIs and are on the roadmap.
Naming status
Working name only — brand verdict **AVOID** (Very High). Collision: Device Pulse. Rename completely.
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.
devicepulse - persistent multi-metric vitals-trend tracker
Usage:
devicepulse snapshot --watch <dir> [--watch <dir> ...] --history <file> [--warn-growth-pct N]
devicepulse trend --history <file> [--watch <dir>] [--last N] [--json]
devicepulse status --watch <dir> [--watch <dir> ...] [--json]
devicepulse help
Commands:
snapshot Take a vitals snapshot, append it to the history file, and warn
on watched-path disk-usage growth beyond the threshold since the
previous snapshot of the same path.
trend Read-only: print snapshot history and per-watched-path usage
over time, with min/max/latest across the shown window.
status Take one snapshot and print current vitals only. Never touches
any history file.
Run "devicepulse <command> -h" is not needed; flags are listed above.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