A · leads
Huginn
96.2
50,561 stars · MIT
Workflow Automation
Huginn leads by 7.1 · clear
A · leads
96.2
50,561 stars · MIT
B
89.1
23,434 stars · AGPL-3.0
Huginn versus skyvern 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; skyvern is written mainly in Python. The composite score is 96.2 for Huginn and 89.1 for skyvern.
Huginn has 50,561 GitHub stars to skyvern's 23,434, a gap of 27,127 (2.16×). Forks are 4,356 for Huginn and 2,246 for skyvern. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 92.
Push history: Huginn was last pushed on 09 November 2026 (8 days ago), and skyvern was last pushed on 17 November 2026 (0 days ago). Open issues stand at 692 for Huginn (0.014 per star) and 301 for skyvern (0.013 per star). Issue-health scores are 84 and 84; 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. skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for Huginn and 52 for skyvern. This is a procurement signal, not legal advice.
In Workflow Automation, both Huginn (50,561 stars) and skyvern (23,434 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, skyvern is open source.
The lead is split. Huginn is furthest ahead on license flexibility (96 to 52), while skyvern is furthest ahead on recent activity (100 to 92). Choose the dimension a rollout cannot compromise on.
Huginn finishes ahead at 96.2 against skyvern at 89.1, a 7.1 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 | skyvern |
|---|---|---|
| GitHub stars | 50,561 | 23,434 |
| Forks | 4,356 | 2,246 |
| Open issues | 692 | 301 |
| Adoption | 100 | 93 |
| Activity | 92 | 100 |
| Community | 100 | 92 |
| Issue health | 84 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 96.2 | 89.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.
Automate browser based workflows with AI
Huginn has more GitHub stars: 50,561 versus 23,434 for skyvern. The gap is 27,127 stars.
skyvern 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 skyvern 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. skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Huginn scores 96.2 and skyvern scores 89.1. This page calls that a clear lead for Huginn.