Back to all posts

DBeaver Alternative for Database Design: DbSchema, Edition by Edition and Price by Price

For DBeaver users who now have to design a schema, get it reviewed and document it before it reaches a server.

On this page

You query and browse your databases in DBeaver, and the next job is a table that no database has yet. It has to be drawn, reviewed and agreed before it reaches a server. For that work, the DBeaver alternative is DbSchema. DbSchema keeps the design in a model file that your team reviews in Git, compares the file with the live database, and exports documentation that opens in a browser.

Both tools have a free edition. DbSchema's Community Edition connects to every database that DbSchema supports, reverse-engineers it into an editable diagram, and includes the SQL editor. The offline model file, Git, schema synchronization and documentation of any size need DbSchema Pro. DBeaver Community is free and open source, and DBeaver puts diagram editing, schema compare and Git sync in its paid Enterprise, Ultimate and Team editions. Every DBeaver fact below comes from dbeaver.com, checked on 12 November 2026.

Try DbSchema on your own database

Free Community Edition plus a 15-day Architect trial. No signup. Windows, macOS and Linux.

DBeaver edits diagrams only in paid editions, straight into the database

DBeaver's ER diagram documentation says that "diagrams are read-only by default". DBeaver draws a line for each foreign key that the database reports. It also draws one for each virtual key, a relation that exists only in DBeaver. A custom diagram can hold only objects that already exist in the database. If your DBeaver diagram shows two related tables with no line between them, the three usual causes and their fixes are a separate question.

Edit mode turns the diagram into a schema editor. To add a table, you right-click an empty area of the canvas and choose Create New Table. When you click Save, DBeaver shows the generated SQL script and applies it to the database. The Edit mode page names Enterprise and Ultimate, and DBeaver's editions page adds Team.

The ER diagram of a PostgreSQL schema in DBeaver Enterprise 25.0, with the Edit Mode and Save buttons in the toolbar under the diagram

Edit mode suits a change to a server that you own. A design that has to be reviewed first needs a place to live until the review ends. In Edit mode, saving the diagram changes the database, so no design file waits in a pull request.

DBeaver Edit mode saves a diagram to the database as an SQL script; DbSchema, designing offline, saves it to a model file that is reviewed in Git and compared with the database before a migration script runs
Figure 1In DBeaver, Save reaches the database. In DbSchema, the database changes only at the last step, after the review.

Each design capability sits in a different edition of each tool

Each cell names the edition that a capability needs, because the edition decides the bill. The DBeaver values come from its editions page and the documentation pages linked in this article:

CapabilityDbSchemaDBeaver
Diagram of an existing databaseCommunity, editableRead-only by default
Edit tables on the diagramCommunity, into the database at onceEdit mode, Enterprise, Ultimate and Team, into the database on Save
Keep the design in a file before it runsThe model file, ProSave in Edit mode runs the script
Relations the database doesn't declareVirtual foreign keys, kept in the model file, ProVirtual keys, stored in DBeaver
Schema comparisonModel with database, or model with model file, ProTwo schemas or databases, Enterprise, Ultimate and Team
Version controlThe model file through File → Git Collaboration, ProProject sync to Git, Enterprise, Ultimate and Team; an extension for Community
Documentation and exportHTML5, PDF and Markdown, Pro; up to 12 tables in CommunityDiagram as PNG, GIF, BMP or GraphML; SVG in paid editions
Test dataData Generator, ProMock data generation, Enterprise, Ultimate and Team
MongoDBCommunityLite, Enterprise and Ultimate
Visual query builderProLite, Enterprise and Ultimate
SQL editorCommunityCommunity
LicensePerpetual with a year of updates, or monthlyYearly or monthly subscription

The two schema comparisons answer different questions. DBeaver's schema compare reads the structure of two schemas or databases. It produces the DDL that makes the target match the source, and warns that the migration "can't be undone automatically". DbSchema compares the agreed design with the running database. It shows how far production has drifted from the model.

Over three years DbSchema Pro costs 321 USD less than DBeaver Enterprise

Schema compare and Git sync start at DBeaver Enterprise, at 255 USD a year or 26 USD a month. Ultimate costs 510 USD a year, and its product page also sells it at 51 USD a month. DBeaver's license documentation marks perpetual licenses as discontinued after version 23.3. A DBeaver subscription blocks access after it expires.

DbSchema Pro costs 294 USD once, with the first year of updates included. After that, updates cost 75 USD a year, and the license keeps working if you stop. Over three years, one user pays 444 USD for DbSchema Pro with two update years, and 765 USD for DBeaver Enterprise. DbSchema Pro is also sold at 29.40 USD a month, with every update included while the subscription runs. All DbSchema prices are on the purchase page.

Bar chart of three-year cost for one user: DbSchema Pro 444 USD, DBeaver Enterprise 765 USD, DBeaver Ultimate 1,530 USD
Figure 2Three years for one user, at list prices without tax.

DbSchema keeps the design in a file your team reviews first

In DbSchema, right-click the diagram and choose Create Table. To draw a foreign key, drag the child column onto the parent column. While DbSchema is connected, every change that you confirm with OK runs in the database at once, as in DBeaver's Edit mode. The difference is offline work. Choose Database → Offline (connect later), and your changes stay in the model, so you can design a schema that no server has yet. Saving the model with File → Save Model to File needs DbSchema Pro.

