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.

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 40,671 and 38,947 stars respectively. In terms of developer contributions, ToolJet has 5,251 forks, indicating strong developer engagement.
ToolJet is growing faster, adding 736 stars in the last 30 days (+1.9%) against adding 333 stars for AppSmith (+0.8%). ToolJet is the smaller project of the two, so it is closing the gap rather than extending a lead.
Both projects show recent activity, with AppSmith last updated 6 hours ago and ToolJet 7 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 ToolJet leverages SCSS, Perl, NestJS.
Both projects started around the same time, with AppSmith beginning 6 years ago and ToolJet 5 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.

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