Skip to content
M2TOOLKIT

Architecture diagrams

Architecture diagrams that stay readable

Services, gateways, databases, caches and queues — connected with clean routed lines and grouped into networks or regions.

  • Free, no sign-up
  • Saved on your device
  • No watermark
Example — the “Three-tier web app” template
Private network (VPC)replicatesUsersCDNObject storageLoad balancerApp server 1App server 2CachePrimary DBRead replicaJob queue

The basics

What is an architecture diagram?

A software architecture diagram shows the building blocks of an application and how they talk to each other: clients, gateways, services, data stores, queues and third-party providers.

Good diagrams make design reviews faster, onboard new engineers quickly and help everyone spot single points of failure.

What you can add

  • Users
  • Internet
  • Web app
  • Mobile app
  • Load balancer
  • Server
  • Container
  • Function

Features

What makes it work

  • Service and data icons

    Load balancers, servers, functions, services, databases, caches, queues, auth and more.

  • Three ready-made patterns

    Three-tier web app, microservices with an event bus, and a serverless mobile backend.

  • Networks and regions

    Wrap private parts in a frame — it carries everything inside when you move it.

  • Real templatesStart from a worked example and make it yours.
  • Smart connectorsDrag a + handle to connect; Tab adds the next step.
  • PNG, SVG & file exportFor docs and slides — or a .json to keep editing.
  • Share linksSend a link; whoever opens it gets their own copy.
  • Private by defaultSaved in your browser. Nothing is uploaded.
  • Works on touchPan, pinch and edit on a tablet or phone.

Templates

Start from a worked example

Open one, change the words and it's yours — every element stays editable.

How it works

Three steps to done

Create an architecture diagram
  1. Step 1

    Pick the three-tier, microservices or serverless template.

  2. Step 2

    Rename services, add or remove parts, and draw the data flows.

  3. Step 3

    Export for your design doc or share a link for review.

Use cases

Who it's for

  • Design reviews

    Agree the shape of a system before building it.

  • Onboarding

    Give new engineers the map of how things fit together.

  • Cloud migrations

    Draw today's setup next to the target architecture.

Architecture Diagram

Common questions

Does it include AWS, Azure or GCP icons?

It uses generic icons (server, function, database, storage, queue, load balancer…) that work for any cloud. Label them with the service name you use.

Can I show data flow direction?

Yes — every connector has arrowheads you can change, plus optional labels and dashed lines.

Can my team review it?

Share a link or a .json file — each reviewer opens their own copy. There's no live co-editing.

Is it free?

Yes, free with no sign-up.

More solutions

Open M2 Boards

Ready when you are

Free in your browser — no account, no download, no watermark.