A · leads
Huginn
96.2
50,561 stars · MIT
Workflow Automation
Huginn leads by 22.2 · decisive
A · leads
96.2
50,561 stars · MIT
B
74.0
2,919 stars · license n/a
Huginn versus LoopForge is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Huginn is written mainly in Ruby; LoopForge is written mainly in Go. The composite score is 96.2 for Huginn and 74.0 for LoopForge.
Huginn has 50,561 GitHub stars to LoopForge's 2,919, a gap of 47,642 (17.32×). Forks are 4,356 for Huginn and 423 for LoopForge. On the log scale used inside this pair, adoption is 100 versus 74, and the fork community is 100 versus 72.
Push history: Huginn was last pushed on 09 November 2026 (8 days ago), and LoopForge was last pushed on 17 November 2026 (0 days ago). Open issues stand at 692 for Huginn (0.014 per star) and 176 for LoopForge (0.060 per star). Issue-health scores are 84 and 52; activity scores are 92 and 100.
Huginn is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. LoopForge is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for Huginn and 30 for LoopForge. This is a procurement signal, not legal advice.
In Workflow Automation, both Huginn (50,561 stars) and LoopForge (2,919 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: Huginn is open source, LoopForge is unpriced in this catalog.
The lead is split. Huginn is furthest ahead on license flexibility (96 to 30), while LoopForge is furthest ahead on recent activity (100 to 92). Choose the dimension a rollout cannot compromise on.
Huginn finishes ahead at 96.2 against LoopForge at 74.0, a 22.2 point decisive margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | Huginn | LoopForge |
|---|---|---|
| GitHub stars | 50,561 | 2,919 |
| Forks | 4,356 | 423 |
| Open issues | 692 | 176 |
| Adoption | 100 | 74 |
| Activity | 92 | 100 |
| Community | 100 | 72 |
| Issue health | 84 | 52 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 96.2 | 74.0 |
Huginn is a self-hosted agent system that watches the web and triggers actions from events. It predates the current wave of LLM agents and is closer to a personal IFTTT you run yourself.
Self-hosted workflows for coding-agent delivery. Orchestrate CodeBuddy, Codex and Claude Code with scripts and human approval gates. Includes Local workflows for coding assistants.
Huginn has more GitHub stars: 50,561 versus 2,919 for LoopForge. The gap is 47,642 stars.
LoopForge was pushed more recently: 17 November 2026 versus 09 November 2026 for Huginn. That is 8 days apart.
Yes. This catalog marks both Huginn and LoopForge as self-hostable. Confirm each project's deploy docs before you plan a migration.
Huginn is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. LoopForge is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Huginn scores 96.2 and LoopForge scores 74.0. This page calls that a decisive lead for Huginn.