A · leads
Huginn
96.2
50,561 stars · MIT
Workflow Automation
Huginn leads by 27.1 · decisive
A · leads
96.2
50,561 stars · MIT
B
69.1
10,062 stars · LGPL-3.0
Huginn versus tpot 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; tpot is written mainly in Jupyter Notebook. The composite score is 96.2 for Huginn and 69.1 for tpot.
Huginn has 50,561 GitHub stars to tpot's 10,062, a gap of 40,499 (5.02×). Forks are 4,356 for Huginn and 1,557 for tpot. On the log scale used inside this pair, adoption is 100 versus 85, and the fork community is 100 versus 88.
Push history: Huginn was last pushed on 09 November 2026 (8 days ago), and tpot was last pushed on 11 September 2025 (431 days ago). Open issues stand at 692 for Huginn (0.014 per star) and 312 for tpot (0.031 per star). Issue-health scores are 84 and 70; activity scores are 92 and 16.
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. tpot is listed as LGPL-3.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. License scores in this pair are 96 for Huginn and 78 for tpot. This is a procurement signal, not legal advice.
In Workflow Automation, both Huginn (50,561 stars) and tpot (10,062 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, tpot is open source.
Huginn is ahead on every scored dimension that is not level. Level dimensions: self-hosting. The widest gap is recent activity at 76 points (92 vs 16), and the tightest is self-hosting at 0 points (100 vs 100).
Huginn finishes ahead at 96.2 against tpot at 69.1, a 27.1 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 | tpot |
|---|---|---|
| GitHub stars | 50,561 | 10,062 |
| Forks | 4,356 | 1,557 |
| Open issues | 692 | 312 |
| Adoption | 100 | 85 |
| Activity | 92 | 16 |
| Community | 100 | 88 |
| Issue health | 84 | 70 |
| License | 96 | 78 |
| Self-hosting | 100 | 100 |
| Composite | 96.2 | 69.1 |
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.
A Python Automated Machine Learning tool that optimizes machine learning pipelines using genetic programming.
Huginn has more GitHub stars: 50,561 versus 10,062 for tpot. The gap is 40,499 stars.
Huginn was pushed more recently: 09 November 2026 versus 11 September 2025 for tpot. That is 423 days apart.
Yes. This catalog marks both Huginn and tpot 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. tpot is listed as LGPL-3.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Huginn scores 96.2 and tpot scores 69.1. This page calls that a decisive lead for Huginn.