A · leads
Huginn
96.2
50,561 stars · MIT
Workflow Automation
Huginn leads by 6.8 · narrow
A · leads
96.2
50,561 stars · MIT
B
89.4
11,990 stars · Apache-2.0
Huginn versus robotframework 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; robotframework is written mainly in Python. The composite score is 96.2 for Huginn and 89.4 for robotframework.
Huginn has 50,561 GitHub stars to robotframework's 11,990, a gap of 38,571 (4.22×). Forks are 4,356 for Huginn and 2,589 for robotframework. On the log scale used inside this pair, adoption is 100 versus 87, and the fork community is 100 versus 94.
Push history: Huginn was last pushed on 09 November 2026 (8 days ago), and robotframework was last pushed on 11 November 2026 (6 days ago). Open issues stand at 692 for Huginn (0.014 per star) and 322 for robotframework (0.027 per star). Issue-health scores are 84 and 70; activity scores are 92 and 92.
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. robotframework 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 robotframework. This is a procurement signal, not legal advice.
In Workflow Automation, both Huginn (50,561 stars) and robotframework (11,990 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, robotframework is open source.
Huginn is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 14 points (84 vs 70), and the tightest is self-hosting at 0 points (100 vs 100).
Huginn finishes ahead at 96.2 against robotframework at 89.4, a 6.8 point narrow 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 | robotframework |
|---|---|---|
| GitHub stars | 50,561 | 11,990 |
| Forks | 4,356 | 2,589 |
| Open issues | 692 | 322 |
| Adoption | 100 | 87 |
| Activity | 92 | 92 |
| Community | 100 | 94 |
| Issue health | 84 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.2 | 89.4 |
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.
Generic automation framework for acceptance testing and RPA
Huginn has more GitHub stars: 50,561 versus 11,990 for robotframework. The gap is 38,571 stars.
robotframework was pushed more recently: 11 November 2026 versus 09 November 2026 for Huginn. That is 2 days apart.
Yes. This catalog marks both Huginn and robotframework 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. robotframework 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 robotframework scores 89.4. This page calls that a narrow lead for Huginn.