Glossary
Learn the terms we use across Canopy and these docs. Each one maps to a real concept in the product, so you can read the rest of the documentation - and the app - without guessing what a word means.
Filter by term or definition, and click any linked term to jump to its full page.
34 terms
| Term | Definition |
|---|---|
| Account | A single person and their login. One account can own and belong to many workspaces. |
| Admin | A workspace role with full edit access and the ability to invite members, but no control over billing, payouts, or listing maps for sale. |
| Architecture as code | Treating a map as a versionable text artifact. A map round-trips losslessly to canopy.json, so you can review it in a PR, diff it, or generate it from a script. |
| Brand icon | The service logo shown on a node, set with the node's brand slug (e.g. "postgresql"). An unknown slug falls back to a neutral box, so a map never breaks. |
| Canopy AI | Prompt-to-map generation: describe a stack in plain English and Canopy drafts the architecture. A Pro feature with a daily rate limit. |
| Canopy Card | A gamified profile card that reflects your activity - badges, tier, and title - and can be shared publicly. |
| canopy.json | The portable JSON representation of a map - its nodes and edges. Paste it to import a map, or export a map as code. |
| Clone | An editable copy of a map or licensed template, created in your active workspace. Every clone is stamped with provenance and a unique watermark. |
| Drift | Divergence between your live stack and what the map says. Surfacing drift keeps a map honest as the real system changes. |
| Edge | A connection between two nodes, written with source and target. Edges carry an optional line style to show the kind of link. |
…
The shape of it
If you remember nothing else, remember the hierarchy - everything else hangs off it:
An account owns one or more workspaces. A workspace holds maps, and each map is made of nodes and edges. The workspace is the team and billing boundary: roles, seats, and the plan all live there.
Next
- Accounts & workspaces - how the layers fit together.
- Map syntax - the node and edge schema in full.
- Marketplace - templates, licenses, and selling.