A · leads
budibase
84.8
28,420 stars · license n/a
Workflow Automation
budibase leads by 1.6 · narrow
A · leads
84.8
28,420 stars · license n/a
B
83.2
1,635 stars · Apache-2.0
budibase versus rulego 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; rulego is written mainly in Go. The composite score is 84.8 for budibase and 83.2 for rulego.
budibase has 28,420 GitHub stars to rulego's 1,635, a gap of 26,785 (17.38×). Forks are 2,237 for budibase and 164 for rulego. On the log scale used inside this pair, adoption is 100 versus 72, and the fork community is 100 versus 66.
Push history: budibase was last pushed on 17 November 2026 (0 days ago), and rulego was last pushed on 13 November 2026 (4 days ago). Open issues stand at 318 for budibase (0.011 per star) and 4 for rulego (0.002 per star). Issue-health scores are 84 and 96; activity scores are 100 and 92.
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. rulego 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. License scores in this pair are 30 for budibase and 96 for rulego. This is a procurement signal, not legal advice.
Only rulego is marked self-hostable here (1,635 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, rulego is open source.
The lead is split. budibase is furthest ahead on fork community (100 to 66), while rulego is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
budibase finishes ahead at 84.8 against rulego at 83.2, a 1.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 | rulego |
|---|---|---|
| GitHub stars | 28,420 | 1,635 |
| Forks | 2,237 | 164 |
| Open issues | 318 | 4 |
| Adoption | 100 | 72 |
| Activity | 100 | 92 |
| Community | 100 | 66 |
| Issue health | 84 | 96 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 84.8 | 83.2 |
AI agents, automations and apps that run your operations. Model agnostic.
⛓️RuleGo is a lightweight, high-performance, embedded, next-generation component orchestration rule engine framework for Go.
budibase has more GitHub stars: 28,420 versus 1,635 for rulego. The gap is 26,785 stars.
budibase was pushed more recently: 17 November 2026 versus 13 November 2026 for rulego. That is 4 days apart.
Only rulego 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. rulego 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
budibase scores 84.8 and rulego scores 83.2. This page calls that a narrow lead for budibase.