Skip to content
DevUtils Online

Workflow Automation

keep vs Windmill

Windmill leads by 10.5 · clear

A

keep

80.2

12,531 stars · license n/a

B · leads

Windmill

90.7

18,618 stars · AGPL-3.0

keep versus Windmill 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; Windmill is written mainly in Rust. The composite score is 80.2 for keep and 90.7 for Windmill.

Windmill has 18,618 GitHub stars to keep's 12,531, a gap of 6,087 (1.49×). Forks are 1,555 for keep and 1,165 for Windmill. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 100 versus 96.

Push history: keep was last pushed on 16 November 2026 (1 day ago), and Windmill was last pushed on 17 November 2026 (0 days ago). Open issues stand at 708 for keep (0.056 per star) and 889 for Windmill (0.048 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. Windmill is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 30 for keep and 52 for Windmill. This is a procurement signal, not legal advice.

Only Windmill is marked self-hostable here (18,618 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, Windmill is open source.

The lead is split. keep is furthest ahead on fork community (100 to 96), while Windmill is furthest ahead on self-hosting (100 to 35). Choose the dimension a rollout cannot compromise on.

Windmill finishes ahead at 90.7 against keep at 80.2, a 10.5 point clear 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 Windmill metrics
Signal keep Windmill
GitHub stars 12,531 18,618
Forks 1,555 1,165
Open issues 708 889
Adoption 96 100
Activity 100 100
Community 100 96
Issue health 52 70
License 30 52
Self-hosting 35 100
Composite 80.2 90.7

Windmill

Windmill runs scripts and approval flows as internal apps, with workers you can scale. It is used by teams that want automation closer to a developer platform than a no-code zap.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, keep or Windmill?

Windmill has more GitHub stars: 18,618 versus 12,531 for keep. The gap is 6,087 stars.

Which was updated more recently, keep or Windmill?

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

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

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

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. Windmill is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the keep vs Windmill score?

Windmill scores 90.7 and keep scores 80.2. This page calls that a clear lead for Windmill.

Related comparisons