CoreFreq vs ZenStates
CoreFreq
cyring.frZenStates
github.comSide by side
| Figure | CoreFreq | ZenStates |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Windows | — | Yes |
| Linux | Yes | — |
| Self-hosted | Yes | — |
| Plans published | 1 | 0 |
| Spec score · PC Overclocking Software | 7.8 (#11) | 6.4 (#30) |
| Installation | The README documents building from source and distribution options including ArchLinux AUR, Gentoo, Debian, Ubuntu, TUXEDO, Fedora, AlmaLinux, and Rocky Linux. | The application is distributed as a ZIP containing the GUI and service executables, and the README describes extracting it and running ZenStates.exe. |
| License | The repository identifies the software as GPL-2.0 licensed. | The repository identifies its license as GPL-3.0. |
| Purpose | CoreFreq is CPU monitoring software with BIOS-like functionalities for 64-bit processors. | ZenStates is a Windows application for controlling AMD Ryzen CPU settings through SMU commands. |
Plans
In their own words
CoreFreq
CoreFreq is free Linux CPU-monitoring software with BIOS-like controls for 64-bit processors. It reads frequencies, ratios, performance counters, instructions per cycle, C-states, temperature, and documented core-voltage readings. The interface shows processor features, brand and architecture strings, plus a topology map including caches. Its driver exposes controls for Turbo Boost, power management, thermal limits, prefetchers, and hardware-controlled performance states. A daemon and command-line client provide monitoring views and JSON-encoded system information. Listed architectures include Intel and AMD families, Arm A64, RISC-V RV64, and PowerPC64 LE. Requirements include Linux kernel 3.3 or newer and GNU C Library. Installation can use source builds or packages for several distributions. The project is GPL-2.0 licensed and uses shared memory between its kernel module and user-space component. Some virtual machines may hide required registers. Driver signing is required when kernel signature verification is enabled. The interface renders best in ASCII or VT100 terminals.