Learn how Dory and Tabularis differ in their key features, development activity, technology stack and community adoption, so you can decide which of these database tools & guis is best for you.
Last 30 days
Last commit
11 hours agoRepository age
10 monthsVersion
v0.37.3License
Apache-2.0Self-hosted
YesRepository
dorylab/dory
Last 30 days
Last commit
2 days agoRepository age
9 monthsVersion
v0.29.0License
Apache-2.0Repository
tabularis
Both Dory and Tabularis have their unique strengths and serve similar purposes effectively. Consider your specific needs regarding popularity, growth, activity, maturity, licensing and features when making your decision.
Tabularis significantly outpaces Dory in community adoption with 5,288 stars compared to 306 stars on GitHub. This 17.3x difference suggests Tabularis has a much larger and more active community. In terms of developer contributions, Tabularis has 395 forks, indicating moderate developer engagement.
Dory is growing faster, adding 19 stars in the last 30 days (+6.6%) against adding 221 stars for Tabularis (+4.4%). Dory is the smaller project of the two, so it is closing the gap rather than extending a lead.
Both projects show recent activity, with Dory last updated 11 hours ago and Tabularis 2 days ago.
Both projects started around the same time, with Dory beginning 10 months ago and Tabularis 9 months ago.
Both projects use the Apache-2.0 license, providing identical terms for usage and distribution.
Both tools serve similar use cases in Database Tools & GUIs.
Dory provides self-hosting options for complete data control and customization, while Tabularis may be primarily cloud-based or require different deployment approaches.