Skip to content
DevUtils Online

Workflow Automation

budibase vs prefect

prefect leads by 11.5 · clear

A

budibase

84.5

28,420 stars · license n/a

B · leads

prefect

96.0

24,170 stars · Apache-2.0

budibase versus prefect 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; prefect is written mainly in Python. The composite score is 84.5 for budibase and 96.0 for prefect.

budibase has 28,420 GitHub stars to prefect's 24,170, a gap of 4,250 (1.18×). Forks are 2,237 for budibase and 2,668 for prefect. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 98 versus 100.

Push history: budibase was last pushed on 17 November 2026 (0 days ago), and prefect was last pushed on 17 November 2026 (0 days ago). Open issues stand at 318 for budibase (0.011 per star) and 876 for prefect (0.036 per star). Issue-health scores are 84 and 70; 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. prefect 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 prefect. This is a procurement signal, not legal advice.

Only prefect is marked self-hostable here (24,170 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, prefect is open source.

The lead is split. budibase is furthest ahead on issue health (84 to 70), while prefect is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.

prefect finishes ahead at 96.0 against budibase at 84.5, a 11.5 point clear margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

budibase versus prefect metrics
Signal budibase prefect
GitHub stars 28,420 24,170
Forks 2,237 2,668
Open issues 318 876
Adoption 100 98
Activity 100 100
Community 98 100
Issue health 84 70
License 30 96
Self-hosting 35 100
Composite 84.5 96.0

Questions this page answers

Which has more GitHub stars, budibase or prefect?

budibase has more GitHub stars: 28,420 versus 24,170 for prefect. The gap is 4,250 stars.

Which was updated more recently, budibase or prefect?

Both were last pushed on 17 November 2026.

Can I self-host both budibase and prefect?

Only prefect is marked self-hostable. budibase is not.

Which license is easier to embed in a commercial product, budibase or prefect?

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. prefect 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.

Who wins the budibase vs prefect score?

prefect scores 96.0 and budibase scores 84.5. This page calls that a clear lead for prefect.

Related comparisons