A · leads
paperclip
94.7
114,484 stars · MIT
Workflow Automation
paperclip leads by 12.7 · clear
A · leads
94.7
114,484 stars · MIT
B
82.0
18,618 stars · AGPL-3.0
paperclip versus Windmill 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; Windmill is written mainly in Rust. The composite score is 94.7 for paperclip and 82.0 for Windmill.
paperclip has 114,484 GitHub stars to Windmill's 18,618, a gap of 95,866 (6.15×). Forks are 18,987 for paperclip and 1,165 for Windmill. On the log scale used inside this pair, adoption is 100 versus 84, and the fork community is 100 versus 72.
Push history: paperclip was last pushed on 17 November 2026 (0 days ago), and Windmill was last pushed on 17 November 2026 (0 days ago). Open issues stand at 6,806 for paperclip (0.059 per star) and 889 for Windmill (0.048 per star). Issue-health scores are 52 and 70; activity scores are 100 and 100.
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. Windmill is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for paperclip and 52 for Windmill. This is a procurement signal, not legal advice.
In Workflow Automation, both paperclip (114,484 stars) and Windmill (18,618 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, Windmill is open source.
The lead is split. paperclip is furthest ahead on license flexibility (96 to 52), while Windmill is furthest ahead on issue health (70 to 52). Choose the dimension a rollout cannot compromise on.
paperclip finishes ahead at 94.7 against Windmill at 82.0, a 12.7 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 | paperclip | Windmill |
|---|---|---|
| GitHub stars | 114,484 | 18,618 |
| Forks | 18,987 | 1,165 |
| Open issues | 6,806 | 889 |
| Adoption | 100 | 84 |
| Activity | 100 | 100 |
| Community | 100 | 72 |
| Issue health | 52 | 70 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 82.0 |
The open-source app everyone uses to manage agents at work
Windmill runs scripts and approval flows as internal apps, with workers you can scale. It is used by teams that want automation closer to a developer platform than a no-code zap.
paperclip has more GitHub stars: 114,484 versus 18,618 for Windmill. The gap is 95,866 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both paperclip and Windmill 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. Windmill is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
paperclip scores 94.7 and Windmill scores 82.0. This page calls that a clear lead for paperclip.