A · leads
Huginn
96.2
50,561 stars · MIT
Workflow Automation
Huginn leads by 2.8 · narrow
A · leads
96.2
50,561 stars · MIT
B
93.4
14,334 stars · Apache-2.0
Huginn versus nanobrowser 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; nanobrowser is written mainly in TypeScript. The composite score is 96.2 for Huginn and 93.4 for nanobrowser.
Huginn has 50,561 GitHub stars to nanobrowser's 14,334, a gap of 36,227 (3.53×). Forks are 4,356 for Huginn and 1,540 for nanobrowser. On the log scale used inside this pair, adoption is 100 versus 88, and the fork community is 100 versus 88.
Push history: Huginn was last pushed on 09 November 2026 (8 days ago), and nanobrowser was last pushed on 17 November 2026 (0 days ago). Open issues stand at 692 for Huginn (0.014 per star) and 62 for nanobrowser (0.004 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. nanobrowser 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 nanobrowser. This is a procurement signal, not legal advice.
In Workflow Automation, both Huginn (50,561 stars) and nanobrowser (14,334 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, nanobrowser is open source.
The lead is split. Huginn is furthest ahead on fork community (100 to 88), while nanobrowser is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
Huginn finishes ahead at 96.2 against nanobrowser at 93.4, a 2.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 | nanobrowser |
|---|---|---|
| GitHub stars | 50,561 | 14,334 |
| Forks | 4,356 | 1,540 |
| Open issues | 692 | 62 |
| Adoption | 100 | 88 |
| Activity | 92 | 100 |
| Community | 100 | 88 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.2 | 93.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.
Open-source AI agent for web automation. Use your real, logged-in browser to automate daily tasks.
Huginn has more GitHub stars: 50,561 versus 14,334 for nanobrowser. The gap is 36,227 stars.
nanobrowser 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 nanobrowser 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. nanobrowser 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 nanobrowser scores 93.4. This page calls that a narrow lead for Huginn.