Cloud architecture diagrams with the official AWS, Azure and Google Cloud icons

Cloud diagrams need the right icons, boundaries that mean something (a region, a VPC, a hub and its spokes) and a layout people can follow. CoPage has the icon sets built in, so neither you nor your agent has to download or upload anything.

#The icon sets

Together that is more than 3,000 icons, embedded in the program, so they work without a network. Each provider's own terms apply: they allow their icons in architecture diagrams and documentation. Search them from the terminal or the editor's icon library:

copage assets load balancer --collection aws
copage assets front door --collection azure
copage assets cloud run --collection gcp

Icons are placed with a label under them, and boundaries are boxes with a title in the corner, drawn behind what they contain.

#How it works

1. Install the free CLI and set up the project. copage init keeps diagrams in ./.copage, and copage skill install (or copage connect cursor, claude, vscode or codex for MCP) gives your coding agent the commands.
2. Start from an example or from your agent. copage open shows three example diagrams, one each on AWS, Azure and Google Cloud; opening one copies it into your diagrams. Or ask your agent: "Draw our landing zone on Azure, hub and spoke, with the on-premises network over ExpressRoute."
3. The agent draws, looks and fixes. It finds icons, adds boxes and connectors, renders a PNG to look at (copage diagram render <id>) and runs the checks (copage diagram check <id>): connectors attached at both ends, every icon labelled, nothing stacked, nothing left unconnected.
4. You adjust it in the editor. Drag, resize, restyle connectors, add icons from the library. The agent sees what you changed the next time it works on the diagram and keeps it.
5. Export. copage diagram export <id> docs/landing-zone.svg (or .png, .drawio, .json).

#draw.io in and out

• Import: copage diagram import platform.drawio. AWS, Azure and Google Cloud shapes become CoPage icons where a built-in icon matches their name, and the import lists any it couldn't match. Each page of the file becomes its own diagram. Compressed draw.io files, and the PNG and SVG files draw.io exports with the diagram inside, import too.
• Export: copage diagram export <id> platform.drawio writes an uncompressed draw.io file with the icons embedded, so it opens in draw.io without CoPage.
• The CoPage app imports .drawio files and exports diagrams as draw.io, SVG, PNG and JSON as well.

#What you get

• An SVG or PNG with the diagram stored inside it (comments and notes left out): open it in CoPage again with copage diagram open docs/landing-zone.svg.
• A .drawio file for colleagues who work in draw.io.
• A diagram source in .copage/diagrams/ to commit with your infrastructure code.
• The same diagram on a slide: a linked diagram, so fixing it once updates every slide that shows it. App · early access

#Who it's for

Cloud and solution architects, platform teams, and pre-sales engineers who draw target architectures for clients. The CLI is free and local: no account, and it sends nothing to us. Teams that also put these diagrams into client proposals use the CoPage app.

#Read more

• Diagrams: elements, icons, connectors and exports.
• CoPage CLI documentation: install and every command.
• Connecting your agent and Checks.
• Install the free CLI · CoPage for enterprise