A · leads
budibase
84.8
28,420 stars · license n/a
Workflow Automation
budibase leads by 8.6 · clear
A · leads
84.8
28,420 stars · license n/a
B
76.2
2,919 stars · license n/a
budibase versus LoopForge 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; LoopForge is written mainly in Go. The composite score is 84.8 for budibase and 76.2 for LoopForge.
budibase has 28,420 GitHub stars to LoopForge's 2,919, a gap of 25,501 (9.74×). Forks are 2,237 for budibase and 423 for LoopForge. On the log scale used inside this pair, adoption is 100 versus 78, and the fork community is 100 versus 78.
Push history: budibase was last pushed on 17 November 2026 (0 days ago), and LoopForge was last pushed on 17 November 2026 (0 days ago). Open issues stand at 318 for budibase (0.011 per star) and 176 for LoopForge (0.060 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. LoopForge 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 LoopForge. This is a procurement signal, not legal advice.
Only LoopForge is marked self-hostable here (2,919 stars, deploy score 100). budibase is not (28,420 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: budibase is unpriced in this catalog, LoopForge is unpriced in this catalog.
The lead is split. budibase is furthest ahead on issue health (84 to 52), while LoopForge is furthest ahead on self-hosting (100 to 35). Choose the dimension a rollout cannot compromise on.
budibase finishes ahead at 84.8 against LoopForge at 76.2, a 8.6 point clear 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 | LoopForge |
|---|---|---|
| GitHub stars | 28,420 | 2,919 |
| Forks | 2,237 | 423 |
| Open issues | 318 | 176 |
| Adoption | 100 | 78 |
| Activity | 100 | 100 |
| Community | 100 | 78 |
| Issue health | 84 | 52 |
| License | 30 | 30 |
| Self-hosting | 35 | 100 |
| Composite | 84.8 | 76.2 |
AI agents, automations and apps that run your operations. Model agnostic.
Self-hosted workflows for coding-agent delivery. Orchestrate CodeBuddy, Codex and Claude Code with scripts and human approval gates. Includes Local workflows for coding assistants.
budibase has more GitHub stars: 28,420 versus 2,919 for LoopForge. The gap is 25,501 stars.
Both were last pushed on 17 November 2026.
Only LoopForge is marked self-hostable. budibase is not.
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. LoopForge 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 LoopForge scores 76.2. This page calls that a clear lead for budibase.