A
Huginn
91.7
50,561 stars · MIT
Workflow Automation
paperclip leads by 3.0 · narrow
A
91.7
50,561 stars · MIT
B · leads
94.7
114,484 stars · MIT
Huginn versus paperclip 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; paperclip is written mainly in TypeScript. The composite score is 91.7 for Huginn and 94.7 for paperclip.
paperclip has 114,484 GitHub stars to Huginn's 50,561, a gap of 63,923 (2.26×). Forks are 4,356 for Huginn and 18,987 for paperclip. On the log scale used inside this pair, adoption is 93 versus 100, and the fork community is 85 versus 100.
Push history: Huginn was last pushed on 09 November 2026 (8 days ago), and paperclip was last pushed on 17 November 2026 (0 days ago). Open issues stand at 692 for Huginn (0.014 per star) and 6,806 for paperclip (0.059 per star). Issue-health scores are 84 and 52; activity scores are 92 and 100.
Both Huginn and paperclip 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 paperclip (114,484 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, paperclip is open source.
The lead is split. Huginn is furthest ahead on issue health (84 to 52), while paperclip is furthest ahead on fork community (100 to 85). Choose the dimension a rollout cannot compromise on.
paperclip finishes ahead at 94.7 against Huginn at 91.7, a 3.0 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 | paperclip |
|---|---|---|
| GitHub stars | 50,561 | 114,484 |
| Forks | 4,356 | 18,987 |
| Open issues | 692 | 6,806 |
| Adoption | 93 | 100 |
| Activity | 92 | 100 |
| Community | 85 | 100 |
| Issue health | 84 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.7 | 94.7 |
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.
The open-source app everyone uses to manage agents at work
paperclip has more GitHub stars: 114,484 versus 50,561 for Huginn. The gap is 63,923 stars.
paperclip 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 paperclip 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. paperclip 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.
paperclip scores 94.7 and Huginn scores 91.7. This page calls that a narrow lead for paperclip.