A
lowdefy
82.0
3,025 stars · Apache-2.0
Workflow Automation
paperclip leads by 12.7 · clear
A
82.0
3,025 stars · Apache-2.0
B · leads
94.7
114,484 stars · MIT
lowdefy versus paperclip is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. lowdefy is written mainly in JavaScript; paperclip is written mainly in TypeScript. The composite score is 82.0 for lowdefy and 94.7 for paperclip.
paperclip has 114,484 GitHub stars to lowdefy's 3,025, a gap of 111,459 (37.85×). Forks are 188 for lowdefy and 18,987 for paperclip. On the log scale used inside this pair, adoption is 69 versus 100, and the fork community is 53 versus 100.
Push history: lowdefy 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 15 for lowdefy (0.005 per star) and 6,806 for paperclip (0.059 per star). Issue-health scores are 96 and 52; activity scores are 100 and 100.
lowdefy is listed as Apache-2.0, 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. 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 96 for lowdefy and 96 for paperclip. This is a procurement signal, not legal advice.
In Workflow Automation, both lowdefy (3,025 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: lowdefy is open source, paperclip is open source.
The lead is split. lowdefy is furthest ahead on issue health (96 to 52), while paperclip is furthest ahead on fork community (100 to 53). Choose the dimension a rollout cannot compromise on.
paperclip finishes ahead at 94.7 against lowdefy 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 | lowdefy | paperclip |
|---|---|---|
| GitHub stars | 3,025 | 114,484 |
| Forks | 188 | 18,987 |
| Open issues | 15 | 6,806 |
| Adoption | 69 | 100 |
| Activity | 100 | 100 |
| Community | 53 | 100 |
| Issue health | 96 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 82.0 | 94.7 |
Build apps that AI can generate, humans can review, and teams can maintain. Config that works between code and natural language.
The open-source app everyone uses to manage agents at work
paperclip has more GitHub stars: 114,484 versus 3,025 for lowdefy. The gap is 111,459 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both lowdefy and paperclip as self-hostable. Confirm each project's deploy docs before you plan a migration.
lowdefy is listed as Apache-2.0, 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. 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 lowdefy scores 82.0. This page calls that a clear lead for paperclip.