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
12 hours agoRepository age
7 yearsVersion
v3.50.0Self-hosted
YesRepository
budibase/budibase
Last 30 days
Last commit
9 hours agoRepository age
6 yearsVersion
v3.20.252-ltsLicense
AGPL-3.0Self-hosted
YesRepository
tooljet/tooljet
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,376 stars and ToolJet having 41,179 stars on GitHub. In terms of developer contributions, ToolJet has 5,510 forks, indicating strong developer engagement.
Budibase and ToolJet are moving at much the same rate, adding 44 stars and adding 150 stars respectively over the last 30 days (+0.2% vs +0.4%). Neither is pulling away from the other on momentum alone.
Both projects show recent activity, with Budibase last updated 12 hours ago and ToolJet 9 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 6 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.