Learn how Budibase and ToolJet differ in their key features, development activity, technology stack and community adoption, so you can decide which of these low-code/no-code platforms is best for you.
Last 30 days
Last commit
Repository age
Version
Self-hosted
Repository

Last 30 days
Last commit
Repository age
Version
License
Self-hosted
Repository

Both Budibase and ToolJet have their unique strengths and serve similar purposes effectively. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
Both tools have similar popularity levels, with Budibase having 28,244 stars and ToolJet having 40,770 stars on GitHub. In terms of developer contributions, ToolJet has 5,416 forks, indicating strong developer engagement.
ToolJet is growing faster, adding 2,504 stars in the last 30 days (+6.5%) against adding 81 stars for Budibase (+0.3%). ToolJet is both larger and pulling further ahead.
Both projects show recent activity, with Budibase last updated 9 hours ago and ToolJet 8 hours ago.
Both tools share common technology foundations, being built with JavaScript, CSS, Bash, Typescript, JSX. However, they differ in their additional technology choices: Budibase uses Next.js, Nuxt.js while ToolJet leverages SCSS, Perl, NestJS.
Budibase has been in development longer, starting 7 years ago, compared to ToolJet which began 5 years ago. This 1.8-year head start suggests Budibase may have more mature features and established processes.
ToolJet is licensed under AGPL-3.0, while Budibase's license terms are not publicly specified.
Both tools serve similar use cases in Low-Code/No-Code.
Both Budibase and ToolJet offer self-hosting capabilities, giving you full control over your data and infrastructure.