Model systems on the canvas

The canvas is intentionally more structured than a generic whiteboard. Components and connectors carry machine-readable meaning so reviews and analysis can reason about the system.

Place architecture components

Drag or add clients, gateways, services, databases, Redis, queues, object stores, external APIs, observability, security controls, linked designs, cloud frames, and sticky notes.

Describe what matters

Select a component to edit its name, purpose, owner, criticality, capacity expectations, and technology-specific settings. Redis can capture cluster mode, replication, persistence, eviction, consistency, failover, backup, memory, and hot-key risk.

Connect the system

Connections represent synchronous requests, asynchronous events, batch transfers, cache reads and writes, model calls, and observability signals. Add protocol, timeout, consistency, and notes in the connector inspector.

Organize without losing meaning

• Cloud frames group deployment or trust boundaries.
• Sticky notes capture risks, decisions, and questions.
• Linked designs reference another accessible design.
• Catalog assets reuse governed enterprise services and infrastructure.