A
gawkbot
64.3
1,582 stars · license n/a
Workflow Automation
paperclip leads by 30.4 · decisive
A
64.3
1,582 stars · license n/a
B · leads
94.7
114,484 stars · MIT
gawkbot versus paperclip is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. gawkbot is written mainly in Go; paperclip is written mainly in TypeScript. The composite score is 64.3 for gawkbot and 94.7 for paperclip.
paperclip has 114,484 GitHub stars to gawkbot's 1,582, a gap of 112,902 (72.37×). Forks are 146 for gawkbot and 18,987 for paperclip. On the log scale used inside this pair, adoption is 63 versus 100, and the fork community is 51 versus 100.
Push history: gawkbot was last pushed on 01 November 2026 (16 days ago), and paperclip was last pushed on 17 November 2026 (0 days ago). Open issues stand at 71 for gawkbot (0.045 per star) and 6,806 for paperclip (0.059 per star). Issue-health scores are 70 and 52; activity scores are 78 and 100.
gawkbot is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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. License scores in this pair are 30 for gawkbot and 96 for paperclip. This is a procurement signal, not legal advice.
In Workflow Automation, both gawkbot (1,582 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: gawkbot is unpriced in this catalog, paperclip is open source.
The lead is split. gawkbot is furthest ahead on issue health (70 to 52), while paperclip is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
paperclip finishes ahead at 94.7 against gawkbot at 64.3, a 30.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 | gawkbot | paperclip |
|---|---|---|
| GitHub stars | 1,582 | 114,484 |
| Forks | 146 | 18,987 |
| Open issues | 71 | 6,806 |
| Adoption | 63 | 100 |
| Activity | 78 | 100 |
| Community | 51 | 100 |
| Issue health | 70 | 52 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 64.3 | 94.7 |
open source grok bot. gawk bots automate your menial work via AI models and build you microapps to manage the outcome, so that you have a false sense of control.
The open-source app everyone uses to manage agents at work
paperclip has more GitHub stars: 114,484 versus 1,582 for gawkbot. The gap is 112,902 stars.
paperclip was pushed more recently: 17 November 2026 versus 01 November 2026 for gawkbot. That is 16 days apart.
Yes. This catalog marks both gawkbot and paperclip as self-hostable. Confirm each project's deploy docs before you plan a migration.
gawkbot is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 gawkbot scores 64.3. This page calls that a decisive lead for paperclip.