Learn how NocoDB and Rowy 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
License
Self-hosted
Repository

Last 30 days
Last commit
Repository age
Version
License
Repository

NocoDB appears to have several advantages over Rowy, particularly in popularity, growth, activity, maturity and features. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
NocoDB significantly outpaces Rowy in community adoption with 64,816 stars compared to 6,839 stars on GitHub. This 9.5x difference suggests NocoDB has a much larger and more active community. In terms of developer contributions, NocoDB has 5,026 forks, indicating strong developer engagement.
NocoDB is growing faster, adding 401 stars in the last 30 days (+0.6%) against adding 8 stars for Rowy (+0.1%). NocoDB is both larger and pulling further ahead.
NocoDB shows more recent development activity with its last commit 1 hour ago, while Rowy was last updated 2 years ago. This suggests NocoDB is being more actively maintained.
Both tools share common technology foundations, being built with JavaScript, CSS, Typescript, JSX. However, they differ in their additional technology choices: NocoDB uses Bash, SCSS, Vue, NestJS, Nuxt.js.
NocoDB has been in development longer, starting 9 years ago, compared to Rowy which began 7 years ago. This 1.9-year head start suggests NocoDB may have more mature features and established processes.
The projects use different licenses: NocoDB is licensed under AGPL-3.0 while Rowy uses Apache-2.0. Consider the licensing requirements when choosing for your project.
Both tools serve similar use cases in Low-Code/No-Code. However, they also have distinct specializations: NocoDB also focuses on Database Tools & GUIs while Rowy extends into Backend-as-a-Service (BaaS).
NocoDB provides self-hosting options for complete data control and customization, while Rowy may be primarily cloud-based or require different deployment approaches.