Learn how Budibase 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
Self-hosted
Repository

Last 30 days
Last commit
Repository age
Version
License
Repository

Budibase appears to have several advantages over Rowy, particularly in popularity, activity and features. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
Budibase significantly outpaces Rowy in community adoption with 28,221 stars compared to 6,833 stars on GitHub. This 4.1x difference suggests Budibase has a much larger and more active community. In terms of developer contributions, Budibase has 2,196 forks, indicating strong developer engagement.
Budibase and Rowy are moving at much the same rate, adding 80 stars and adding 9 stars respectively over the last 30 days (+0.3% vs +0.1%). Neither is pulling away from the other on momentum alone.
Budibase shows more recent development activity with its last commit 7 hours ago, while Rowy was last updated 2 years ago. This suggests Budibase 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: Budibase uses Bash, Next.js, Nuxt.js.
Both projects started around the same time, with Budibase beginning 7 years ago and Rowy 7 years ago.
Rowy 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. However, they also have distinct specializations: Rowy extends into Backend-as-a-Service (BaaS).
Budibase provides self-hosting options for complete data control and customization, while Rowy may be primarily cloud-based or require different deployment approaches.