Thrum

Thrum vs Stats: which Mac menu bar monitor fits?

Last reviewed: 19 November 2026.

Stats is a free, MIT-licensed menu bar monitor with modules for CPU, GPU, memory, disk, network, battery, sensors, Bluetooth devices and clocks, and it runs on macOS 12 and later. Thrum is a paid app for macOS 26 that focuses on processes: the eight busiest in five tabs, energy impact per app, and Quit or Force Quit. If you want free and broad, Stats is the obvious choice; Thrum is for finding and stopping the process behind a slowdown.

How do Thrum and Stats compare on the facts?

ThrumStats
Price$4.99 once, up to 3 Macs, 14-day trialFree
Source codeClosedOpen source, MIT license
macOS requiredmacOS 26 Tahoe or latermacOS 12 Monterey or later (beta macOS releases are not supported)
InstallDirect download; updates install themselvesDownload Stats.dmg from GitHub, or brew install stats
Latest version checked1.0v3.1.0, released 15 November 2026
Menu barCPU graph, CPU %, memory used, or CPU and memory bars; optional network speed itemOne item per module you turn on
Modules or tabsCPU, Memory, Energy, Network, DiskCPU, GPU, memory, disk, network, battery, fan control, sensors, Bluetooth, clock
Process listsTop 8 per tab, including root processes (CPU and memory)Not described in the README
Quit a processQuit or Force Quit, with confirmationNot described in the README
Temperatures and fansThermal state onlySensors module (temperature, voltage, power); fan control in legacy mode
AlertsBusy process, critical memory pressureNot described in the README

Stats facts are from the exelban/stats README and releases page on GitHub, checked in November 2026.

Where does Stats do more?

What does the Stats FAQ say about fan control and sensors?

The README is open about two limits. Fan control "is in legacy mode. It does not receive any updates or fixes"; it still works on older Macs, and the author accepts pull requests for it. Sensor readings are grouped as thermal zones rather than per-core values, because, in the README's words, "with each new SoC, Apple changes the sensor keys".

The same FAQ names Sensors and Bluetooth as the most costly modules for Stats' own CPU use and suggests turning them off if you do not need them. Thrum does not read sensors; it shows the thermal state macOS reports (nominal, fair, serious or critical).

Where does Thrum fit next to Stats?

Thrum answers a narrower question: which process is busy, and do you want to stop it. Each of its five tabs ranks the eight heaviest processes with app icons, and clicking one shows its PID, user, threads, CPU time, idle wake-ups and memory, with Quit, Force Quit, Reveal in Finder and Open in Activity Monitor buttons. The Energy tab ranks apps by energy impact, and the Network and Disk tabs show per-app rates.

Some people run Stats for sensors and clocks and Thrum for processes. Both are menu bar apps and can run side by side.

How can Thrum help?

Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes.

Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.

Questions

Is Stats safe to install?

It is open source, published on GitHub by its author, and installable through Homebrew. As with any download, get it from the GitHub releases page or Homebrew rather than a mirror.

Does Stats need an account?

No for the normal app. The README describes an optional headless install for remote Macs that enables a Remote module and links the Mac to an account on the developer's service.

Does Stats show which app uses the most CPU?

The README does not describe process lists. Check the current release if you need that, or use Activity Monitor or Thrum.

Sources