Draw wide.
Explain deep.

01 / Altitude

One diagram, several conversations

Use the top level as the 10,000-foot system map. Put clouds, clusters, streams, and other boundaries inside it. Nest workloads and topics inside those containers. Open any container to focus the board on that level, then use the breadcrumb to climb back out.

02 / Source format

Flowboard Markdown

The first heading names the diagram. List items create infrastructure. Indentation creates containment. Attributes in braces give each item a stable ID, type, position, size, and optional color.

# Checkout platform

- AWS production {#aws type=aws}
  - Payments EKS {#eks type=eks}
    - Checkout API {#api type=pod}
    - Outbox worker {#outbox type=pod}
- Event backbone {#msk type=msk}
  - orders.v1 {#orders type=topic}

> Busy during product drops. {#note x=40 y=420}

Supported shape types

aws · gcp · eks · gke · k8s · pod · service · container · lambda · client · database · msk · kafka · confluent · topic · gateway · loadbalancer · dns · githubactions · argocd · helm · zot · istio · certmanager · bind · haproxy · virtualservice

03 / Motion

Connect the IDs

Add a ## Flows section. Each line connects two stable IDs. Color identifies a signal, state controls pressure, and label names what moves.

## Flows
- api -> orders {#events color=#f05a47 state=busy label="order events"}
- outbox -> orders {#retry color=#2878ff state=normal label="retries"}

Available pressure states are idle, normal, and busy.

04 / Ownership

Local until you publish

Editing the starter diagram writes only to your browser's local storage. It cannot change another visitor's demo. Export Markdown, JSON, or GIF at any time. Publishing requires an approved account and creates an owned server copy; only its owner can update or delete it.

05 / Agents

The canvas and the agent share a language

Give an LLM the same Markdown you use in the editor, or connect it directly through MCP. Personal API keys are available to approved users on the MCP page and are shown once.