Skip to content
DevUtils Online

Workflow Automation

flowgram.ai vs keep

flowgram.ai leads by 13.7 · clear

B

keep

81.6

12,531 stars · license n/a

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

keep has 12,531 GitHub stars to flowgram.ai's 8,589, a gap of 3,942 (1.46×). Forks are 788 for flowgram.ai and 1,555 for keep. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 91 versus 100.

Push history: flowgram.ai was last pushed on 16 November 2026 (1 day ago), and keep was last pushed on 16 November 2026 (1 day ago). Open issues stand at 117 for flowgram.ai (0.014 per star) and 708 for keep (0.056 per star). Issue-health scores are 84 and 52; activity scores are 100 and 100.

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

Only flowgram.ai is marked self-hostable here (8,589 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: flowgram.ai is open source, keep is unpriced in this catalog.

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

flowgram.ai finishes ahead at 95.3 against keep at 81.6, a 13.7 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.

flowgram.ai versus keep metrics
Signal flowgram.ai keep
GitHub stars 8,589 12,531
Forks 788 1,555
Open issues 117 708
Adoption 96 100
Activity 100 100
Community 91 100
Issue health 84 52
License 96 30
Self-hosting 100 35
Composite 95.3 81.6

flowgram.ai

FlowGram is an extensible workflow development framework with built-in canvas, form, variable, and materials that helps developers build AI workflow platforms faster and simpler.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, flowgram.ai or keep?

keep has more GitHub stars: 12,531 versus 8,589 for flowgram.ai. The gap is 3,942 stars.

Which was updated more recently, flowgram.ai or keep?

Both were last pushed on 16 November 2026.

Can I self-host both flowgram.ai and keep?

Only flowgram.ai is marked self-hostable. keep is not.

Which license is easier to embed in a commercial product, flowgram.ai or keep?

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

flowgram.ai scores 95.3 and keep scores 81.6. This page calls that a clear lead for flowgram.ai.

Related comparisons