Skip to content
DevUtils Online

Workflow Automation

conductor vs keep

conductor leads by 18.7 · decisive

A · leads

conductor

97.2

32,478 stars · Apache-2.0

B

keep

78.5

12,531 stars · license n/a

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

conductor has 32,478 GitHub stars to keep's 12,531, a gap of 19,947 (2.59×). Forks are 1,074 for conductor and 1,555 for keep. On the log scale used inside this pair, adoption is 100 versus 91, and the fork community is 95 versus 100.

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

conductor 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. 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. License scores in this pair are 96 for conductor and 30 for keep. This is a procurement signal, not legal advice.

Only conductor is marked self-hostable here (32,478 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: conductor is open source, keep is unpriced in this catalog.

The lead is split. conductor is furthest ahead on license flexibility (96 to 30), while keep is furthest ahead on fork community (100 to 95). Choose the dimension a rollout cannot compromise on.

conductor finishes ahead at 97.2 against keep at 78.5, a 18.7 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.

conductor versus keep metrics
Signal conductor keep
GitHub stars 32,478 12,531
Forks 1,074 1,555
Open issues 300 708
Adoption 100 91
Activity 100 100
Community 95 100
Issue health 84 52
License 96 30
Self-hosting 100 35
Composite 97.2 78.5

conductor

Conductor is an event driven agentic workflow engine providing durable and highly resilient execution engine for applications and AI Agents

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, conductor or keep?

conductor has more GitHub stars: 32,478 versus 12,531 for keep. The gap is 19,947 stars.

Which was updated more recently, conductor or keep?

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

Can I self-host both conductor and keep?

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

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

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

Who wins the conductor vs keep score?

conductor scores 97.2 and keep scores 78.5. This page calls that a decisive lead for conductor.

Related comparisons