A · leads
Huginn
96.2
50,561 stars · MIT
Workflow Automation
Huginn leads by 11.2 · clear
A · leads
96.2
50,561 stars · MIT
B
85.0
3,025 stars · Apache-2.0
Huginn versus lowdefy 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; lowdefy is written mainly in JavaScript. The composite score is 96.2 for Huginn and 85.0 for lowdefy.
Huginn has 50,561 GitHub stars to lowdefy's 3,025, a gap of 47,536 (16.71×). Forks are 4,356 for Huginn and 188 for lowdefy. On the log scale used inside this pair, adoption is 100 versus 74, and the fork community is 100 versus 63.
Push history: Huginn was last pushed on 09 November 2026 (8 days ago), and lowdefy was last pushed on 17 November 2026 (0 days ago). Open issues stand at 692 for Huginn (0.014 per star) and 15 for lowdefy (0.005 per star). Issue-health scores are 84 and 96; 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. lowdefy is listed as Apache-2.0, 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. License scores in this pair are 96 for Huginn and 96 for lowdefy. This is a procurement signal, not legal advice.
In Workflow Automation, both Huginn (50,561 stars) and lowdefy (3,025 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, lowdefy is open source.
The lead is split. Huginn is furthest ahead on fork community (100 to 63), while lowdefy is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
Huginn finishes ahead at 96.2 against lowdefy at 85.0, a 11.2 point clear 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 | lowdefy |
|---|---|---|
| GitHub stars | 50,561 | 3,025 |
| Forks | 4,356 | 188 |
| Open issues | 692 | 15 |
| Adoption | 100 | 74 |
| Activity | 92 | 100 |
| Community | 100 | 63 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.2 | 85.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.
Build apps that AI can generate, humans can review, and teams can maintain. Config that works between code and natural language.
Huginn has more GitHub stars: 50,561 versus 3,025 for lowdefy. The gap is 47,536 stars.
lowdefy 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 lowdefy 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. lowdefy is listed as Apache-2.0, 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Huginn scores 96.2 and lowdefy scores 85.0. This page calls that a clear lead for Huginn.