N
NJHTools

System Architecture Diagram Tool

Sketch how your system fits together, from clients and APIs to services, queues and databases, with labelled arrows for every data flow. Start from the architecture template and export SVG for your docs, free and with no signup.

Templates
ExportAutosaves in this browser

Private: everything stays in your browser.

How to make an architecture diagram on the whiteboard

  1. 1Start from the architecture template, which loads on this page with a client, API, service and database.
  2. 2Rename the boxes to match your own components and add any that are missing.
  3. 3Draw arrows for each request or data flow and label them with the protocol, such as HTTPS or gRPC.
  4. 4Draw boundary boxes around groups such as a VPC, a cluster or a third-party service.
  5. 5Add a title and a small legend, then export SVG for docs or PNG for chat.

Pick one level of detail per diagram

The C4 model is a widely used way to structure architecture diagrams at four zoom levels: System Context (your system, its users and the external systems it talks to), Containers (apps, services and databases), Components (the main parts inside one container) and Code.

Most teams only need the first two or three. Mixing levels, such as showing classes next to whole services, is the most common reason architecture diagrams become confusing.

Conventions that make diagrams readable

Label every box with its name and technology, for example 'Orders API (Node.js)', and label every arrow with what flows and how, for example 'POST /orders (HTTPS)'. Point arrows in the direction of the request or the data.

Use one shape per kind of element, such as rectangles for services and a distinct shape for databases, and draw dashed boundary boxes for trust zones, networks or ownership. Add a title, a date and a small legend so the diagram still makes sense months later.

Frequently Asked Questions

Does it include AWS, Azure or Google Cloud icons?↓

No official cloud icon sets are bundled. Use labelled shapes such as 'S3 bucket' or 'Cloud SQL', or drop in icon images you are licensed to use; they stay in your browser.

Can I keep the diagram in my repository?↓

Yes. Export SVG to embed in a README or wiki, and commit the .excalidraw file next to it. The file is plain JSON, so it diffs in code review and can be reopened here to update the diagram.

Can I export the board as an image?↓

Yes. Click PNG for chat, email and documents (it is exported at double resolution so text stays crisp), or SVG for a vector file that stays sharp at any size in slides and wikis. Untick Background for a transparent image.

How do I save a board and open it again later?↓

Your board autosaves in this browser, so it is still there when you come back. To keep a permanent copy or move it to another device, click .excalidraw to download the board as a file, then use Open file (or drag the file onto the canvas) to load it again. Clearing site data deletes the autosaved board, and very large images may not fit in browser storage, so keep a file for anything important.

Is my whiteboard private? Is anything uploaded?↓

Nothing is uploaded. The board runs entirely in your browser and is autosaved to your browser's local storage on this device. There is no signup, and images you drop on the board stay on your computer.

All CSS & Design Tools →

Last updated: