Learn how AppSmith and Budibase 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
2 days agoRepository age
6 yearsVersion
v2.6.0License
Apache-2.0Self-hosted
YesRepository
appsmithorg/appsmith
Last 30 days
Last commit
24 hours agoRepository age
7 yearsVersion
v3.50.0Self-hosted
YesRepository
budibase/budibase
Both AppSmith and Budibase 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 AppSmith having 41,190 stars and Budibase having 28,395 stars on GitHub. In terms of developer contributions, AppSmith has 4,826 forks, indicating strong developer engagement.
AppSmith and Budibase are moving at much the same rate, adding 148 stars and adding 67 stars respectively over the last 30 days (+0.4% vs +0.2%). Neither is pulling away from the other on momentum alone.
Both projects show recent activity, with AppSmith last updated 2 days ago and Budibase 24 hours ago.
Both tools share common technology foundations, being built with JavaScript, CSS, Bash, Typescript, JSX. However, they differ in their additional technology choices: AppSmith uses Python, Java while Budibase leverages Next.js, Nuxt.js.
Budibase has been in development longer, starting 7 years ago, compared to AppSmith which began 6 years ago. This 1.1-year head start suggests Budibase may have more mature features and established processes.
AppSmith is licensed under Apache-2.0, while Budibase's license terms are not publicly specified.
Both tools serve similar use cases in Low-Code/No-Code.
Both AppSmith and Budibase offer self-hosting capabilities, giving you full control over your data and infrastructure.