DevoraCamp Draw: free system design and diagram canvas
DevoraCamp Draw is a whiteboard for sketching software architecture in your browser. It is built on Excalidraw, so diagrams have a clean hand-drawn look, and it adds a library of system components you can drop onto the canvas instead of drawing every box yourself.
Use it to plan a system before you build it, to practise for a system design interview, or to illustrate an idea for a teammate. The canvas is infinite, so a diagram can grow as the design does.
How to use it
- Pick a shape, or insert a ready-made system component such as a database, cache, or queue.
- Connect components with arrows to show how requests and data flow.
- Add text labels to name each part and note the important details.
- Group, duplicate, and rearrange elements until the layout reads clearly.
- Export the result as an image, as JSON, or as Mermaid code.
Handy keyboard shortcuts
- R, O, D: rectangle, ellipse, diamond
- A and L: arrow and line
- T: text, and P: free-hand pencil
- V or Esc: back to the selection tool
- Ctrl+D: duplicate, and Ctrl+G: group the selection
- Ctrl+Z and Ctrl+Y: undo and redo
What it is good for
- Architecture diagrams showing clients, services, databases, caches, and queues
- System design interview practice, where you explain a design while you draw it
- Flowcharts and request-flow sketches for documentation
- Quick brainstorming before writing a design document
Frequently asked questions
Is DevoraCamp Draw free?
Yes. The canvas is free to use and does not require an account.
Can I export my diagram?
Yes. You can export a diagram as a PNG or SVG image, save it as JSON to reopen later, or copy it as Mermaid code to paste into documentation.
Does it work on a phone?
The canvas is designed for a laptop or desktop screen with a mouse or trackpad. On a small phone screen there is not enough room to draw comfortably.
What is a system design diagram?
It is a drawing of the parts of a software system, such as clients, load balancers, services, caches, queues, and databases, and the connections between them. It is the usual way to explain an architecture in a design review or an interview.