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

> CoPage draws AWS, Azure and Google Cloud architecture diagrams with each provider's official icon set built in and working offline, imports and exports draw.io files, and exports SVG and PNG that open for editing again. Your coding agent can draw them for you with the free CoPage CLI.

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

| Collection | Source | Use it for |
| --- | --- | --- |
| `aws` | AWS Architecture Icons (2026-07-31 release) | Services, resources and groups such as VPC, subnet and region |
| `azure` | Azure Public Service Icons V24 | Azure services |
| `gcp` | Google Cloud icons, current and legacy style | Google Cloud products and categories |
| `general` | Lucide line icons | People, devices, databases, arrows and the rest |

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:

```bash
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. (CoPage 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](/docs/diagrams): elements, icons, connectors and exports.
- [CoPage CLI documentation](/docs/cli): install and every command.
- [Connecting your agent](/docs/agents) and [Checks](/docs/checks).
- [Install the free CLI](/#cli) · [CoPage for enterprise](/enterprise)

## Questions

### Which cloud icon sets does CoPage include?

AWS Architecture Icons, Azure Public Service Icons (V24) and Google Cloud's icons, plus Lucide line icons for
everything else: more than 3,000 icons, built into the program and usable offline.

### Can I import my existing draw.io diagrams?

Yes. `copage diagram import file.drawio` brings each page in as a diagram, with AWS, Azure and Google Cloud shapes
turned into CoPage icons where one matches. draw.io's own PNG and SVG exports import as well.

### Can I go back to draw.io?

Yes. `copage diagram export <id> file.drawio` writes a draw.io file with the icons embedded, so it opens in draw.io
without CoPage installed.

### Do I need a cloud account or an internet connection?

No. The CLI reads no cloud account and draws only what you or your agent describe. Icons, fonts and checks are built
in, so drawing and exporting work offline.

### Can I add my own icons?

Yes. `copage import ~/Downloads/k8s-icons --kind icon --collection Kubernetes` adds a folder of icon files to the
library as a collection of its own.