Working private release

HumWatch

See what the machine is doing before it becomes a mystery.

A self-hosted browser dashboard for the Windows and Linux computers around you. Watch the temperatures, load, memory, disks, fans, battery, and other useful signs without sending the readings into someone else’s cloud.

HumWatch browser dashboard showing local CPU, GPU, memory, and battery readings
The dashboard is served by the machine being watched.

HumWatch is a self-hosted hardware monitor for people running their own Windows or Linux machines, showing CPU, GPU, memory, and other readings in a browser dashboard served by the machine itself. It has working release builds for both platforms, but the repository and downloads are private right now, so the public cannot get it yet.

Windows and Linux
Local history
Private build

When the fan suddenly has opinions

The useful signs, in one place.

HumWatch is for the computers you care about personally. It helps answer “what is this box doing?” without pretending to replace a data center monitoring stack.

CPU and GPU

Load, clocks, temperatures, power, video memory, and fans when the hardware exposes them.

Memory and disks

RAM, swap, storage use, read and write activity, and the processes taking the biggest bite.

Network and battery

Transfer rates, cumulative traffic, charge level, health, rate, and voltage where available.

A moment is useful. A pattern is better.

Seven-day history lives in local SQLite.

Readings roll into a database on the machine and age out after seven days. The dashboard can show the spike that already passed, not only whatever the sensor happens to say right now.

Real dashboard, real readings

Move from the whole machine to the stubborn part.

HumWatch overview dashboard with live local hardware readings
See the machine’s main signals together.
HumWatch machines view listing chosen computers and their current status
Keep the other computers you chose within reach.
HumWatch GPU page with temperature, utilization, memory, and power charts
Follow the component that is making the most noise.

One machine first

Add the other boxes you choose.

Each HumWatch machine serves its own dashboard. You can add other instances to a machines view and reach them over the LAN or private network you already run. Nothing requires a central HumWatch cloud account.

Local does not mean careless

The dashboard still gets a locked door.

Current HumWatch builds require HTTPS and a bearer token, including development setup. The telemetry database stays on the machine. There is no HumWatch account and no hosted service receiving the readings.

Different machines, different sensors

Windows digs deeper. Linux reads what the system exposes.

Windows

Basic readings work through the bundled system layer. Advanced temperatures, voltages, fans, and GPU details use LibreHardwareMonitor, with PawnIO needed for full sensor access.

Linux

HumWatch reads the hardware and process information Linux exposes through its normal system interfaces. Available detail depends on the machine and drivers.

Before you point it at your rig

Questions worth answering plainly

What does HumWatch monitor?

HumWatch tracks CPU and GPU load, clocks, temperatures, and power, along with memory, disk activity, network traffic, and battery health where the hardware exposes it. Windows gets deeper sensor detail through LibreHardwareMonitor and PawnIO. Linux reads whatever its own system interfaces expose, which varies by machine and drivers.

Does HumWatch work on Windows and Linux?

Yes. Basic Windows readings work through the bundled system layer, with LibreHardwareMonitor and PawnIO for deeper sensors. Linux reads hardware and process information through its normal system interfaces, with the available detail depending on the machine.

Where is HumWatch's data stored?

On the machine being watched. Readings roll into a local SQLite database and age out after seven days, and there is no HumWatch account or hosted service receiving them.

Can I watch more than one machine?

Yes. Each HumWatch instance serves its own dashboard, and you can add other machines to a machines view and reach them over the LAN or private network you already run. Nothing requires a central HumWatch cloud account.

Is HumWatch open to the internet?

HumWatch is built to be reached over the LAN or private network you already run, not opened to the internet by the app itself. Current builds require HTTPS and a bearer token, including during development setup, so the dashboard is never served without a lock on it.

Working build, private door

Public downloads are not open yet.

HumWatch has working Windows and Linux release artifacts, but the repository and downloads are private today. This page will not send ordinary visitors to a GitHub door they cannot open.

Back to the Home Lab