A · leads
paperclip
94.7
114,484 stars · MIT
Workflow Automation
paperclip leads by 29.4 · decisive
A · leads
94.7
114,484 stars · MIT
B
65.3
1,415 stars · BSD-3-Clause
paperclip versus utask is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. paperclip is written mainly in TypeScript; utask is written mainly in Go. The composite score is 94.7 for paperclip and 65.3 for utask.
paperclip has 114,484 GitHub stars to utask's 1,415, a gap of 113,069 (80.91×). Forks are 18,987 for paperclip and 105 for utask. On the log scale used inside this pair, adoption is 100 versus 62, and the fork community is 100 versus 47.
Push history: paperclip was last pushed on 17 November 2026 (0 days ago), and utask was last pushed on 29 July 2026 (111 days ago). Open issues stand at 6,806 for paperclip (0.059 per star) and 85 for utask (0.060 per star). Issue-health scores are 52 and 52; activity scores are 100 and 58.
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. utask is listed as BSD-3-Clause, 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 paperclip and 96 for utask. This is a procurement signal, not legal advice.
In Workflow Automation, both paperclip (114,484 stars) and utask (1,415 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: paperclip is open source, utask is open source.
paperclip is ahead on every scored dimension that is not level. Level dimensions: issue health, license flexibility, self-hosting. The widest gap is fork community at 53 points (100 vs 47), and the tightest is self-hosting at 0 points (100 vs 100).
paperclip finishes ahead at 94.7 against utask at 65.3, a 29.4 point decisive 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 | paperclip | utask |
|---|---|---|
| GitHub stars | 114,484 | 1,415 |
| Forks | 18,987 | 105 |
| Open issues | 6,806 | 85 |
| Adoption | 100 | 62 |
| Activity | 100 | 58 |
| Community | 100 | 47 |
| Issue health | 52 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 65.3 |
The open-source app everyone uses to manage agents at work
µTask is an automation engine that models and executes business processes declared in yaml. ✏️📋
paperclip has more GitHub stars: 114,484 versus 1,415 for utask. The gap is 113,069 stars.
paperclip was pushed more recently: 17 November 2026 versus 29 July 2026 for utask. That is 111 days apart.
Yes. This catalog marks both paperclip and utask as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. utask is listed as BSD-3-Clause, 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 utask scores 65.3. This page calls that a decisive lead for paperclip.