Graphrun documentation

Model a system, run a journey, and explain the result. Start with an example or bring your own architecture.

Get to a first run

  1. Choose a template and select Use template to copy it into your workspace.
  2. Choose an included journey and use the numbered Run control in the editor command bar. A journey supplies the entry point, inputs, and starting state. Open Simulate to follow the result.
  3. Step through the timeline to see the route and its results. Return to Design, change a condition, run again, and compare the behavior.
Note
Runs demonstrate the model you configured. They are not measurements of production latency, capacity, or cost.

One model, multiple lenses

Design the architecture, map it to an existing repository, simulate its behavior, explore changes, and present the result. These are ways of working with the same model—not separate diagrams to keep in sync.

Diagram — what exists and how it behaves
Components and typed ports define the structure. Connections provide routes; handlers choose actions such as calling a service, emitting an event, or returning a response.
Journey — the situation to test
Inputs, fixtures, a seed, and safe limits describe a success, retry, timeout, or failure path.
Run — evidence you can replay
Ordered events show what happened. Inspect the timeline, open Present mode, or record a local video. A diagram checkpoint saves the graph and selected journeys, not the run recording. See Presenting & sharing for current distribution limits.

Find the right guide

Working on API contracts? Learn to define HTTP APIs, reuse JSON Schemas, and export OpenAPI specifications.