head to head · open source

huginn vs auto-cpufreq

huginn has 49,969 GitHub stars, 4,299 forks, 698 open issues and last shipped today. auto-cpufreq has 7,760 stars, 356 forks, 79 open issues and last shipped 6 days ago. huginn leads on adoption by 544% (49,969 vs 7,760 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.

huginn ★ 50K auto-cpufreq ★ 7.8K category Infrastructure & Operations

← all 8884 open source comparisons

Side by side

huginn auto-cpufreq
GitHub stars ★ 50K ★ 7.8K
License MIT GPL-3.0
Written in Ruby Python
Last push 2026-09-18 2026-09-12
Forks ⑂ 4.3K ⑂ 356
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

full huginn profile →

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

full auto-cpufreq profile →

About huginn

Huginn is an open source system for building agents that perform automated tasks online, written in Ruby and released under the MIT license. Its agents read the web, watch for events, and take actions on the user's behalf. Internally, agents create and consume events that propagate along a directed graph, which means one agent's output becomes another agent's input and a chain of small steps can be composed into a larger workflow. The project lives in the Ruby ecosystem and is distributed as an official Docker image or installed locally from a forked repository.

read the full huginn overview →

About auto-cpufreq

auto cpufreq is a GPL 3.0 Python daemon and command line tool that watches a Linux laptop's battery state, CPU usage, CPU temperature, and system load, then adjusts CPU frequency and power settings automatically for users who want longer battery life without giving up responsiveness.

read the full auto-cpufreq overview →

More in Infrastructure & Operations

Immich ★ 114K Uptime Kuma ★ 91K worldmonitor ★ 87K mall ★ 85K NetData ★ 81K Elasticsearch ★ 78K

Related comparisons

uptime-kuma vs huginn worldmonitor vs huginn uptime-kuma vs worldmonitor uptime-kuma vs netdata uptime-kuma vs grafana worldmonitor vs netdata worldmonitor vs grafana netdata vs grafana immich vs paperless-ngx immich vs ceph immich vs filestash immich vs garage immich vs storj immich vs alarik immich vs spinifex paperless-ngx vs ceph mall vs prometheus mall vs nocodb mall vs etcd mall vs dbeaver mall vs orm prometheus vs nocodb mall vs milvus mall vs tidb

More Monitoring & Observability projects

Compare either of these against the rest of the Monitoring & Observability field.

huginn vs Uptime Kuma huginn vs worldmonitor huginn vs NetData huginn vs Grafana huginn vs Sentry huginn vs SigNoz huginn vs Grafana Loki huginn vs beszel huginn vs cilium huginn vs Apache SkyWalking huginn vs jaeger huginn vs Vector

Frequently asked questions

Is huginn or auto-cpufreq more popular?

huginn has 49,969 GitHub stars and auto-cpufreq has 7,760. 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 (49,969 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.