A · leads
Huginn
96.1
50,561 stars · MIT
Workflow Automation
Huginn leads by 3.3 · narrow
A · leads
96.1
50,561 stars · MIT
B
92.8
27,230 stars · MIT
Huginn versus vagrant is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Ruby. The composite score is 96.1 for Huginn and 92.8 for vagrant.
Huginn has 50,561 GitHub stars to vagrant's 27,230, a gap of 23,331 (1.86×). Forks are 4,356 for Huginn and 4,491 for vagrant. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 100.
Push history: Huginn was last pushed on 09 November 2026 (8 days ago), and vagrant was last pushed on 12 November 2026 (5 days ago). Open issues stand at 692 for Huginn (0.014 per star) and 760 for vagrant (0.028 per star). Issue-health scores are 84 and 70; activity scores are 92 and 92.
Both Huginn and vagrant are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Workflow Automation, both Huginn (50,561 stars) and vagrant (27,230 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, vagrant is open source.
The lead is split. Huginn is furthest ahead on issue health (84 to 70), while vagrant is furthest ahead on fork community (100 to 100). Choose the dimension a rollout cannot compromise on.
Huginn finishes ahead at 96.1 against vagrant at 92.8, a 3.3 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 | vagrant |
|---|---|---|
| GitHub stars | 50,561 | 27,230 |
| Forks | 4,356 | 4,491 |
| Open issues | 692 | 760 |
| Adoption | 100 | 94 |
| Activity | 92 | 92 |
| Community | 100 | 100 |
| Issue health | 84 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.1 | 92.8 |
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.
Vagrant is a tool for building and distributing development environments.
Huginn has more GitHub stars: 50,561 versus 27,230 for vagrant. The gap is 23,331 stars.
vagrant was pushed more recently: 12 November 2026 versus 09 November 2026 for Huginn. That is 3 days apart.
Yes. This catalog marks both Huginn and vagrant 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. vagrant 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Huginn scores 96.1 and vagrant scores 92.8. This page calls that a narrow lead for Huginn.