Skip to content
DevUtils Online

Workflow Automation

keep vs open-claude-cowork

keep leads by 1.9 · narrow

A · leads

keep

81.6

12,531 stars · license n/a

keep versus open-claude-cowork 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; open-claude-cowork is written mainly in JavaScript. The composite score is 81.6 for keep and 79.7 for open-claude-cowork.

keep has 12,531 GitHub stars to open-claude-cowork's 4,319, a gap of 8,212 (2.90×). Forks are 1,555 for keep and 701 for open-claude-cowork. On the log scale used inside this pair, adoption is 100 versus 89, and the fork community is 100 versus 89.

Push history: keep was last pushed on 16 November 2026 (1 day ago), and open-claude-cowork was last pushed on 23 May 2026 (178 days ago). Open issues stand at 708 for keep (0.056 per star) and 16 for open-claude-cowork (0.004 per star). Issue-health scores are 52 and 96; activity scores are 100 and 36.

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. open-claude-cowork 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 open-claude-cowork. This is a procurement signal, not legal advice.

Only open-claude-cowork is marked self-hostable here (4,319 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, open-claude-cowork is open source.

The lead is split. keep is furthest ahead on recent activity (100 to 36), while open-claude-cowork is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.

keep finishes ahead at 81.6 against open-claude-cowork at 79.7, a 1.9 point narrow 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 open-claude-cowork metrics
Signal keep open-claude-cowork
GitHub stars 12,531 4,319
Forks 1,555 701
Open issues 708 16
Adoption 100 89
Activity 100 36
Community 100 89
Issue health 52 96
License 30 96
Self-hosting 35 100
Composite 81.6 79.7

Questions this page answers

Which has more GitHub stars, keep or open-claude-cowork?

keep has more GitHub stars: 12,531 versus 4,319 for open-claude-cowork. The gap is 8,212 stars.

Which was updated more recently, keep or open-claude-cowork?

keep was pushed more recently: 16 November 2026 versus 23 May 2026 for open-claude-cowork. That is 177 days apart.

Can I self-host both keep and open-claude-cowork?

Only open-claude-cowork is marked self-hostable. keep is not.

Which license is easier to embed in a commercial product, keep or open-claude-cowork?

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. open-claude-cowork 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 open-claude-cowork score?

keep scores 81.6 and open-claude-cowork scores 79.7. This page calls that a narrow lead for keep.

Related comparisons