For a relationship that the database never declared, tick Virtual in the foreign key dialog. DbSchema draws the line and never creates the key in the database. Model → Find Virtual Foreign Keys suggests such keys between columns with matching names.

The model is one .dbs file that holds the tables, the foreign keys, virtual ones included, and the diagrams. File → Git Collaboration opens DbSchema's Git dialog, which clones a repository, commits the file, pushes and pulls. A colleague then reviews a schema change in a pull request, like code. Committing changes the repository, not the database.

The Git dialog in DbSchema for the model shop.dbs, with the commits of two people, a merge, and Pull and Push buttons

When the design is agreed, schema synchronization compares the model with the database. The Synchronize Model and Database dialog lists every difference, one per row. For each row you choose which side wins. Then press Apply to the model, Commit in the database, or Generate SQL script to review the statements first.

The Synchronize Model and Database dialog in DbSchema with three differences: birth_date in customers and the rename of carrier_name set to the database, the table suppliers set to the model, and the ALTER TABLE statement of birth_date below
  1. 1Create birth_date in the database
  2. 2The statement that would run
  3. 3Generate SQL script for review
Figure 3Each difference between model and database is one row, and the bottom pane shows the statement that the chosen action would run.

To share the design with people who don't run DbSchema, choose File → Export As... → HTML5/PDF Documentation. The HTML5 documentation is one file that opens in any browser. It carries the diagram as a vector image, with table and column comments as mouse-over tooltips. DbSchema Pro documents any diagram. The Community Edition documents a diagram of up to 12 tables, with "DbSchema Trial" across the diagram image.

The Data Explorer, in DbSchema Pro, follows the foreign keys, virtual ones included. Select a customer, and the pane beside it shows only that customer's orders. The Data Generator, also in Pro, fills the tables with test rows.

Other DBeaver alternatives draw the keys that already exist

Most DBeaver alternatives are SQL clients. For design work, what separates them is the diagram. In some, the diagram is a picture of the keys that the database already has. In others, the diagram is a model that you change before the database has it. The job in this article needs a model that lives apart from the database, and DbSchema and Navicat Premium both keep one. The vendor pages below were checked on 12 November 2026.

DataGrip's diagram documentation generates a diagram from existing database objects, with relations from their primary and foreign keys. You add a table by dragging it from the Database Explorer. DataGrip exports a diagram as PNG, GraphML, draw.io, Mermaid or PlantUML.

DbVisualizer's references graph "automatically renders all primary/foreign key mappings", in both the Free and Pro editions. It exports the graph as PNG, SVG, PDF and other image formats.

Navicat Premium connects to MySQL, PostgreSQL, SQL Server, Oracle, SQLite, MariaDB, MongoDB, Redis and Snowflake. Its feature matrix lists conceptual, logical and physical models, and synchronizing a model to the database, both in the Enterprise edition.

For the wider field, see DBeaver alternatives for visual database design and Best ER Diagram Tools.

Switching takes three steps against the same database

Both tools connect over JDBC, so you can keep DBeaver open on the same database while you design in DbSchema. DBeaver's editions page puts a task scheduler and table data comparison in Enterprise and Ultimate, for databases that already run. DbSchema covers the step before: what the schema should be, and who agreed to it.

  1. Connect to the same database Community

    In DbSchema, choose Connect to Database, pick the engine, and enter the host, user and password that you use in DBeaver. DbSchema downloads the JDBC driver on the first connection.

  2. Reverse-engineer the schema Community

    In the Reverse Engineer the Database dialog, tick the schemas to import and press Load. DbSchema draws their tables and foreign keys on an editable diagram.

  3. Save the model and commit it Pro

    Save with File → Save Model to File, then commit the .dbs file from File → Git Collaboration.

A DbSchema diagram with the tables countries, addresses, customers, payments, orders and order_items, and the foreign key lines between them

To try the workflow on your own schema, download DbSchema and connect it to a database that you already open in DBeaver. Connecting, reverse-engineering, the editable diagram and the SQL editor are in the free Community Edition. The offline model file, Git, schema synchronization, documentation of any size, the Data Explorer and the Data Generator are in DbSchema Pro. A new installation starts with a 15-day trial of the Architect edition, which has every feature.

Sources

  1. DBeaver Community
  2. DBeaver: ER diagrams
  3. DBeaver: Virtual keys
  4. DBeaver: Custom diagrams
  5. DBeaver: Edit mode
  6. DBeaver: Editions
  7. DBeaver: Schema compare
  8. DBeaver: Ultimate
  9. DBeaver: Differences between license types
  10. DataGrip: Diagrams
  11. DbVisualizer: References graph
  12. Navicat Premium
  13. Navicat Premium: Feature matrix
  14. DbSchema: Purchase
  15. DbSchema documentation: Schema synchronization
  16. DbSchema documentation: Git Collaboration
  17. DbSchema documentation: Schema documentation

Switch to a design-first workflow

DbSchema covers ER diagrams, documentation, Git-friendly model files and schema sync. Start on the free Community Edition and upgrade when your team is ready.