Getting Started with Architecture Maps
Learn what architecture maps are, how to create one, and how to add nodes representing your data layers and system components.
Architecture maps give you a visual overview of your entire data landscape. They show how data flows from external sources through your model, into projections, and out to APIs and user interfaces. Rather than describing architecture in text, you lay it out on a grid-based canvas where each node represents a real artefact in your project.
Why Use Architecture Maps
End-to-End Visibility
See the complete data flow from source systems to consumer interfaces in one place
Living Documentation
Nodes link to real projections and integrations, so the map stays in sync with your design
Stakeholder Communication
Share a clear, visual summary of your data architecture with technical and non-technical audiences
Creating an Architecture Map
The Grid Canvas
Architecture maps use a grid-based layout. Nodes snap to grid cells, making it straightforward to align elements and maintain a tidy diagram. You can resize nodes to span multiple cells when you need to represent larger subsystems or groupings.
Node Types at a Glance
| Node Type | Represents | Source |
|---|---|---|
| External | Systems outside your project boundary | Added manually |
| Model | Your canonical data model | Imported from project |
| Projection | A transformation of model data for a specific concern | Imported from project |
| Integration | APIs, webhooks, or other outbound connections | Imported from project |