A · leads
budibase
84.8
28,420 stars · license n/a
Workflow Automation
budibase leads by 7.0 · clear
A · leads
84.8
28,420 stars · license n/a
B
77.8
2,639 stars · MIT
budibase versus shepherd 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; shepherd is written mainly in Python. The composite score is 84.8 for budibase and 77.8 for shepherd.
budibase has 28,420 GitHub stars to shepherd's 2,639, a gap of 25,781 (10.77×). Forks are 2,237 for budibase and 227 for shepherd. On the log scale used inside this pair, adoption is 100 versus 77, and the fork community is 100 versus 70.
Push history: budibase was last pushed on 17 November 2026 (0 days ago), and shepherd was last pushed on 09 September 2026 (69 days ago). Open issues stand at 318 for budibase (0.011 per star) and 13 for shepherd (0.005 per star). Issue-health scores are 84 and 96; activity scores are 100 and 58.
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. shepherd 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 shepherd. This is a procurement signal, not legal advice.
Only shepherd is marked self-hostable here (2,639 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, shepherd is open source.
The lead is split. budibase is furthest ahead on recent activity (100 to 58), while shepherd is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
budibase finishes ahead at 84.8 against shepherd at 77.8, a 7.0 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 | shepherd |
|---|---|---|
| GitHub stars | 28,420 | 2,639 |
| Forks | 2,237 | 227 |
| Open issues | 318 | 13 |
| Adoption | 100 | 77 |
| Activity | 100 | 58 |
| Community | 100 | 70 |
| Issue health | 84 | 96 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 84.8 | 77.8 |
AI agents, automations and apps that run your operations. Model agnostic.
A runtime substrate that turns an agent's execution into a reversible, Git-like trace, so meta-agents can observe, fork, replay, and revert any run. Couples agent and environments in a copy-on-write fork ~5x faster than docker commit, with ~95% KV-cache reuse on replay. Framework built for meta-agents to supervise, optimize, and train other agents
budibase has more GitHub stars: 28,420 versus 2,639 for shepherd. The gap is 25,781 stars.
budibase was pushed more recently: 17 November 2026 versus 09 September 2026 for shepherd. That is 69 days apart.
Only shepherd 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. shepherd 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.
budibase scores 84.8 and shepherd scores 77.8. This page calls that a clear lead for budibase.