Learn how DBeaver and Dory 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
6 hours agoRepository age
11 yearsVersion
26.2.5License
Apache-2.0Repository
dbeaver/dbeaver
Last 30 days
Last commit
2 days agoRepository age
10 monthsVersion
v0.37.3License
Apache-2.0Self-hosted
YesRepository
dorylab/dory
Both DBeaver and Dory 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.
DBeaver significantly outpaces Dory in community adoption with 52,437 stars compared to 314 stars on GitHub. This 167.0x difference suggests DBeaver has a much larger and more active community. In terms of developer contributions, DBeaver has 4,455 forks, indicating strong developer engagement.
Dory is growing faster, adding 10 stars in the last 30 days (+3.3%) against adding 350 stars for DBeaver (+0.7%). 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 DBeaver last updated 6 hours ago and Dory 2 days ago.
DBeaver has been in development longer, starting 11 years ago, compared to Dory which began 10 months ago. This 10.4-year head start suggests DBeaver may have more mature features and established processes.
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 DBeaver may be primarily cloud-based or require different deployment approaches.