A
AutoHotkey
85.1
13,492 stars · GPL-2.0
Workflow Automation
paperclip leads by 9.6 · clear
A
85.1
13,492 stars · GPL-2.0
B · leads
94.7
114,484 stars · MIT
AutoHotkey versus paperclip is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. AutoHotkey is written mainly in C++; paperclip is written mainly in TypeScript. The composite score is 85.1 for AutoHotkey and 94.7 for paperclip.
paperclip has 114,484 GitHub stars to AutoHotkey's 13,492, a gap of 100,992 (8.49×). Forks are 1,206 for AutoHotkey and 18,987 for paperclip. On the log scale used inside this pair, adoption is 82 versus 100, and the fork community is 72 versus 100.
Push history: AutoHotkey was last pushed on 13 November 2026 (3 days ago), and paperclip was last pushed on 17 November 2026 (0 days ago). Open issues stand at 13 for AutoHotkey (0.001 per star) and 6,806 for paperclip (0.059 per star). Issue-health scores are 96 and 52; activity scores are 100 and 100.
AutoHotkey is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. 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 64 for AutoHotkey and 96 for paperclip. This is a procurement signal, not legal advice.
In Workflow Automation, both AutoHotkey (13,492 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: AutoHotkey is open source, paperclip is open source.
The lead is split. AutoHotkey is furthest ahead on issue health (96 to 52), while paperclip is furthest ahead on license flexibility (96 to 64). Choose the dimension a rollout cannot compromise on.
paperclip finishes ahead at 94.7 against AutoHotkey at 85.1, a 9.6 point clear 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 | AutoHotkey | paperclip |
|---|---|---|
| GitHub stars | 13,492 | 114,484 |
| Forks | 1,206 | 18,987 |
| Open issues | 13 | 6,806 |
| Adoption | 82 | 100 |
| Activity | 100 | 100 |
| Community | 72 | 100 |
| Issue health | 96 | 52 |
| License | 64 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 85.1 | 94.7 |
AutoHotkey - macro-creation and automation-oriented scripting utility for Windows.
The open-source app everyone uses to manage agents at work
paperclip has more GitHub stars: 114,484 versus 13,492 for AutoHotkey. The gap is 100,992 stars.
paperclip was pushed more recently: 17 November 2026 versus 13 November 2026 for AutoHotkey. That is 3 days apart.
Yes. This catalog marks both AutoHotkey and paperclip as self-hostable. Confirm each project's deploy docs before you plan a migration.
AutoHotkey is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. 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 AutoHotkey scores 85.1. This page calls that a clear lead for paperclip.