drawDB Hosting
Design database schemas visually with an editor that exports SQL and diagrams in your browser.
- One click deploy
- 1 GB RAM Memory needed
- 15 GB Disk Space Needed
- From 2 € Price
Tech
- Docker image
- ghcr.io/drawdb-io/drawdb:latest
- Default port
- 80
How drawDB works
drawDB provides a visual canvas for adding tables, fields, keys, and relationships, then arranging them into an entity-relationship diagram. Users can begin from an empty design or import supported SQL to reverse-engineer a starting schema. The editor can generate SQL and migration-oriented output from the model, helping teams move between discussion diagrams and implementation artefacts.
The upstream application is designed to work in a browser without requiring an account. Diagrams can be exported and imported, and visual output can be shared through generated files. The hosted package serves the editor but does not add a central organisation workspace, user directory, server-side diagram database, or subscription collaboration layer.
Key drawDB features
Table groups, notes, colours, relationship lines, layout controls, and editor customisation help explain a schema beyond raw SQL. Importing an existing script can reveal relationships and naming patterns, while generated SQL gives a project a useful draft for supported database dialects. Generated output should still be reviewed before it reaches a live database.
Browser persistence and export behaviour should be treated carefully. The hosted package has no declared persistent application volume or relational database for saved projects, so users should export important diagrams rather than assuming another browser, profile, or device will see them. Confidential production credentials are unnecessary and should not be pasted into a schema-design tool.
drawDB vs dbdiagram.io
drawDB offers visual schema editing, SQL import and export, migration generation, and account-free browser use. dbdiagram.io centres on diagrams written in DBML, with personal and team workspaces, sharing, real-time collaboration, private or password-protected diagrams, and professional features under its service plans.
dbdiagram.io may fit teams that want provider-managed workspaces and simultaneous editing around a textual schema language. drawDB is appealing for independent visual modelling, self-hosting, and file-based exchange, provided users establish their own process for versioning, review, collaboration, and durable storage.
Who uses drawDB
Developers sketch a new service database before writing migrations, architects review relationships across modules, and students learn normalisation by arranging tables visually. Teams can also import a legacy schema to make design discussions easier for people who do not want to read a long SQL file.
drawDB does not validate business rules, test migrations against production data, manage database credentials, or replace change-control tooling. An attractive diagram can still contain invalid types, unsupported syntax, missing indexes, or destructive migration choices, so generated scripts need database-specific review and testing.
Self-hosting drawDB: requirements and cost
The main workload runs in the visitor browser and grows with diagram size, number of tables, relationship density, SQL import complexity, and generated output. The catalogue marks the relational database as Not required because the hosted editor does not provision a project database. Browser memory and disciplined exports are more important than server-side storage for ordinary use.
On AvaHost, drawDB uses Plan 1 at €2. The hosted drawDB package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. No shared workspace, server-side project account, production database connection, or automatic migration execution is included. Users should export diagrams and review generated SQL in their normal version-control and database-change process.
F.A.Q
drawDB starts at €2 on Plan 1. The service is lightweight because most editing work happens in the browser. Very large schemas, dense relationship maps, complicated SQL imports, and several simultaneous viewers can increase client or server activity, but the entry plan is suitable for ordinary individual and small-team diagram work.
A custom domain can point to the hosted drawDB editor with automated HTTPS. The branded address makes the tool easier to share, but it does not create a private team workspace or per-user permissions. Anyone who can reach the page can load the editor, so share diagram files through an appropriate controlled channel.
The catalogue does not declare PostgreSQL, MariaDB, or a persistent server project store for drawDB. Treat exported diagram and SQL files as the durable copies, and do not rely on one browser profile as the only location. Save important work in your organisation’s approved repository or document system after each meaningful change.
The hosted package is a diagram and SQL-generation tool, not a database connection or deployment service. Review types, constraints, indexes, migrations, and destructive statements against the target engine before execution. Use your normal testing, backup, approval, and release process rather than assuming generated output is ready for production unchanged.