CoreFreq vs HYDRA
CoreFreq
cyring.fr
HYDRA
patreon.comSide by side
| Figure | CoreFreq | HYDRA |
|---|---|---|
| Price from | Free | $3/mo |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Windows | — | Yes |
| Linux | Yes | — |
| API | — | Yes |
| Self-hosted | Yes | — |
| Plans published | 1 | 3 |
| Spec score · PC Overclocking Software | 7.8 (#11) | 8.3 (#8) |
| Compatibility limit | The README cautions that some virtual machines do not provide access to registers used by the driver. | The 1.8G release says eCLK control requires corresponding motherboard support. |
| Monitoring | It retrieves CPU frequencies and ratios, performance counters, instructions per cycle, C-states, temperature, and documented core-voltage readings. | The monitoring interface provides separate CPU, CCD, DRAM and GPU views plus history charts and statistics for numeric sensors. |
| Purpose | CoreFreq is CPU monitoring software with BIOS-like functionalities for 64-bit processors. | HYDRA is a Windows toolkit for PC hardware diagnostics, monitoring, and tuning. |
Plans
HYDRA
- Project Supporter$3 a month
- Development Supporter$5 a month
- HYDRA PRO Early Access$15 a month
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.