Skip to content

25 editable reference diagrams

Software Architecture Diagrams

Choose a software architecture by the boundaries your team needs to maintain: presentation, business rules, data ownership and integration. Compare layered, clean, hexagonal and modular designs before committing to a deployment model.

Start with the simplest structure that keeps those responsibilities clear. A microservice introduces network and operational boundaries; a module inside one application may provide enough separation. Use these diagrams to discuss dependencies and change ownership.

Choose a diagram for your design question

Open a reference to inspect its component flow and trade-offs, then adapt it in the browser-local editor. Manual editing does not require login; AI generation and account storage do.