Back to all posts

DBeaver Alternatives for Visual Database Design: 5 Tools Compared

Five tools that replace or sit beside DBeaver when the job turns from querying a database to designing one.

On this page

The release needs three tables nobody has created yet, DBeaver is open on the second screen, and the diagram from the last design review is a PNG in a wiki. For that work, the DBeaver alternative is DbSchema: it reverse-engineers the database into a diagram you edit, keeps the design in a model file you commit next to the code, and generates the migration SQL from the difference between that file and the live database. pgAdmin, DbVisualizer, Navicat Premium and dbForge Studio divide the same job differently, as the sections below show.

Short answer

DBeaver is a SQL client, and editing its ER diagrams is a paid Enterprise feature. DbSchema is built for the design side, with a model file, virtual foreign keys and a compare that writes the ALTER script, and its Community Edition is free for any use.

  • Design a schema, keep it in Git and generate migrations: DbSchema.
  • PostgreSQL-only administration with an ERD tool, free: pgAdmin.
  • DBeaver itself puts ERD editing, schema compare and Git sync in Enterprise and Ultimate.

DBeaver is a good SQL client, but its ERD editing is paid

DBeaver is good at what a SQL client is for: connecting to many engines, running queries, browsing and editing rows. DBeaver's own site, read on 3 November 2026, describes DBeaver Community as a free, open-source database management tool. The search for an alternative starts when the task changes from reading a database to producing one, because the design work needs things a live connection does not hold: a design that exists before the database does, a diagram layout that survives being closed, and a change script someone can review before it runs.

DBeaver's edition and pricing page, read the same day, places that work in its paid line. Database schema development in ERD Edit mode, schema compare and migration, and syncing projects to a Git repository are listed for Enterprise, Ultimate and Team, and not for Lite. So the question is less "is DBeaver good" than "which tool should own the schema", and whether that tool also replaces DBeaver for queries.

A diagram drawn from the live connection shows the foreign keys the database declares, and nothing else. Many schemas carry links that were never declared. This PostgreSQL schema has one of each:

CREATE TABLE customers (id int PRIMARY KEY, name text);
CREATE TABLE orders (id int PRIMARY KEY, customer_id int REFERENCES customers(id));
CREATE TABLE invoices (id int PRIMARY KEY, order_id int);
INSERT INTO customers VALUES (1, 'Ana'), (2, 'Ben');
INSERT INTO orders VALUES (10, 1), (11, 2);
INSERT INTO invoices VALUES (100, 10), (101, 11), (102, 99);

The catalog, which is what a client reads to draw its lines, knows only the first link:

SELECT tc.table_name, kcu.column_name, ccu.table_name AS references_table
FROM information_schema.table_constraints tc
JOIN information_schema.key_column_usage kcu ON kcu.constraint_name = tc.constraint_name
JOIN information_schema.constraint_column_usage ccu ON ccu.constraint_name = tc.constraint_name
WHERE tc.constraint_type = 'FOREIGN KEY';

Result · PostgreSQL 17.6

table_namecolumn_namereferences_table
orderscustomer_idcustomers

The undeclared link is also the one nothing checks. A LEFT JOIN finds an invoice whose order does not exist:

SELECT i.id AS invoice_id, i.order_id
FROM invoices i LEFT JOIN orders o ON o.id = i.order_id
WHERE o.id IS NULL;

Result · PostgreSQL 17.6

invoice_idorder_id
10299
customers, orders and invoices: a declared foreign key from orders to customers and an undeclared link from invoices to orders, drawn dashed as a virtual foreign key
Figure 1The catalog lists the solid line only. The dashed one exists in the data and in a DbSchema model, not in PostgreSQL.

In DbSchema you add the missing line as a virtual foreign key: it exists only in the model, DbSchema never creates it in the database, and the Query Builder and Data Explorer follow it like a real one. Keeping it means saving the model file, which is DbSchema Pro.

Five alternatives split the design work in different ways

DbSchema is a desktop design and query tool for relational and NoSQL databases (its databases page lists 100+ engines). It reverse-engineers a live schema into diagrams and keeps the design in a model file. Editing a diagram changes the model only. The database changes when you choose Database → Create or Upgrade Model in the Database, or apply rows from the synchronization dialog, which lists each difference between model and database and the SQL it would run. Connecting, reverse-engineering, diagrams and the SQL editor are in the free Community Edition; saving the model, synchronization, HTML5 documentation, the Query Builder and the Data Explorer are Pro.

