Reusable draw.io / diagrams.net libraries for creating clean, consistent, and professional architecture diagrams.
This repository provides curated symbol libraries for system design, cloud architecture, DevOps, and security diagrams, optimized for clarity, reuse, and documentation quality.
Search and filter every shape library in the browser β no need to open draw.io just to see what's included.
Architectural diagrams often fail due to:
- inconsistent symbols
- visual clutter
- lack of shared semantics
This project solves that by offering standardized, reusable libraries that help teams produce diagrams that are:
- easier to read
- easier to maintain
- easier to review
Browse and search every library interactively in the live gallery, or read the full descriptions here:
π CATALOG.md
Each library is independently usable and versioned.
Libraries are intentionally minimal and semantic rather than exhaustive icon packs.
- Open draw.io / diagrams.net
- Go to File β Open Library from β Device
- Select the
.xmllibrary file - Drag symbols into your diagram
- Download a release ZIP from GitHub Releases
- Extract the libraries
- Import one or more
.xmlfiles into draw.io
Ready-to-open sample diagrams built from these libraries live in examples/:
| Example | File |
|---|---|
| CI/CD Pipeline | examples/ci-cd-pipeline.drawio |
| Integration Patterns | examples/integration-patterns.drawio |
| Kubernetes Microservices | examples/kubernetes-microservices.drawio |
| User Access Context | examples/user-access-context.drawio |
| AWS Serverless Web Application | examples/aws-serverless-web-app.drawio |
| Azure Three-Tier Web Application | examples/azure-three-tier-web-app.drawio |
| GCP Microservices on GKE | examples/gcp-microservices-gke.drawio |
| CI/CD GitOps Pipeline | examples/devops-cicd-gitops-pipeline.drawio |
Open any file directly in draw.io / diagrams.net (File β Open) to see a complete diagram, not just individual shapes.
For a deeper walkthrough of the Data Flow Diagram libraries specifically, see docs/dfd_doc.md.
These libraries follow a few strict rules:
- Architecture first β symbols represent concepts, not vendors
- Consistent sizing β predictable alignment and spacing
- Low visual noise β diagrams stay readable at scale
- Print & dark-mode friendly
- Tool-agnostic semantics (works beyond draw.io)
- System architecture diagrams
- C4 (Context / Container / Component) diagrams
- Cloud and infrastructure design reviews
- DevOps and CI/CD flows
- Technical documentation and RFCs
- Architecture review boards (ARB) material
This repository publishes versioned release packs.
Each release:
- is tagged (e.g.
v1.0.0) - includes a downloadable ZIP
- contains stable library definitions
π See GitHub Releases for downloadable packs, and CHANGELOG.md for what changed in each one.
Contributions are welcome β new libraries, refinements to existing symbols, visual consistency improvements, documentation and examples.
See CONTRIBUTING.md for guidelines on adding a new library, and the Code of Conduct for how we work together.
- Expand catalog previews
- Add more C4-aligned symbols
- Add example diagrams per library
- Provide light/dark theme variants
- Improve cross-library consistency
MIT License β free to use, modify, and distribute.
Good diagrams are a force multiplier for engineering teams.
This repository exists to make clear architecture diagrams the default, not the exception.






























