> ## Documentation Index
> Fetch the complete documentation index at: https://support.myapps.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Boards

> Node workspaces for multi-step media pipelines

**Boards** is a node workspace. You place nodes on a canvas, connect them into branches, and route shots, references, and multi-step media pipelines — the flow map is the source of truth.

## Boards vs Canvas

Both are visual workspaces. They solve different problems.

|             | Boards                           | [Canvas](/create/canvas)   |
| ----------- | -------------------------------- | -------------------------- |
| Model       | Nodes and connections            | Layered document           |
| Thinking in | Flow and branches                | Composition and stacking   |
| Best for    | Multi-step pipelines, variations | Compositing a single image |
| Node graphs | Yes — that's the point           | **No**                     |

If you're chaining steps, use Boards. If you're building one image out of layers, use Canvas.

## Working in it

<Steps>
  <Step title="Create a board project">
    From the library, start a new board or open an existing one. Each board is its own saved node workspace.
  </Step>

  <Step title="Build node flows">
    Place nodes, connect them into branches, and route shots, references, and multi-step pipelines.
  </Step>

  <Step title="Generate and assemble">
    Use the board hub and director tools to run generations, preview outputs, and keep the flow map authoritative.
  </Step>
</Steps>

## What's on a board

| Piece              | What it's for                                                |
| ------------------ | ------------------------------------------------------------ |
| **Nodes**          | Steps in the pipeline — a generation, a reference, an output |
| **Connections**    | How output flows into the next step                          |
| **Branches**       | Explore variations side by side without losing the original  |
| **Asset hub**      | Bring existing assets into the board                         |
| **Director panel** | Direct the shot rather than hand-tuning raw parameters       |
| **Assembly strip** | Line up outputs toward a finished sequence                   |

## Why branch

Branching is the reason to use a board. Instead of overwriting a prompt and losing what you had, you fork — three treatments of the same shot side by side, all visible at once, all traceable back to the same source.

<Tip>
  Branch at the point of uncertainty. If you're unsure about a style, fork there and generate both — you'll see the answer instead of arguing with yourself about it.
</Tip>

## Sharing

Boards can be shared by link, so someone can see the flow and its outputs without a Pixio account. See [Share links](/library/share-links).

## Credits

Nodes that generate cost credits at their model's normal rate. Placing and connecting nodes is free — you only pay when a generation runs, so map the whole flow before running any of it.

<Info>
  Board and spatial-canvas project CRUD is available through the API. See [what you can automate](/integrations/what-you-can-automate).
</Info>