The Synchronize Model and Database dialog with three differences between the DbSchema model and the database, and the ALTER TABLE statement for the selected one
  1. 1Column present in the model, absent in the database
  2. 2The ALTER TABLE that runs on the database
  3. 3Generate SQL script instead of running it
Figure 2Each row is one difference. You pick the side that wins and DbSchema shows the statement it would run.

pgAdmin's site describes pgAdmin 4 as the open-source graphical management tool for PostgreSQL, at version 9.19 since 29 October 2026, running as a desktop application or as a web application. Its documentation says the ERD Tool designs tables and relationships, generates a diagram from an existing database, generates ready-to-run SQL from the design and saves the diagram to a file. It works with PostgreSQL only.

DbVisualizer is a SQL client over JDBC. Its user guide says the References graph shows how tables relate through foreign keys, and exports it as an image or a GML file. Schema comparison is Pro only, and the same guide says it does not fully show the differences between two schemas.

Navicat Premium is a multi-engine GUI client for MySQL, PostgreSQL, MongoDB, MariaDB, SQL Server, Oracle, SQLite, Redis and Snowflake, with a Model feature for data modelling, according to its product page. Its store lists Enterprise, Standard and Non-Commercial editions, with the data modelling tool in Enterprise and Non-Commercial, sold per user as a perpetual licence with a year of maintenance included. A free Navicat Premium Lite is also offered.

dbForge Studio is an IDE sold per engine; Devart's editions page says the SQL Server product comes in Enterprise, Professional, Standard and Express editions, and Express activates when the trial expires. Its ordering page offers each paid edition as a subscription or as a perpetual licence.

The licence model differs more than the feature list

Prices come from each vendor's own page, read on 3 November 2026, per user and excluding tax. Where a vendor's page shows no price, the cell names the licence model.

Cross-engine clients

DbSchema is the cross-engine client with a free edition for any use and a one-time Pro licence:

ToolBuilt forEnginesFree tierPaid licence
DbSchemaDesign, migration, documentation, queries100+ SQL and NoSQLCommunity Edition, for any usePro 294 USD one-time or 29.40 USD a month
DbVisualizerSQL clientJDBC databases, incl. MongoDB and CassandraFree, standard feature setPro 199 USD first year, then 89 USD a year
Navicat PremiumMulti-engine administrationNine engines incl. MongoDB, Redis, SnowflakeNavicat Premium LitePerpetual, per user, three editions

DBeaver itself and single-engine tools

DBeaver charges a yearly fee per edition, while pgAdmin and dbForge Studio each stay on one engine:

ToolBuilt forEnginesFree tierPaid licence
DbSchemaDesign, migration, documentation, queries100+ SQL and NoSQLCommunity Edition, for any usePro 294 USD one-time or 29.40 USD a month
DBeaverSQL client and administrationSQL and NoSQLCommunity, open sourceLite 113, Enterprise 255, Ultimate 510 USD a year
pgAdmin 4PostgreSQL administrationPostgreSQLOpen sourceNone
dbForge StudioOne engine per productSQL Server (separate MySQL product)Express editionSubscription or perpetual

The licence column decides more than it looks. DBeaver's ERD editing starts at Enterprise, 765 USD over three years. DbSchema Pro is 294 USD once with the first year of updates, and the optional renewal is 75 USD a year, 444 USD over three years if you renew both times (DbSchema purchase page). DbVisualizer's pricing page says every subscription includes a perpetual usage licence for the versions released during the term.

DBeaver and DbVisualizer differ mostly in licence and editions

Both are SQL clients over JDBC, so the split is licensing and edition boundaries rather than what they are for. DbVisualizer Free has the standard feature set; Pro adds table management, the query builder, explain plan, import and export, and the command line, at 199 USD per user for the first year and 89 USD a year after. DBeaver charges per edition per year and puts ERD editing and schema compare in Enterprise.

DbVisualizer's References graph is drawn from the foreign keys the connection reports, which is the limit the query above shows, and DBeaver keeps ERD editing in its paid editions. DbSchema adds that layer, and its SQL editor, in the free Community Edition, runs the day-to-day queries either of them would have handled.

