A · leads
Huginn
96.2
50,561 stars · MIT
Workflow Automation
Huginn leads by 20.7 · decisive
A · leads
96.2
50,561 stars · MIT
B
75.5
12,531 stars · license n/a
Huginn versus keep 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; keep is written mainly in Python. The composite score is 96.2 for Huginn and 75.5 for keep.
Huginn has 50,561 GitHub stars to keep's 12,531, a gap of 38,030 (4.03×). Forks are 4,356 for Huginn and 1,555 for keep. On the log scale used inside this pair, adoption is 100 versus 87, and the fork community is 100 versus 88.
Push history: Huginn was last pushed on 09 November 2026 (8 days ago), and keep was last pushed on 16 November 2026 (1 day ago). Open issues stand at 692 for Huginn (0.014 per star) and 708 for keep (0.056 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. keep 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 keep. This is a procurement signal, not legal advice.
Only Huginn is marked self-hostable here (50,561 stars, deploy score 100). keep is not (12,531 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: Huginn is open source, keep is unpriced in this catalog.
The lead is split. Huginn is furthest ahead on license flexibility (96 to 30), while keep is furthest ahead on recent activity (100 to 92). Choose the dimension a rollout cannot compromise on.
Huginn finishes ahead at 96.2 against keep at 75.5, a 20.7 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 | keep |
|---|---|---|
| GitHub stars | 50,561 | 12,531 |
| Forks | 4,356 | 1,555 |
| Open issues | 692 | 708 |
| Adoption | 100 | 87 |
| Activity | 92 | 100 |
| Community | 100 | 88 |
| Issue health | 84 | 52 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 96.2 | 75.5 |
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.
The open-source AIOps and alert management platform
Huginn has more GitHub stars: 50,561 versus 12,531 for keep. The gap is 38,030 stars.
keep was pushed more recently: 16 November 2026 versus 09 November 2026 for Huginn. That is 7 days apart.
Only Huginn is marked self-hostable. keep is not.
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. keep 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 keep scores 75.5. This page calls that a decisive lead for Huginn.