New Bring your own storage. Keep your diagrams in your own private GitHub repository, on Pro and Team.Bring your own storage on GitHub, for Pro and Team. Learn more about bring your own storage

changelog

New features, improvements, and fixes to the Zindex platform.

Week of · 6 changes · Every week

new

FK edges anchor at the named column row in ER diagrams

ER edges now anchor at the FK column row inside each entity, precisely connecting to the column that carries the foreign key relationship. When an edge's label matches a column declared in either endpoint's extensions.columns, the engine auto-promotes the edge to a column-row anchor and drops the label - the column position carries the FK identity. Agents can also set endpoint.column directly. Set style.forceLabel: true on an edge to keep its label visible.

new

Canvas auto-extends to fit computed layout

The layout engine now automatically expands the scene canvas when auto-positioned nodes overflow the declared dimensions. A CANVAS_AUTO_EXTENDED diagnostic is emitted so agents know the canvas grew. Declared dimensions are treated as a minimum, not a hard cap - no more clipped diagrams when layout is denser than expected.

improved

Dark and sketch theme edge contrast

Edge strokes in dark and sketch render themes now use higher contrast values, improving legibility on dense diagrams. Container outline visibility in the sketch theme was also raised.

improved

Payment Processing playground example

The built-in Flow example in the playground has been replaced with a richer Payment Processing reference diagram that demonstrates gateway routing, parallel flows, and service integrations at a realistic scale.

fixed

Converging edges no longer render as invisible duplicates

Multiple edges arriving at the same target port are now fanned across adjacent anchor slots. Previously, edges sharing an exact port produced visually identical paths that stacked on top of each other and rendered as a single line.

fixed

Diverging edges no longer stack at a single source anchor

When a node has multiple outgoing edges leaving the same face, the router now distributes their exit anchors evenly along the face. Previously, hub fanout patterns - an ER table with many child relationships, or a service node with several outbound connections - could collapse onto one anchor and read as a single overloaded line. Bundled edges that intentionally share a trunk segment are preserved.