Diagram types
Every diagram type
The full catalogue: cloud and AWS architecture, flowcharts, sequence diagrams, ERDs, UML class, C4, state machines, gantt, kanban, mindmaps and charts.
Drawn on the free-form canvas
These are the diagrams where you decide the arrangement, because the arrangement is part of what the diagram says.
Cloud and AWS architecture
Regions, VPCs, subnets and managed services, with real provider logos on the shapes.
Microservice landscapes
Gateways, services, event buses and per-service datastores.
Kubernetes topologies
Ingress, namespaced workloads, persistent storage and observability.
Network diagrams
Availability zones with public, private and isolated subnets.
Flowcharts and process diagrams
Decisions, branches and terminals — the classic boxes and diamonds.
Swimlane diagrams
The same process, split by who is responsible for each step.
Org charts and sitemaps
Hierarchies where you want control over how the tree is laid out.
Laid out automatically
These place themselves. You supply the content and the layout stays tidy no matter how much you add.
Sequence diagram
Messages between services, clients and people, in order. You fill in participants and messages.
Entity relationship diagram
Database tables, their columns and how they relate. You fill in entities and relationships.
Class diagram
Types, their members and the relationships between them. You fill in classes and relationships.
State machine
States and the events that move between them. You fill in states and transitions.
Delivery plan
Phases, tasks, durations and milestones on a timeline. You fill in phases and tasks.
C4 container diagram
People, systems and the containers inside your system. You fill in elements and relationships.
User journey
Steps a user goes through, scored for how well they go. You fill in phases and steps.
Timeline
What happened when — good for architecture history. You fill in periods.
Kanban board
Work in progress, by column. You fill in columns and cards.
Mindmap
Break a system or problem into branches. You fill in branches.
Pie chart
Proportional breakdown of a total. You fill in slices.
Priority quadrant
Plot options against two axes — effort versus impact and friends. You fill in items.
Git branching
Branches, commits, tags and merges — how a team actually ships. You fill in branches and commits.
Requirements
What the system must do, and what proves that it does. You fill in requirements, elements and between requirements.
Packet layout
How a header or wire format is laid out, bit by bit. You fill in fields.
Sankey flow
Where a quantity goes — traffic, spend, funnel drop-off. You fill in stages and flows.
XY chart
Bars and lines over a shared axis — traffic, latency, revenue. You fill in x axis and series.
Radar comparison
Score two or three options against the same set of criteria. You fill in criteria and options.
Treemap
Nested proportions — cloud spend, codebase size, revenue mix. You fill in boxes.
Fishbone
Cause and effect for an incident or a defect, grouped by theme. You fill in causes.
Frequently asked
- Is this a draw.io alternative?
- For architecture diagrams, flowcharts and the auto-layout families listed here, yes — with no sign-up, and with diagrams that stay in your browser rather than on a server.
- Can I draw AWS architecture diagrams?
- Yes. The free-form canvas ships AWS, Azure, Google Cloud and Kubernetes logos, plus group shapes for regions, VPCs and subnets. The AWS three-tier template is a working example to start from.
Did this page answer your question?
If something here is unclear, wrong, or missing, tell us — it is the fastest way to get it fixed. Feature requests are welcome too.
No account needed. We ask for your email so we can actually reply — it is used for nothing else.