Diagravo documentation

Build an architecture diagram, watch requests flow through it, and see where it would break — then share it. These docs cover the whole tool.

Quick · about 5 minBuild your first diagramDrop three components on the canvas, connect them, press Play and fix the first overload you see.Concept · about 10 minHow the system behavesWhat Play actually does with your diagram: where a request starts, where it goes, and why.

What Diagravo is#

Diagravo is a browser-based tool for designing and explaining software and systems architecture. You drag components (a client, a backend, a database, a cache, a load balancer, and about thirty more) onto a canvas, connect them, and set their sizes and limits. Then you press Play and watch requests travel through the diagram, with a console that narrates every hop and flags the components your numbers would overload.

It is a tool for sketching, testing an idea and communicating a design — not for deploying one. Nothing you build here provisions anything real. It is also not a load tester: playback is a what-if illustration driven by the numbers you type in, and the docs are explicit about exactly what it does and does not model.

You do not need an account to start. Diagrams are saved on your device; an account adds cloud sync, share links and collaboration.

Browse the docs#

Build

Components and connectionsEvery component type, what its settings mean, and how to connect, group, copy and replicate them.

How the system behaves

Terminal & scripting

The terminalBuild and change a whole diagram by typing commands — the language, the shortcuts and every command.

Saving, sharing and exportWhere your diagrams are stored, Ctrl+S, My Diagrams and cloud sync, publish links, collaboration, and every export format.

Reference

Need something else?#

Search the docs with Ctrl + K, or write to contact@diagravo.com. If a page is wrong or unclear, tell us — that is how the docs get better.

Last updated October 9, 2026. Something unclear or out of date? Tell us.