Learn how Mathesar 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.
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 .

Mathesar appears to have several advantages over Rowy, particularly in activity, licensing and features. Consider your specific needs regarding popularity, activity, technology, maturity, licensing and features when making your decision.
Both tools have similar popularity levels, with Mathesar having 4,934 stars and Rowy having 6,805 stars on GitHub. In terms of developer contributions, Rowy has 545 forks, indicating moderate developer engagement.
Mathesar shows more recent development activity with its last commit 22 hours ago, while Rowy was last updated 1 year ago. This suggests Mathesar is being more actively maintained.
Both tools share common technology foundations, being built with JavaScript, CSS, Typescript. However, they differ in their additional technology choices: Mathesar uses Bash, Python, SCSS while Rowy leverages JSX.
Rowy has been in development longer, starting 7 years ago, compared to Mathesar which began 5 years ago. This 1.6-year head start suggests Rowy may have more mature features and established processes.
Mathesar is licensed under GPL-3.0, while Rowy's license terms are not publicly specified.
Both tools serve similar use cases in Low-Code/No-Code. However, they also have distinct specializations: Mathesar also focuses on Database Tools & GUIs while Rowy extends into Backend-as-a-Service (BaaS).
Mathesar provides self-hosting options for complete data control and customization, while Rowy may be primarily cloud-based or require different deployment approaches.