What Is DBModeler?
DBModeler is a browser-based ER diagram editor focused on designing relational schemas, organizing them as projects, and generating versioned SQL output.
It combines three layers of work in a single tool:
- visual schema modeling for tables, fields, and relationships
- project-level configuration for engine, schema defaults, and storage
- versioning workflows for snapshots, diffs, and migration SQL
What you can do in DBModeler
Section titled “What you can do in DBModeler”DBModeler is built for day-to-day schema work rather than just drawing diagrams.
- Create and manage projects for different databases or environments.
- Model tables, fields, constraints, and foreign-key relationships.
- Import existing SQL into a diagram.
- Export SQL for supported engines.
- Create sequential versions and generate migration scripts.
- Add custom SQL scripts per version.
- Connect projects to GitHub or GitLab.
- Store projects locally or sync them through cloud providers.
What makes it different
Section titled “What makes it different”It runs in the browser
Section titled “It runs in the browser”The application is front-end only. There is no server-side schema editor behind the UI. Project data lives in browser storage and, when you choose it, in your own connected providers.
It is project-based
Section titled “It is project-based”Each schema is stored as a project. A project includes the diagram, engine configuration, versions, custom scripts, and integration settings.
It is version-aware
Section titled “It is version-aware”DBModeler does not stop at drawing tables. It keeps version history so you can compare changes and generate SQL for both initial schema creation and later migrations.
Storage and ownership model
Section titled “Storage and ownership model”DBModeler is designed around the principle used across the product site: your data stays in your storage choices.
- Local projects are stored in the browser.
- Cloud-backed projects sync through Google Drive, OneDrive, or Dropbox.
- Git-backed workflows generate SQL artifacts in your own repositories.
Sensitive credentials such as refresh tokens can be protected with the built-in secret manager and a master password.
What this documentation covers
Section titled “What this documentation covers”This documentation site is split into two product-facing areas:
- User Guide for onboarding, modeling, export, versioning, and integrations.
- Development for future internal and contributor-facing technical notes.
If you are new to the product, continue with Quickstart or Browser-Only Architecture.