Stats

Stats exists because people want always-on telemetry without paying for iStat Menus or living inside Activity Monitor. It is a Swift menu-bar app with modular widgets, MIT licensing, and a maintainer (Serhiy Mytrovtsiy / exelban) who still ships frequent builds. In July 2026, v3.0.9 continued that pattern with updater, battery capacity, and support-window fixes. Apple Silicon support is not a checkbox; it is ongoing sensor mapping work. 2026 notes call out M5 super-core detection and an SMAppService migration for the SMC daemon. When a new chip ships, expect a lag before every temperature key is pretty. The GitHub issue list is where that lag is visible. Tahoe’s menu-bar privacy controls created a support pattern: icons ‘disappear’ until the user enables Stats in System Settings → Menu Bar. That is an OS policy change, not a corrupted install. Document it for anyone you help upgrade. Install from GitHub Releases or brew install --cask stats. Prefer those channels over random reupload sites. Disable modules you do not read if you care about energy impact; the project documents that Sensors and Bluetooth can cost more than a simple CPU meter. Fan control remains legacy and not maintained. When you compare Stats with iStat Menus, decide whether you need long historical graphs and extra polish. If the answer is no, the free tool covers the daily job. If you present metrics on stream or want finer theme control, paid still has a lane. Either way, try Stats for a week on a real workload before spending money. For multi-Mac households, Homebrew becomes the easy fleet move: same cask, same defaults, optional brewfile. Developers imaging new MacBooks can drop Stats into the bootstrap script next to their editor and terminal. That ubiquity is how a free utility becomes infrastructure. Operational detail matters once Stats is always running. Put CPU and memory on the left of your menu-bar cluster if those are the metrics you actually act on. Hide disks if you never run out of space. On a 14-inch laptop the menu bar is scarce real estate; three well-chosen modules beat eight tiny graphs you ignore. Permission prompts can look scary because menu-bar monitors touch system information. Read what macOS asks for, grant what you need for the modules you enabled, and deny the rest. On Tahoe, the Menu Bar privacy list is a second gate after the usual Privacy & Security panes. If you reinstall often, expect to re-enable the toggle. Update strategy should be boring. Homebrew users can fold Stats into a weekly brew upgrade ritual. GitHub Releases users should glance at notes for SMC daemon changes and battery fixes before installing on a machine mid-render. v3.0.x has moved quickly enough that skipping six releases at once can hide which fix solved your issue. Comparing open source to paid tools is not only about money. iStat Menus funds support and polish; Stats funds itself on maintainer time and donations. If you depend on Stats in a studio, occasional donations keep the lights on without a subscription negotiation with finance. If you need a vendor to call when something breaks, paid still has a place. Sensor accuracy is a living document. After an Apple Silicon generation ships, community-captured keys and maintainer merges close gaps. If a temperature reads absurdly, check issues before assuming your machine is on fire. Likewise, Bluetooth device battery widgets depend on devices that expose that data; not every headset will show a perfect percentage. Developers debugging runaway CI agents on a Mac mini can leave Stats up on a shared display as a cheap status board. Combined with Activity Monitor only when something looks wrong, it reduces constant window switching. For teachers imaging lab Macs, a free MIT tool with a cask is easier to justify than seat-licensed monitors. Text-only widgets help on dense status bars where graphs become noise. Combined modules in recent 3.x work try to preserve position so upgrades do not scramble your carefully ordered icons. Battery max-capacity readouts help decide when a laptop repair is worth discussing, not just when percentage hits 10%. Multi-time-zone clocks are easy to overlook but useful for remote teams that live in three continents of standups. If Stats conflicts with another menu-bar meter, disable overlapping modules rather than running two CPU graphs forever. Public IP widgets need network; turn them off on locked-down networks that flag outbound checks. Teachers can use the CPU graph as a teaching aid when explaining why too many Chrome profiles feel slow. Open source means you can audit code paths that read SMC data if your security team requires it. Do not run untrusted forks that re-enable aggressive fan control without understanding thermal risk. Pair Stats with intentional focus modes so notifications from other apps do not crowd the same menu corner. On stage demos, hide network totals if they reveal internal hostnames or VPN states you did not mean to show. Homebrew cask tokens make fleet uninstalls as easy as installs when a lab changes standards. Studio Macs that render overnight benefit from temperature history the next morning even if nobody watched the graph live. Students writing papers on aging MacBooks use battery watts to decide whether a library outlet hunt is worth interrupting flow. Sysadmins can screenshot the menu bar during a ticket to prove CPU was pegged rather than relying on user adjectives like 'slow'. When Bluetooth widgets show nothing, confirm the accessory exposes battery status; the empty row is often the device, not Stats. People who dual-boot or use virtual machines should remember Stats reports the macOS host view, not guest CPU maps inside Parallels. If you stage demos, switch to text widgets so a spike does not become a distracting animation behind your slides. Open-source licensing means internal forks for locked-down environments are legally simpler than cracking a paid suite. Keep release notes for v3.0.2 and v3.0.9 handy when explaining M5 and updater fixes to teammates who skip changelogs. A minimalist setup might show only Battery on a phone-free travel day and add CPU again when back at the desk. Network totals since boot reset on reboot; do not treat them as monthly ISP counters. GPU readouts help creators notice whether a export is actually using acceleration or silently falling back. Combined with Console.app only when needed, Stats stays the calm first look rather than a full forensics suite. Menu-bar real estate fights with other utilities: VPN status, cloud sync, password managers, and chat badges. Stats earns its pixels only if you look at it. If a module has not changed a decision in a month, turn it off. The app is modular for that reason. Apple Silicon power states make watt readouts educational. You can see a browser with dozens of tabs cost more than an idle IDE, then close the tabs and watch the number drop. That feedback loop is more persuasive than generic advice to 'close apps.' Thermal paste myths flourish online. Stats will not tell you to repaste a MacBook; it will tell you temperatures under load. Use that as an input to Apple service decisions, not as a DIY license for voiding coverage.