Skip to content
DevUtils Online

Workflow Automation

keep vs paperclip

paperclip leads by 23.1 · decisive

A

keep

71.6

12,531 stars · license n/a

B · leads

paperclip

94.7

114,484 stars · MIT

keep versus paperclip is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. keep is written mainly in Python; paperclip is written mainly in TypeScript. The composite score is 71.6 for keep and 94.7 for paperclip.

paperclip has 114,484 GitHub stars to keep's 12,531, a gap of 101,953 (9.14×). Forks are 1,555 for keep and 18,987 for paperclip. On the log scale used inside this pair, adoption is 81 versus 100, and the fork community is 75 versus 100.

Push history: keep was last pushed on 16 November 2026 (1 day ago), and paperclip was last pushed on 17 November 2026 (0 days ago). Open issues stand at 708 for keep (0.056 per star) and 6,806 for paperclip (0.059 per star). Issue-health scores are 52 and 52; activity scores are 100 and 100.

keep 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 keep and 96 for paperclip. This is a procurement signal, not legal advice.

Only paperclip is marked self-hostable here (114,484 stars, deploy score 100). keep is not (12,531 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: keep 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. The widest gap is license flexibility at 66 points (30 vs 96), and the tightest is issue health at 0 points (52 vs 52).

paperclip finishes ahead at 94.7 against keep at 71.6, a 23.1 point decisive margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

keep versus paperclip metrics
Signal keep paperclip
GitHub stars 12,531 114,484
Forks 1,555 18,987
Open issues 708 6,806
Adoption 81 100
Activity 100 100
Community 75 100
Issue health 52 52
License 30 96
Self-hosting 35 100
Composite 71.6 94.7

Questions this page answers

Which has more GitHub stars, keep or paperclip?

paperclip has more GitHub stars: 114,484 versus 12,531 for keep. The gap is 101,953 stars.

Which was updated more recently, keep or paperclip?

paperclip was pushed more recently: 17 November 2026 versus 16 November 2026 for keep. That is 1 days apart.

Can I self-host both keep and paperclip?

Only paperclip is marked self-hostable. keep is not.

Which license is easier to embed in a commercial product, keep or paperclip?

keep 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.

Who wins the keep vs paperclip score?

paperclip scores 94.7 and keep scores 71.6. This page calls that a decisive lead for paperclip.

Related comparisons