· Product · 5 min read

Keeping a visual service graph and a YAML file in sync

By Ethan Cole, Co-Founder & CTO

Visual infrastructure tools usually rot because they fight Git. A canvas only holds up in production when the diagram and service.yaml compile from the same schema.

Engineers are rightly skeptical of drag-and-drop infrastructure builders. Too often, clicking around in a web UI creates hidden state that drifts away from the repository and cannot be reviewed in a pull request.

At the same time, staring at three hundred lines of nested YAML is a terrible way to understand whether the background worker depends on Redis or which port the public gateway expects.

We designed the Visual Service Designer and service.yaml around one shared schema. Adding an edge on the canvas updates the same declarative service spec that lives in Git.

Teams use the canvas when onboarding teammates or sketching a new service boundary, and review exact text diffs in pull requests before anything reaches staging or production.

Visual clarity and version-controlled configuration do not need to be competing workflows when they share a single source of truth.

All notes