Skip to content
Arch Viz

Infrastructure Diagram Builder

Build system architecture and network diagrams using only the GUI. Add nodes, give each a name and a shape (rectangle, rounded, stadium, cylinder or diamond), then connect them with solid, dotted, thick or arrowless lines and optional labels such as a protocol or port. Choose one of four layout directions. The result is output as Mermaid code and a PNG image, and the code renders as a diagram when pasted into a GitHub README, issue or pull request. Layout is automatic, but in the rich SVG view you can drag nodes to rearrange them. Nodes that share a group name are enclosed in a box, such as a VPC. Everything runs in your browser and nothing you enter is sent anywhere.

Nodes

Connections

graph TB Users["Users"] LB["Load Balancer"] App1["App Server 1"] App2["App Server 2"] DB[("Database")] Users --> LB LB --> App1 LB --> App2 App1 --> DB App2 --> DB

Your diagram and the positions of the nodes you moved are saved automatically in this browser (nothing is sent to a server), so you can pick up where you left off next time.

Templates

Load a starting point. It replaces the current diagram.

Export to other tools

Turn the diagram above into Graphviz DOT, PlantUML, D2 or Mermaid architecture-beta (an icon-based architecture diagram) text. BT and RL directions are drawn as TB and LR in PlantUML. architecture-beta has only five built-in icons (user, gateway and network become internet; storage becomes disk), and no edge labels, dotted or thick lines.

Review the diagram

Checks the shape of the diagram above for common design smells: isolated parts, a database facing the internet, a single database for many services, long chains, loops. It cannot see real settings or things you did not draw, so treat each point as a question to ask.

Guide

How to use & features

  • Click "Add Node" to create elements and set their labels and shapes (Rectangle, Round, Cylinder, etc.).
  • Use "Add Connection" to define relationships between elements by selecting from/to nodes from the dropdowns.
  • Switch the diagram flow (Top to Bottom, Left to Right, etc.) in the "Layout Direction" section.
  • Download the generated diagram as a PNG image using the "Download PNG" button.
  • Copy the Mermaid syntax to your clipboard with "Copy Mermaid" for use in README files or documentation tools.
Samples

Examples

Standard Web 3-Tier

Input
Nodes: Internet, Load Balancer, App Server, DB
Connections: Internet -> LB -> App -> DB
Output
graph TB
    n1["Internet"]
    n2(["Load Balancer"])
    n3["App Server"]
    n4[("Database")]
    n1 --> n2
    n2 --> n3
    n3 --> n4
FAQ

FAQ

  • Can I save my diagram?

    Use "Download PNG" to save an image. You can also copy the Mermaid code and paste it into a GitHub README, issue or pull request, where it renders as a diagram. Keep the code and you can paste it again later to rebuild the diagram.
  • Can I use cloud icons such as AWS or GCP?

    No. Nodes use five shapes: rectangle, rounded, stadium, cylinder and diamond. Use them by convention, for example a cylinder for a database and a diamond for a decision, so the kinds of nodes are easy to tell apart.
  • Can I drag nodes to position them?

    No. Layout is automatic through Mermaid. To tidy a diagram, change the layout direction (top to bottom, left to right and so on) or reorder how you add nodes and connections. If you want free placement, use "SQL to ER Diagram" or "Architecture Diagram Editor", where you can drag things around.
  • Which line styles can I choose for connections?

    Four: solid, dotted and thick with an arrow, and solid without an arrow. A common convention is solid for synchronous calls, dotted for asynchronous or optional paths, and thick for the main path. Connections can also carry an optional label such as a protocol or port.
  • How is this different from the GitHub Actions visualizer?

    This tool is for building a general diagram by hand, such as servers, databases and networks. To draw job dependencies automatically from a GitHub Actions YAML, use the "GitHub Actions Visualizer".
  • Is my input sent anywhere?

    No. Building and rendering the diagram happen entirely in your browser, so you can enter internal system layouts you do not want to share. Note that reloading the page clears your work.
Use cases

Common use cases

  • Quick architecture diagrams

    From side projects to business systems, add nodes and connections and you have an architecture diagram. Share the big picture in five minutes before a proposal or design review.
  • Diagrams for READMEs and internal wikis

    The output is Mermaid syntax. Paste it into a GitHub README, issue or pull request and it renders as a diagram. Because it is code, it can be diffed and there is no separate image file to manage.
  • Explaining networks and data flow

    Draw the path from load balancer to app to database, or the relation between subnets and gateways, to align the team. Add labels to connections to note protocols or ports.
  • Incident response and onboarding material

    A diagram of which database an API uses, or how it connects to external services, speeds up troubleshooting and explaining the system to new teammates.
  • Comparing design options

    Change layout direction and line styles to draw several candidate architectures. Make before-and-after diagrams and compare them in a review.
Notes

Notes & limitations

  • Edits are not saved

    Reloading the page clears what you entered. To keep it, copy the Mermaid code or save the PNG.
  • Layout is automatic; you cannot place nodes precisely

    It uses Mermaid's automatic layout, so nodes cannot be placed where you like. If lines cross and the diagram is hard to read, change the layout direction or the order of nodes.
  • There is no grouping box

    Enclosing several nodes in one box, such as a VPC or subnet, is not supported. Compensate by writing the membership in the node label, for example "Subnet A / app".
  • Very large diagrams get slow

    With a great many nodes and connections, rendering takes longer and the diagram becomes hard to read. Split a large system into several diagrams by role.
About

About this tool

Infrastructure Diagram Builder

Automatically render visual infrastructure architecture diagrams from code using Mermaid.js.
This tool makes it easy to map out server configurations, network topologies, and cloud resources (AWS, GCP, Azure) locally, treating your diagram essentially as Infrastructure as Code.

Key Features and Use Cases

  • Rapid Sharing: Instantly generate architecture diagrams in real-time as you type your configuration.
  • Perfect for Documentation: Download generated diagrams as images (PNG) or copy the Mermaid code directly into Markdown-compatible environments like GitHub, Notion, or Zenn.
  • Secure Browser-Side Processing: Because cloud architectural metadata can be highly sensitive, all rendering and parsing happens locally in your web browser. Nothing is ever sent to our servers.

Articles for this tool

Recent Articles