Learn how DBeaver 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
11 yearsVersion
26.2.3License
Apache-2.0Repository
dbeaver/dbeaver
Last 30 days
Last commit
1 day agoRepository age
9 monthsVersion
v0.30.0License
Apache-2.0Repository
tabularis
Both DBeaver and Tabularis have their unique strengths and serve similar purposes effectively. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
DBeaver significantly outpaces Tabularis in community adoption with 52,257 stars compared to 5,350 stars on GitHub. This 9.8x difference suggests DBeaver has a much larger and more active community. In terms of developer contributions, DBeaver has 4,439 forks, indicating strong developer engagement.
Tabularis is growing faster, adding 249 stars in the last 30 days (+4.9%) against adding 312 stars for DBeaver (+0.6%). Tabularis 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 11 hours ago and Tabularis 1 day ago.
Both tools share common technology foundations, being built with JavaScript, CSS, Bash. However, they differ in their additional technology choices: DBeaver uses C, Objective-C, Java, C++ while Tabularis leverages Typescript, JSX, Python, Rust, Tauri.
DBeaver has been in development longer, starting 11 years ago, compared to Tabularis which began 9 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.