Skip to content

Architecture diagrams

Show the system, the relationships, and the story.

Boundaries, integrations, and dependencies without overwhelming the audience.

A shared core keeps boundaries clear Portal, core services, data, and partners

Portal

Staff workspace and customer requests

Core

Case service and rules

Data

Records store and search index

Integrations

Mail, identity, payments

Fictional exampleBoundaries stay readable left to right

What makes an architecture readable

Every box earns its place: a component, a relationship, or a decision.
Left-to-right flow with group boundaries.
Product-neutral shapes. This is not a vendor reference architecture.

Full example

A shared core keeps boundaries clear Portal, core services, data, and partners

Portal

Staff workspace and customer requests

Core

Case service and rules

Data

Records store and search index

Integrations

Mail, identity, payments

Fictional exampleBoundaries stay readable left to right

See all examples Open in DeckSpec (not available yet)

Output

Export SVG, PNG, PDF, and best-effort editable PowerPoint. PowerPoint is a compatibility format, not the source of truth.