A
budibase
84.8
28,420 stars · license n/a
Workflow Automation
trigger.dev leads by 10.7 · clear
A
84.8
28,420 stars · license n/a
B · leads
95.5
16,776 stars · Apache-2.0
budibase versus trigger.dev is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 84.8 for budibase and 95.5 for trigger.dev.
budibase has 28,420 GitHub stars to trigger.dev's 16,776, a gap of 11,644 (1.69×). Forks are 2,237 for budibase and 1,534 for trigger.dev. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 100 versus 95.
Push history: budibase was last pushed on 17 November 2026 (0 days ago), and trigger.dev was last pushed on 17 November 2026 (0 days ago). Open issues stand at 318 for budibase (0.011 per star) and 268 for trigger.dev (0.016 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. trigger.dev 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 trigger.dev. This is a procurement signal, not legal advice.
Only trigger.dev is marked self-hostable here (16,776 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, trigger.dev is open source.
The lead is split. budibase is furthest ahead on adoption (100 to 95), while trigger.dev is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
trigger.dev finishes ahead at 95.5 against budibase at 84.8, a 10.7 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 | trigger.dev |
|---|---|---|
| GitHub stars | 28,420 | 16,776 |
| Forks | 2,237 | 1,534 |
| Open issues | 318 | 268 |
| Adoption | 100 | 95 |
| Activity | 100 | 100 |
| Community | 100 | 95 |
| Issue health | 84 | 84 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 84.8 | 95.5 |
AI agents, automations and apps that run your operations. Model agnostic.
Trigger.dev – build and deploy durable AI agents and workflows
budibase has more GitHub stars: 28,420 versus 16,776 for trigger.dev. The gap is 11,644 stars.
Both were last pushed on 17 November 2026.
Only trigger.dev 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. trigger.dev 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.
trigger.dev scores 95.5 and budibase scores 84.8. This page calls that a clear lead for trigger.dev.