DEV.co
Open-Source Databases · drawdb-io

drawdb

DrawDB is a free, browser-based database diagram editor that lets you design entity-relationship diagrams (ERDs), generate SQL scripts, and export schemas without requiring an account. It supports major databases including PostgreSQL, MySQL, MariaDB, Oracle, SQL Server, and SQLite.

Source: GitHub — github.com/drawdb-io/drawdb
38k
GitHub stars
3.1k
Forks
JavaScript
Primary language
AGPL-3.0
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
Repositorydrawdb-io/drawdb
Ownerdrawdb-io
Primary languageJavaScript
LicenseAGPL-3.0 — OSI-approved
Stars38k
Forks3.1k
Open issues226
Latest releaseUnknown
Last updated2026-07-08
Sourcehttps://github.com/drawdb-io/drawdb

What drawdb is

Built in JavaScript/React with Tailwind CSS, DrawDB is a client-side SPA that uses IndexedDB for local persistence. It provides ERD visualization, SQL import/export, migration generation, and optional server-side sharing via drawdb-server. Licensed under AGPL-3.0.

Quickstart

Get the drawdb source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/drawdb-io/drawdb.gitcd drawdb# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Individual Schema Design & Documentation

Solo developers and small teams designing database schemas locally without cloud dependencies or account requirements. Suitable for quick prototyping and schema documentation in agile workflows.

SQL Learning & Database Education

Students and junior developers learning database design patterns. Visual ERD editor lowers entry barriers and immediate SQL generation reinforces schema-to-code mapping.

Cross-Database Schema Migration Planning

Teams planning migrations between PostgreSQL, MySQL, Oracle, or SQL Server. Import existing schemas and export targeted SQL dialects for validation before execution.

Implementation considerations

  • AGPL-3.0 licensing: Any network-accessible deployment must provide source access. Clarify whether your deployment model (SaaS, internal tool, embedded) triggers copyleft obligations.
  • Optional server component for sharing: Default client-only use requires no backend; sharing features need drawdb-server deployment and environment variable configuration.
  • Local storage via IndexedDB: Schemas persist in browser storage. No automatic cloud backup; users must export manually or set up server-backed sharing.
  • SQL dialect support: Import/export covers PostgreSQL, MySQL, MariaDB, Oracle, SQL Server, SQLite. Validate target database syntax if using advanced features.
  • No authentication layer: Desktop/local deployments have no user identity. Sharing relies on optional server; self-hosted instances need external auth if multi-user isolation required.

When to avoid it — and what to weigh

  • Proprietary/Closed-Source Deployments — AGPL-3.0 requires source code disclosure for network-accessible deployments. Requires careful legal review if integrating into proprietary products or SaaS offerings.
  • Enterprise Audit & Compliance Requirements — No evidence of audit logging, role-based access control, or compliance certifications (SOC 2, ISO 27001). Not suitable for regulated industries requiring formal security posture.
  • Large-Scale Collaborative Teams — Sharing requires optional server setup; no built-in multi-user conflict resolution, real-time collaboration, or permission granularity. Better for small teams or individual use.
  • Real-Time Data Sync or Live Schema Monitoring — No indication of live database connection or change-data-capture capabilities. Designed for design-time schema editing, not runtime monitoring.

License & commercial use

Licensed under AGPL-3.0 (GNU Affero General Public License v3.0). This is a copyleft license requiring that network-accessible modifications disclose source code. Desktop/local use without network sharing is less restrictive; hosted or integrated deployments require legal review.

Commercial use is permitted under AGPL-3.0, but with caveats: if you deploy DrawDB as a service or integrate it into a product accessible over a network, you must provide users access to the modified source code. Internal business tools and self-hosted deployments may be acceptable if not externally accessible. Legal review is strongly recommended before commercial deployment. Requires careful evaluation of your distribution model.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationAdequate
License clarityClear
Deployment complexityLow
DEV.co fitGood
Assessment confidenceHigh
Security considerations

Client-side processing means schemas never leave the browser unless exported or server sharing is used. No documented security audit or vulnerability disclosure policy. AGPL-3.0 source is publicly available; review code for secrets, input validation, and XSS/injection risks before deployment. Optional sharing server introduces additional attack surface; secure that component separately. IndexedDB storage is not encrypted at rest; sensitive schema data in local storage could be exposed if device is compromised.

Alternatives to consider

Lucidchart

Commercial, feature-rich, multi-user real-time collaboration, audit trails, compliance certifications. Higher cost; no open-source option.

DbSchema

Desktop + cloud options, advanced versioning and team collaboration, multiple database support. Proprietary licensing; steeper learning curve.

DBeaver (with ERD plugin)

Free, open-source (Apache 2.0), desktop-based, live database connectivity, schema reverse-engineering. Heavier client; less polished UI for pure ERD editing.

Software development agency

Build on drawdb with DEV.co software developers

DrawDB is ideal for teams needing lightweight, free schema design without vendor lock-in. Verify AGPL-3.0 licensing compliance for your deployment model. Contact us to assess fit with your architecture and commercial requirements.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Related on DEV.co

Explore the category and the services that help you build with it.

drawdb FAQ

Can I use DrawDB commercially?
AGPL-3.0 allows commercial use, but network-accessible deployments must disclose source. Desktop/internal tools have fewer restrictions. Consult legal counsel before deploying as a service.
Do I need a server to use DrawDB?
No. Default is client-only (browser + IndexedDB). Optional drawdb-server enables file sharing; without it, users export/import manually.
What databases are supported?
PostgreSQL, MySQL, MariaDB, Oracle Database, SQL Server, SQLite. Import/export works via SQL text; visual editor is database-agnostic.
Is there real-time collaboration?
No built-in real-time sync. Optional server supports sharing, but no live multi-user editing or conflict resolution. Designed for individual or small-team, non-concurrent workflows.

Work with a software development agency

Need help beyond evaluating drawdb? DEV.co is a software development agency offering software development services and web development for teams of every size. Our software developers and web developers build custom software, web applications, APIs, and open-source databases integrations — and maintain them long-term.

Evaluate DrawDB for Your Database Design Workflow

DrawDB is ideal for teams needing lightweight, free schema design without vendor lock-in. Verify AGPL-3.0 licensing compliance for your deployment model. Contact us to assess fit with your architecture and commercial requirements.