A
LoopForge
70.7
2,919 stars · license n/a
Workflow Automation
paperclip leads by 24.0 · decisive
A
70.7
2,919 stars · license n/a
B · leads
94.7
114,484 stars · MIT
LoopForge versus paperclip is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. LoopForge is written mainly in Go; paperclip is written mainly in TypeScript. The composite score is 70.7 for LoopForge and 94.7 for paperclip.
paperclip has 114,484 GitHub stars to LoopForge's 2,919, a gap of 111,565 (39.22×). Forks are 423 for LoopForge and 18,987 for paperclip. On the log scale used inside this pair, adoption is 68 versus 100, and the fork community is 61 versus 100.
Push history: LoopForge was last pushed on 17 November 2026 (0 days ago), and paperclip was last pushed on 17 November 2026 (0 days ago). Open issues stand at 176 for LoopForge (0.060 per star) and 6,806 for paperclip (0.059 per star). Issue-health scores are 52 and 52; activity scores are 100 and 100.
LoopForge 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 LoopForge and 96 for paperclip. This is a procurement signal, not legal advice.
In Workflow Automation, both LoopForge (2,919 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: LoopForge is unpriced in this catalog, paperclip is open source.
paperclip is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, self-hosting. The widest gap is license flexibility at 66 points (30 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
paperclip finishes ahead at 94.7 against LoopForge at 70.7, a 24.0 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 | LoopForge | paperclip |
|---|---|---|
| GitHub stars | 2,919 | 114,484 |
| Forks | 423 | 18,987 |
| Open issues | 176 | 6,806 |
| Adoption | 68 | 100 |
| Activity | 100 | 100 |
| Community | 61 | 100 |
| Issue health | 52 | 52 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 70.7 | 94.7 |
Self-hosted workflows for coding-agent delivery. Orchestrate CodeBuddy, Codex and Claude Code with scripts and human approval gates. Includes Local workflows for coding assistants.
The open-source app everyone uses to manage agents at work
paperclip has more GitHub stars: 114,484 versus 2,919 for LoopForge. The gap is 111,565 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both LoopForge and paperclip as self-hostable. Confirm each project's deploy docs before you plan a migration.
LoopForge 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 LoopForge scores 70.7. This page calls that a decisive lead for paperclip.