Skip to content
DevUtils Online

Workflow Automation

keep vs Meshroom

Meshroom leads by 1.6 · narrow

A

keep

81.4

12,531 stars · license n/a

B · leads

Meshroom

83.0

13,096 stars · license n/a

keep versus Meshroom is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Python. The composite score is 81.4 for keep and 83.0 for Meshroom.

Meshroom has 13,096 GitHub stars to keep's 12,531, a gap of 565 (1.05×). Forks are 1,555 for keep and 1,243 for Meshroom. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 100 versus 97.

Push history: keep was last pushed on 16 November 2026 (1 day ago), and Meshroom was last pushed on 17 November 2026 (0 days ago). Open issues stand at 708 for keep (0.056 per star) and 549 for Meshroom (0.042 per star). Issue-health scores are 52 and 70; 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. Meshroom 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. License scores in this pair are 30 for keep and 30 for Meshroom. This is a procurement signal, not legal advice.

Neither keep nor Meshroom is marked self-hostable in this catalog (12,531 and 13,096 stars). Deploy scores stay at 35 and 35. Treat both as hosted products until their own docs say you can run them. Pricing labels on file: keep is unpriced in this catalog, Meshroom is unpriced in this catalog.

The lead is split. keep is furthest ahead on fork community (100 to 97), while Meshroom is furthest ahead on issue health (70 to 52). Choose the dimension a rollout cannot compromise on.

Meshroom finishes ahead at 83.0 against keep at 81.4, a 1.6 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 Meshroom metrics
Signal keep Meshroom
GitHub stars 12,531 13,096
Forks 1,555 1,243
Open issues 708 549
Adoption 100 100
Activity 100 100
Community 100 97
Issue health 52 70
License 30 30
Self-hosting 35 35
Composite 81.4 83.0

Questions this page answers

Which has more GitHub stars, keep or Meshroom?

Meshroom has more GitHub stars: 13,096 versus 12,531 for keep. The gap is 565 stars.

Which was updated more recently, keep or Meshroom?

Meshroom 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 Meshroom?

Neither keep nor Meshroom is marked self-hostable in this catalog.

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

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. Meshroom 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the keep vs Meshroom score?

Meshroom scores 83.0 and keep scores 81.4. This page calls that a narrow lead for Meshroom.

Related comparisons