pgAdmin covers PostgreSQL in depth and no other engine

For PostgreSQL alone, pgAdmin goes deeper: it is the open-source tool for administering, developing and monitoring PostgreSQL, and it is free. DBeaver goes wider across engines. Once a second engine appears in the project, pgAdmin no longer covers it, while DbSchema puts PostgreSQL, MySQL, MongoDB and the rest of its engines into one model, with MongoDB collections inferred from their documents and drawn next to the relational tables.

DbSchema leaves you a model file you review in Git

The three differ in the artifact you end up owning. DbSchema hands you a model file that holds the schema, every diagram and layout, and the virtual foreign keys. You commit it from inside DbSchema with File → Git Collaboration, so a schema change reads as added and removed lines in a pull request (DbSchema Git). Committing changes the repository; the database changes only when you synchronize. File → Export As... → HTML5/PDF Documentation turns the same model into a page a colleague opens in a browser (schema documentation). A design that exists before the database does is DbSchema Architect's logical design: entities and relations with no connection open, turned into the physical model with Model → Generate Physical Model once the engine is chosen.

DbSchema model your design

  • Tables, keys and virtual foreign keys
  • Diagram layouts and groups
  • Committed to Git as a file
  • Compared with the database before anything runs

Live database what runs

  • Declared foreign keys only
  • No layout
  • Changed by the SQL you apply
  • What every client reads

Navicat Premium covers several engines in one client with a modelling tool in two of its editions. dbForge Studio goes the other way, with one product per engine and its code completion and automation written for SQL Server or MySQL specifically. If your week mixes schema work with server administration, DbSchema owns the schema and one administration client covers the servers.

Switching from DBeaver keeps your database, drivers and scripts

The database carries over untouched, because both products reach it over JDBC drivers: host, port, credentials and driver parameters mean the same thing in DbSchema, and saved .sql scripts open in the DbSchema SQL editor. DbSchema reverse-engineers the schema in one pass with every declared foreign key drawn, so nothing about the existing structure is retyped.

Two things you set up once. Connections are entered again, because each product keeps its own store, and the diagram layout is arranged again: Diagram → Auto Arrange Tables lays the tables out by their foreign keys, and from then on the layout is saved in the model file (DbSchema diagrams).

Test it on a schema you already know. Download DbSchema, connect it to the database DBeaver already uses and reverse-engineer it into a diagram, which the free Community Edition covers. Saving the model, Git, virtual foreign keys that persist, synchronization and HTML5 documentation are in DbSchema Pro, and logical design before the database exists is in DbSchema Architect. The 15-day trial in the download covers both.

FAQ

What is the best DBeaver alternative for visual database design?

DbSchema, when the job is designing rather than querying. One model file holds several diagrams of the same schema, the virtual foreign keys the database lacks, and the design that DbSchema compares against a live database to generate the migration SQL.

Can I keep using DBeaver alongside DbSchema?

Both reach the database over JDBC, and neither locks the other out. DbSchema downloads the right driver the first time you connect, and the Driver Manager accepts an uploaded .jar where a machine has no internet access.

Does DBeaver support offline schema design?

DBeaver's ERD editing is listed for its Enterprise, Ultimate and Team editions. DbSchema has an offline mode: Database → Offline (connect later) lets you edit tables, columns and keys with no database attached, and when you connect again DbSchema lists the differences for you to apply. Saving that design to a model file is Pro.

Does DbSchema support Git versioning?

DbSchema saves the design as a model file and versions it from File → Git Collaboration, where you clone, commit, push and pull (DbSchema Git). Saving the model to a file is a Pro feature.

Is DBeaver free for commercial use?

DBeaver Community is free and open source, and the PRO editions in the table above are the paid line. DbSchema Community Edition is free for any use, commercial work included.

Sources

  1. DbSchema purchase page
  2. DbSchema foreign keys
  3. DbSchema schema synchronization

Design the schema DBeaver queries

DbSchema reverse-engineers your database into diagrams, keeps the design in a model file you commit to Git, and compares it with the live database before anything runs. Connecting, reverse-engineering and diagrams are in the free Community Edition, and DbSchema Architect adds logical design before the database exists.