A · leads
budibase
84.8
28,420 stars · license n/a
Workflow Automation
budibase leads by 6.6 · narrow
A · leads
84.8
28,420 stars · license n/a
B
78.2
12,531 stars · license n/a
budibase versus keep is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. budibase is written mainly in TypeScript; keep is written mainly in Python. The composite score is 84.8 for budibase and 78.2 for keep.
budibase has 28,420 GitHub stars to keep's 12,531, a gap of 15,889 (2.27×). Forks are 2,237 for budibase and 1,555 for keep. On the log scale used inside this pair, adoption is 100 versus 92, and the fork community is 100 versus 95.
Push history: budibase 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 318 for budibase (0.011 per star) and 708 for keep (0.056 per star). Issue-health scores are 84 and 52; activity scores are 100 and 100.
budibase 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 budibase and 30 for keep. This is a procurement signal, not legal advice.
Neither budibase nor keep is marked self-hostable in this catalog (28,420 and 12,531 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: budibase is unpriced in this catalog, keep is unpriced in this catalog.
budibase is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 32 points (84 vs 52), and the tightest is self-hosting at 0 points (35 vs 35).
budibase finishes ahead at 84.8 against keep at 78.2, a 6.6 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | budibase | keep |
|---|---|---|
| GitHub stars | 28,420 | 12,531 |
| Forks | 2,237 | 1,555 |
| Open issues | 318 | 708 |
| Adoption | 100 | 92 |
| Activity | 100 | 100 |
| Community | 100 | 95 |
| Issue health | 84 | 52 |
| License | 30 | 30 |
| Self-hosting | 35 | 35 |
| Composite | 84.8 | 78.2 |
AI agents, automations and apps that run your operations. Model agnostic.
The open-source AIOps and alert management platform
budibase has more GitHub stars: 28,420 versus 12,531 for keep. The gap is 15,889 stars.
budibase was pushed more recently: 17 November 2026 versus 16 November 2026 for keep. That is 1 days apart.
Neither budibase nor keep is marked self-hostable in this catalog.
budibase 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.
budibase scores 84.8 and keep scores 78.2. This page calls that a narrow lead for budibase.