A · level
bruno
95.8
48,427 stars · MIT
Workflow Automation
Too close to call · 95.8 to 96.2
A · level
95.8
48,427 stars · MIT
B · level
96.2
50,561 stars · MIT
bruno versus Huginn is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. bruno is written mainly in JavaScript; Huginn is written mainly in Ruby. The composite score is 95.8 for bruno and 96.2 for Huginn.
Huginn has 50,561 GitHub stars to bruno's 48,427, a gap of 2,134 (1.04×). Forks are 3,115 for bruno and 4,356 for Huginn. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 96 versus 100.
Push history: bruno was last pushed on 17 November 2026 (0 days ago), and Huginn was last pushed on 09 November 2026 (8 days ago). Open issues stand at 2,002 for bruno (0.041 per star) and 692 for Huginn (0.014 per star). Issue-health scores are 70 and 84; activity scores are 100 and 92.
Both bruno and Huginn 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 bruno (48,427 stars) and Huginn (50,561 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: bruno is open source, Huginn is open source.
The lead is split. bruno is furthest ahead on recent activity (100 to 92), while Huginn is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
Composite score: bruno 95.8, Huginn 96.2. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | bruno | Huginn |
|---|---|---|
| GitHub stars | 48,427 | 50,561 |
| Forks | 3,115 | 4,356 |
| Open issues | 2,002 | 692 |
| Adoption | 100 | 100 |
| Activity | 100 | 92 |
| Community | 96 | 100 |
| Issue health | 70 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 95.8 | 96.2 |
Opensource IDE For Exploring and Testing API's (lightweight alternative to Postman/Insomnia)
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.
Huginn has more GitHub stars: 50,561 versus 48,427 for bruno. The gap is 2,134 stars.
bruno was pushed more recently: 17 November 2026 versus 09 November 2026 for Huginn. That is 8 days apart.
Yes. This catalog marks both bruno and Huginn as self-hostable. Confirm each project's deploy docs before you plan a migration.
bruno 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Neither tool clears a one-point margin. bruno scores 95.8 and Huginn scores 96.2.