Mockflow documentation
Mockflow helps you explain how a system behaves. You draw the system, describe a situation, run it, and review the result as a clear story. These guides explain each step without assuming specialist knowledge.
How Mockflow works
Everything in Mockflow follows one simple loop. Build a diagram from components and connections. Add a scenario that says what should happen. Run it. Mockflow records the result one step at a time, so you can replay it, explain it, and share a safe version with other people.
Runs are illustrative. They demonstrate the behavior and ordering you configured — not real-world capacity, latency, or cost.
What these guides cover
The guides cover the whole visible product: workspaces and templates, diagram editing, every component type, connections, component behavior, scenarios, runs, the timeline and transcript, contracts and data descriptions, presentation, sharing, and Agent Access Keys for MCP clients.
These are product guides, not an internal engineering manual. They explain what you can do and what the result means. They do not publish Mockflow's source design, storage design, private interfaces, or internal document formats.
Get to a first run
Start small. A client, a gateway, and one service are enough to make the loop concrete. Build the smallest path that tells the story you want to review, then add detail as the question becomes clearer.
- Open Templates and choose a ready-to-run example, or create a blank diagram in your workspace.
- Add and connect the components that participate in the path. The creating diagrams guide covers the editor basics.
- Create a scenario that says where the story starts and what information it should use.
- Run the scenario and read the timeline or transcript. Use Checkpoint when you want a named review point.