Database Modeler
Reverse-engineer any database into a clean data model
Connect Postgres, MySQL, Snowflake, BigQuery, Redshift or Databricks. OffDataAI reads the catalog, finds the relationships nobody declared, classifies every table, and builds a project you can modernize.
source snowflake · ANALYTICS.PUBLIC tables 142 read (catalog only, no rows) inferred relationships orders.cust_id → customers.id 0.94 ✓ order_items.order_id → orders.id 0.97 ✓ payments.ord_ref → orders.id 0.71 review classification orders fact grain: one row per order customers dimension SCD 2 · PII: email, phone order_items fact grain: one row per line stg_orders_raw staging excluded build remodel → Kimball · target: snowflake
Most real databases were never designed on a whiteboard. Foreign keys are missing, staging tables sit next to facts, and the only documentation is in someone's head. Rebuilding a model from that by hand takes weeks.
The Database Modeler does the archaeology for you. It reads only the catalog, never your rows, then infers undeclared relationships with a confidence score and the evidence behind each one. Every table is classified as a fact, dimension, bridge, lookup, staging table and more, with grain, PII and history detected. Review the result, then build a project: mirror the schema 1:1, or let AI remodel it as a star schema or Data Vault for the warehouse you are moving to.
What the Database Modeler does
Catalog-only introspection
Tables, views, columns, keys, indexes, constraints and comments, read from the catalog. No rows are selected, and credentials are encrypted at rest.
Relationship inference you can review
Undeclared foreign keys are suggested with a confidence score and evidence. Accept, reject or bulk-accept; only accepted ones are used.
Automatic classification
Facts, dimensions, bridges, lookups, staging and audit tables, plus column roles, PII, SCD type, grain and subject area.
Mirror or remodel
Keep the schema 1:1 for documentation, or remodel it as a Kimball star schema or Data Vault 2.0 for a new platform.
Schema drift
Re-analyze a source and compare snapshots to see exactly what changed before you rebuild.
From database to ontology
Use an imported schema as an ontology source and merge it with your warehouse model into one business vocabulary.
Frequently asked questions
Which databases can the Database Modeler read?
Does OffDataAI read my data?
What if my database has no foreign keys declared?
How are tables classified?
What can I build from an imported schema?
Can it detect schema changes?
Which plan includes the Database Modeler?
Explore OffDataAI
- Ontology builderTurn a data model into a published business ontology.
- MCP server for AI agentsGive Claude and other agents your tables, joins and metrics.
- Model BuilderDrag-and-drop data modeling on a full-screen canvas.
- AI data modeling toolDesign a data model from a plain-English description.
- Data model templates174 production-grade models to start from.
- DuckDB schema generatorNative DuckDB DDL and dbt from the same model.
Your data warehouse is one conversation away.
Describe your domain, or open one of 170+ production-grade templates. ERDs, DDL, and a complete dbt project — generated in under a minute.
