Design a PostgreSQL schema visually
PostgreSQL has more to model than most databases: enums, arrays, domains, extensions, partitioned tables, exclusion constraints and row level security. DesignDB models those directly, so the diagram is the schema and not a simplified picture of it.
PostgreSQL features it understands
- Enums and composite types, array columns (including arrays of an enum), JSON and JSONB.
- Extensions such as PostGIS and pgvector, with their types offered in the type list.
- Declarative partitioning (range, list and hash) and EXCLUDE constraints.
- Partial and multi-column indexes, with the index method (btree, GIN, GiST and so on) and its parameters chosen per index.
- Schemas, views and materialized views.
Checks while you design
The schema checks flag common problems as you go: tables with no primary key, foreign keys with no index, columns whose names suggest a missing relationship. Each can be fixed in one click, and the fix can be undone.
From diagram to database
On Pro, export the diagram as PostgreSQL DDL, or generate a migration for Flyway, Liquibase, Atlas, golang-migrate, dbmate, Prisma Migrate, Drizzle Kit or Alembic, with warnings about steps that can lose data. Try it in your browser with no account: your diagrams stay in that browser. A free account saves up to 5 diagrams in the cloud, with up to 50 tables each. Importing and exporting SQL and other formats, sharing, comments and version history are part of Pro.
Schemas to start from
Questions
Does it support PostGIS and pgvector?
Yes. Both have templates (a geospatial store locator and an AI knowledge base), and their types and indexes are available in the editor.
Can I get a migration instead of a full dump?
On Pro: paste the schema your database has now, and DesignDB writes the SQL that brings it to your diagram, with a roll back script.
Does it connect to my database?
No. To read an existing schema you run a read-only query in your own client and paste the result, so DesignDB never needs access or credentials.