DBeaver is a database client that connects to almost anything with a JDBC driver. PostgreSQL, MySQL, MariaDB, SQLite, Oracle, SQL Server, DB2, Snowflake, BigQuery, Redshift, ClickHouse and dozens more, with the enterprise edition adding MongoDB, Cassandra, Redis and other non-relational stores. For anyone whose work spans several database engines, the value is not having to learn a different client for each one.
The SQL editor is the part used most: syntax highlighting, completion aware of your actual schema, execution plans, query history, and the ability to run a script and see multiple result sets. Results are editable in place, so correcting a row does not require writing an update statement, and the grid handles large result sets without loading everything into memory. Data can be exported to CSV, JSON, XML, SQL inserts or an Excel file, and imported back the same way.
Beyond querying, DBeaver covers schema work: a visual entity-relationship diagram generated from the live database, DDL generation, comparison between two schemas, and a data transfer tool that moves tables between different database engines, which is the least glamorous and most frequently useful feature in it. Connections can be tunnelled over SSH, which is how most people reach a production database safely.
The community edition is free and open source under the Apache licence, and it is not crippled. The paid enterprise edition adds NoSQL support, advanced security features, cloud service integrations and a visual query builder, and there is a browser-based team edition. Most individual developers never need to leave the free version.
The criticisms are consistent: DBeaver is a Java application built on Eclipse, so it carries a noticeable memory footprint and a startup delay, and the interface is dense with menus in a way that reflects its Eclipse ancestry rather than modern design. Newcomers find it cluttered. The trade is breadth: nothing else connects to as many things from one window.
Who it suits: developers, analysts and administrators working across multiple database engines, and anyone who needs to move data between them. Who should look elsewhere: people working with exactly one database who would prefer a lighter, native client.