head to head · open source
huginn vs auto-cpufreq
huginn has 50,269 GitHub stars, 4,339 forks, 698 open issues and last shipped yesterday. auto-cpufreq has 7,859 stars, 360 forks, 79 open issues and last shipped 6 days ago. huginn leads on adoption by 540% (50,269 vs 7,859 stars). huginn is written in Ruby under MIT; auto-cpufreq is written in Python under GPL-3.0. huginn has attracted 9% as many forks as stars, auto-cpufreq 5%. huginn was the more recently maintained of the two, and both are self-hostable with no licence fee.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| huginn | auto-cpufreq | |
|---|---|---|
| GitHub stars | ★ 50K | ★ 7.9K |
| License | MIT | GPL-3.0 |
| Written in | Ruby | Python |
| Last push | 2026-11-02 | 2026-10-28 |
| Forks | ⑂ 4.3K | ⑂ 360 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick huginn if
- You weight community size — 50K stars and counting
- You want the MIT license terms
- Your stack matches Ruby
- You value the larger contributor base for long-term maintenance
pick auto-cpufreq if
- You want the auto-cpufreq feature set and don't need the biggest community
- You prefer the GPL-3.0 license terms
- Your stack matches Python
- You evaluated both and auto-cpufreq fits your workflow better
About huginn
What is Huginn? Huginn is a system for building agents that perform automated tasks for you online. They can read the web, watch for events, and take actions on your behalf. Huginn's Agents create and consume events, propagating them along a directed graph. Think of it as a hackable version of IFTTT or Zapier on your own server. You always know who has your data. You do. Here are some of the things that you can do with Huginn: Track the weather and get an email when it's going to rain (or snow) tomorrow ("Don't forget your umbrella!") List terms that you care about and receive email when their occurrence on…
read the full huginn overview →
About auto-cpufreq
auto cpufreq Automatic CPU speed & power optimizer for Linux. Actively monitors laptop battery state, CPU usage, CPU temperature, and system load, ultimately allowing you to improve battery life without making any compromises. For tl;dr folks: Youtube: From 10 day vacation project to 100k users: auto cpufreq v3 story Blog post: From 10 day vacation project to 100k users: auto cpufreq v3 story Youtube: auto cpufreq v2.0 release & demo of all available features and options Blog post: auto cpufreq v2.0 Youtube: auto cpufreq tool demo Blog post: auto cpufreq – Automatic CPU speed & power optimizer for Linux If…
read the full auto-cpufreq overview →
More in Infrastructure & Operations
Related comparisons
More Monitoring & Observability projects
Compare either of these against the rest of the Monitoring & Observability field.
Frequently asked questions
Is huginn or auto-cpufreq more popular?
huginn has 50,269 GitHub stars and auto-cpufreq has 7,859. huginn has the larger community by that measure.
Are huginn and auto-cpufreq free?
Both are open source. huginn is licensed under MIT and auto-cpufreq under GPL-3.0. Neither carries a licence fee.
What is the difference between huginn and auto-cpufreq?
huginn is written in Ruby and auto-cpufreq in Python. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, huginn or auto-cpufreq?
Choose huginn if you want the larger community (50,269 stars) or its MIT licence terms. Choose auto-cpufreq if its feature set, stack or GPL-3.0 licence fits better. Both are self-hostable.