13 templates
Cloud architecture templates
Cloud and platform architecture across AWS, Azure, Google Cloud and Kubernetes — 331 resource types, real containment (account, region, network, zone, subnet, cluster, namespace) and typed edges. Checks the architecture as well as drawing it: a datastore reachable from the internet with no ingress on the path, a datastore in a public subnet, a tier claiming redundancy from inside one zone, an edge crossing a network boundary with no gateway.
AWS — Three-Tier Web Application, Multi-AZ
The reference architecture, drawn correctly and reported clean: a public load balancer, application servers in private subnets across two availability zones, and the database isolated with a standby in the other zone. Copy this one. Every check runs and finds nothing, which the engine states rather than implies.
ArchitectureTeaching Case — A Database in a Public Subnet
Deliberately wrong, and the drawing of it is indistinguishable from a correct one — which is the point. The database sits in a subnet the document itself declares public, and the traffic path from the internet reaches it without passing through anything that terminates or filters. The engine names both, with the path it walked, so a reader can check the accusation rather than take it.
ArchitectureTeaching Case — "Highly Available" in One Zone
Three application servers and a database, every one of them marked highly available, all of them inside a single availability zone. The count is the trap: `count 3` looks like redundancy and is not, because three instances in one zone is one zone. The engine says exactly that, in those words.
ArchitectureTeaching Case — What "I Could Not Check That" Looks Like
The most important template in this set, and nothing in it is wrong. It is an ordinary, sensible diagram that declares no availability zones — which is what almost every real cloud diagram looks like. The availability check therefore cannot run at all, and the engine says so plainly instead of reporting a pass. That state is the one most tools never show anyone.
ArchitectureAWS — Serverless API, Edge to Table
A serverless request path with no servers in it: CDN, API gateway, functions, a document store and an object store, with a queue for the asynchronous half. Reports clean — and shows the async edge style, which is drawn differently from request traffic because a queue between two services is a different claim from a call.
ArchitectureGoogle Cloud — GKE Microservices with Managed Data
A Kubernetes cluster on GKE with its namespaces drawn as real containers, an ingress terminating outside traffic, and the stateful half deliberately outside the cluster in managed services. Reports clean. The pattern worth copying is that last part: the databases are managed, not StatefulSets, and the diagram makes that visible.
ArchitectureAzure — Hub-and-Spoke Landing Zone
The enterprise pattern: a hub virtual network carrying the shared firewall, bastion and gateway, with workload spokes peered to it. Reports clean. Note the boundary edges — traffic that crosses from one virtual network to another names the gateway it crosses at, which is what stops the engine reporting an unexplained boundary crossing.
ArchitectureHybrid — On-Premises to Cloud Over a VPN
A migration-shaped diagram: a mainframe and a file server still on-premises, a VPN into the cloud, and a third-party payment provider outside both. Reports clean. It is the clearest demonstration of what the boundary check is for — every edge that leaves one network for another names the gateway it goes through.
ArchitectureAWS — Streaming Data Pipeline
Ingest to dashboard, with every edge carrying the kind of movement it really is: async where a stream sits between two services, data where bulk moves, request traffic only where something calls something. Reports clean. Drawing all three as one arrow is the commonest way an architecture diagram stops being useful.
Data & SchemaKubernetes — Workloads, Storage and Config
A cluster drawn in pure Kubernetes objects, with the distinction the notation exists to make visible: a Deployment is stateless and replicated, a StatefulSet has a volume claim behind it, and the two must not be drawn the same way. Reports clean.
ArchitectureTeaching Case — Boxes Nobody Connected, Words Nobody Knows
Two quieter failures, side by side. A resource that appears in no edge is a box somebody drew and never wired — legitimate for a legend, a real omission everywhere else — and a type word this engine's vocabulary does not carry is reported as a GAP in the vocabulary rather than as a mistake by the author. The difference between those two sentences is the difference between blaming the reader and blaming the tool.
ArchitectureProvider-Agnostic — One Architecture, No Vendor Names
The same shape written entirely in the generic vocabulary, which is what a design document wants before the cloud has been chosen and what a comparison across two clouds needs. Reports clean. Categories still colour the boxes, so the figure reads by function rather than by vendor — which is the question anyone looking at it is trying to answer.
ArchitectureTeaching Case — The Addresses Under a Correct-Looking Picture
Every box is in the right place. Two availability zones, a public load balancer, private application subnets, isolated data subnets — a diagram that would pass any review held over a screen. The arithmetic under it says something else: a subnet declared outside its own VPC, a /22 that silently swallows the /24 next to it, a management network numbered from documentation space no packet reaches, an address written where a block was meant, and a /29 asked to hold eight machines. Not one of those is visible in the drawing, and every one of them is decidable from the text. That is the entire case for checking the numbers rather than printing them.
Architecture