Learn how NocoBase 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.
Stars
Forks
Last commit
Repository age
Self-hosted
Auto-fetched .

Stars
Forks
Last commit
Repository age
Warning: This project hasn't been updated in 1 year and might not be actively maintained anymore.
Auto-fetched .

NocoBase appears to have several advantages over Rowy, particularly in popularity, activity and features. Consider your specific needs regarding popularity, activity, maturity and features when making your decision.
NocoBase significantly outpaces Rowy in community adoption with 22,152 stars compared to 6,804 stars on GitHub. This 3.3x difference suggests NocoBase has a much larger and more active community. In terms of developer contributions, NocoBase has 2,549 forks, indicating strong developer engagement.
NocoBase shows more recent development activity with its last commit 10 hours ago, while Rowy was last updated 1 year ago. This suggests NocoBase is being more actively maintained.
Rowy has been in development longer, starting 7 years ago, compared to NocoBase which began 5 years ago. This 1.2-year head start suggests Rowy may have more mature features and established processes.
Both tools serve similar use cases in Low-Code/No-Code. However, they also have distinct specializations: NocoBase also focuses on PaaS & Deployment Tools while Rowy extends into Backend-as-a-Service (BaaS).
NocoBase provides self-hosting options for complete data control and customization, while Rowy may be primarily cloud-based or require different deployment approaches.