A
budibase
84.8
28,420 stars · license n/a
Workflow Automation
semantic-release leads by 12.2 · clear
A
84.8
28,420 stars · license n/a
B · leads
97.0
24,177 stars · MIT
budibase versus semantic-release 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; semantic-release is written mainly in JavaScript. The composite score is 84.8 for budibase and 97.0 for semantic-release.
budibase has 28,420 GitHub stars to semantic-release's 24,177, a gap of 4,243 (1.18×). Forks are 2,237 for budibase and 1,807 for semantic-release. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 100 versus 97.
Push history: budibase was last pushed on 17 November 2026 (0 days ago), and semantic-release was last pushed on 17 November 2026 (0 days ago). Open issues stand at 318 for budibase (0.011 per star) and 410 for semantic-release (0.017 per star). Issue-health scores are 84 and 84; 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. semantic-release 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. License scores in this pair are 30 for budibase and 96 for semantic-release. This is a procurement signal, not legal advice.
Only semantic-release is marked self-hostable here (24,177 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, semantic-release is open source.
The lead is split. budibase is furthest ahead on fork community (100 to 97), while semantic-release is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
semantic-release finishes ahead at 97.0 against budibase at 84.8, a 12.2 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 | semantic-release |
|---|---|---|
| GitHub stars | 28,420 | 24,177 |
| Forks | 2,237 | 1,807 |
| Open issues | 318 | 410 |
| Adoption | 100 | 98 |
| Activity | 100 | 100 |
| Community | 100 | 97 |
| Issue health | 84 | 84 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 84.8 | 97.0 |
AI agents, automations and apps that run your operations. Model agnostic.
📦🚀 Fully automated version management and package publishing
budibase has more GitHub stars: 28,420 versus 24,177 for semantic-release. The gap is 4,243 stars.
Both were last pushed on 17 November 2026.
Only semantic-release 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. semantic-release 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
semantic-release scores 97.0 and budibase scores 84.8. This page calls that a clear lead for semantic-release.