Skip to content
DevUtils Online

Workflow Automation

agenta vs keep

Too close to call · 82.0 to 81.6

A · level

agenta

82.0

4,915 stars · license n/a

B · level

keep

81.6

12,531 stars · license n/a

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

keep has 12,531 GitHub stars to agenta's 4,915, a gap of 7,616 (2.55×). Forks are 733 for agenta and 1,555 for keep. On the log scale used inside this pair, adoption is 90 versus 100, and the fork community is 90 versus 100.

Push history: agenta 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 307 for agenta (0.062 per star) and 708 for keep (0.056 per star). Issue-health scores are 52 and 52; activity scores are 100 and 100.

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

Only agenta is marked self-hostable here (4,915 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: agenta is unpriced in this catalog, keep is unpriced in this catalog.

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

Composite score: agenta 82.0, keep 81.6. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.

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.

agenta versus keep metrics
Signal agenta keep
GitHub stars 4,915 12,531
Forks 733 1,555
Open issues 307 708
Adoption 90 100
Activity 100 100
Community 90 100
Issue health 52 52
License 30 30
Self-hosting 100 35
Composite 82.0 81.6

Questions this page answers

Which has more GitHub stars, agenta or keep?

keep has more GitHub stars: 12,531 versus 4,915 for agenta. The gap is 7,616 stars.

Which was updated more recently, agenta or keep?

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

Can I self-host both agenta and keep?

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

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

agenta 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. 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 agenta vs keep score?

Neither tool clears a one-point margin. agenta scores 82.0 and keep scores 81.6.

Related comparisons