Use official cloud symbols
Represent deployed services and Kubernetes resources with recognizable artwork that remains editable, connectable, and exportable.
- AWS Architecture Icons
- Kubernetes resource symbols
- Regions, zones, networks, and boundaries
Cloud infrastructure solution
Make cloud architecture reviewable.From intent to deployment.
Use recognizable AWS and Kubernetes symbols, import infrastructure definitions, and connect every service, boundary, and tradeoff to the specification that explains why it exists.
- 307 AWS icons
- 31 Kubernetes symbols
- Terraform import
- Architecture checks
Service architecture · cloud runtimeSource-rendered starter
Rendered from the checked-in service architecture starter used by the application.
EdgeLoad balancerTLS · health routing
KubernetesApplication clusterPrivate subnets
AsyncWork queueDecoupled jobs
DataMulti-zone storeEncrypted at rest
@
Cloud SLO linkedAvailability and recovery
Architecture grounded in reality
Explain what runs, where it runs, and why.
Keep provider detail, system intent, operational constraints, and review evidence together instead of spreading them across screenshots and wikis.
Start from infrastructure
Import Terraform and Kubernetes YAML to accelerate the first view, then organize the result around the architecture story people need.
- Resource-to-icon mapping
- Editable imported topology
- Ownership and environment metadata
Attach cloud decisions
Link resilience targets, security decisions, cost assumptions, and runbook context to the exact service or route they govern.
- Precise specification references
- Bidirectional backlinks
- Expiring review links
Cloud work in Struct
Represent deployed resources without flattening provider detail.
Use provider-native libraries, infrastructure imports, explicit boundaries, and linked operating requirements in a single editable architecture record.
- 01307 AWS iconsOfficial architecture artwork stays editable, connectable, searchable, and exportable.
- 0231 Kubernetes symbolsWorkloads, networking, configuration, storage, policy, and cluster resources.
- 03Infrastructure importMap Terraform and Kubernetes YAML resources into an editable first architecture view.
- 04Operational contextRecord region, zone, environment, ownership, failure domain, and linked SLO or runbook requirements.
Cloud design workflow
Import, clarify, govern, and communicate.
Turn provider resources into a shared architecture model that platform, security, software, and operations teams can evaluate together.
Map the deployed foundation
Import infrastructure or begin with focused cloud starters and provider-native icons.
Show boundaries and critical flows
Make regions, zones, subnets, ingress, data paths, and failure domains explicit.
Link requirements and tradeoffs
Reference reliability, security, compliance, and cost specifications from the affected components.
Review across disciplines
Give application, networking, security, and operations teams one versioned system view.