Learn how AppSmith 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
2 days agoRepository age
6 yearsVersion
v2.6.0License
Apache-2.0Self-hosted
YesRepository
appsmithorg/appsmith
Last 30 days
Last commit
1 day agoRepository age
6 yearsVersion
v3.20.256-ltsLicense
AGPL-3.0Self-hosted
YesRepository
tooljet/tooljet
Both AppSmith 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 AppSmith and ToolJet show comparable community engagement with 41,190 and 41,207 stars respectively. In terms of developer contributions, ToolJet has 5,510 forks, indicating strong developer engagement.
AppSmith and ToolJet are moving at much the same rate, adding 148 stars and adding 153 stars respectively over the last 30 days (+0.4% vs +0.4%). Neither is pulling away from the other on momentum alone.
Both projects show recent activity, with AppSmith last updated 2 days ago and ToolJet 1 day 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 ToolJet leverages SCSS, Perl, NestJS.
Both projects started around the same time, with AppSmith beginning 6 years ago and ToolJet 6 years ago.
The projects use different licenses: AppSmith is licensed under Apache-2.0 while ToolJet uses AGPL-3.0. Consider the licensing requirements when choosing for your project.
Both tools serve similar use cases in Low-Code/No-Code.
Both AppSmith and ToolJet offer self-hosting capabilities, giving you full control over your data and infrastructure.