Generating diagrams

1. 1Describe the system in the prompt bar, or paste Terraform, SQL, dbt, or OpenAPI text, or attach files.
2. 2Name what matters. The technologies, zones, and tables you name are treated as a specification, not a suggestion.
3. 3Datadef generates an overview-scoped diagram a reader can follow in one pass, with icons for the technologies it recognizes.
4. 4Refine the result on the canvas or through the AI panel; every generated element stays editable.

• The dashboard prompt bar. Creates a new cloud project from a description or attached files.
• The scratch canvas at /scratch, without an account.
• The AI panel on the canvas. Edits the open diagram in place: "add a staging zone", "collapse the ingestion tier".
• An AI agent over MCP, with the create_diagram and edit_diagram tools. See MCP and agents.
• A connected repository, where the input is the code itself. See Repositories.

The diagram is only as detailed as the description. The generator does not pad a thin prompt with invented services, so the difference between a generic diagram and your platform is what you name:

• Name the actual technologies. "Snowflake, dbt, Airflow, Kafka, Fivetran" draws those, with their icons. "A data pipeline" draws a guess.
• Name the layers or zones you want. Zone names you give are treated as a specification, not a suggestion: ask for "bronze, silver, gold" and you get exactly those three zones.
• Name the tables that matter. Tables you name arrive as table nodes with columns, which is what makes column-level lineage possible later.

The prompt field accepts infrastructure and schema text directly. Paste Terraform resources, SQL DDL, a dbt_project.yml with model SQL, or an OpenAPI spec, and the generator reads the structure out of it rather than treating it as prose.

You can also attach files. Accepted types:

A reference image is recreated structurally: the generator reproduces its zones, nesting, and components in Datadef's own visual language. It does not trace pixels, and layout is recomputed.

Generation runs against an explicit size budget:

• Overview (the default): 12 to 20 nodes, no more connections than nodes. Repeated objects collapse into one node stating the count, and supporting tiers like governance or monitoring get at most one node each. This is the right scope for almost every request; a reader should follow the whole flow in one pass.
• Detailed: 25 to 40 nodes carrying full fields, schedules, contracts, and owners. Reserved for when depth is explicitly asked for. Today the detailed scope is exposed through the MCP create_diagram tool's scope parameter; in-app generation uses the overview budget.