Architecture Diagrams
Important
Architecture Diagrams is part of experimental builds. This capability is actively evolving. APIs, UI, and workflows may change between releases. To enable this feature, contact your sales representative.
Nodinite Architecture Diagrams turns architecture from static slides into a live, navigable operating asset. Teams get C4-aligned views that stay connected to the Repository and can pivot straight into runtime investigation from grouped Log Views.
This capability applies the C4 model in a Repository-first way so architecture communication and operational truth stay aligned.
- ✅ Tell one consistent architecture story across all zoom levels using Diagram Sets that group Landscape, Context, Container, Component, Dynamic, and Deployment views.
- ✅ Navigate architecture instead of hunting for files with automatic drill-through between related diagrams in the same set.
- ✅ Keep diagrams trustworthy over time through live Repository bindings and lifecycle control with Draft, Active, and Archived states.
- ✅ Start from what you already have by importing Mermaid, PlantUML, Structurizr DSL, or Draw.io XML.
- ✅ Generate full sets from live topology with Generate from Integration Landscape when your source of truth is Repository entity data.
- ✅ Investigate runtime behavior immediately with grouped Log View runtime diagrams in Participants mode or Systems mode.
Example of a C4 Context diagram showing a high-level view of an Order-to-Cash system and its interactions with users and other systems.
Tip
You can Import this specific diagram source to test it out in your Environment. Just copy the Mermaid source from the Example section and paste it into the Import flow to see how it looks in Nodinite.
Why Teams Choose Architecture Diagrams
Many tools can draw boxes. Few can keep those boxes aligned with reality after week one.
| Common architecture challenge | What Nodinite Architecture Diagrams changes |
|---|---|
| Context, Container, and Component views drift apart | Diagram Set structure keeps related views together and connected |
| Teams waste time finding the right "next" diagram | Drill-through navigation links related diagrams automatically |
| Diagram updates become manual, slow, and error-prone | Repository bindings keep labels and entity identity aligned |
| Imported diagrams become dead snapshots | Imported diagrams become live, maintainable architecture artifacts |
| Runtime understanding requires separate tooling and separate thinking | Grouped Log View runtime diagrams give immediate event-context architecture views |
For first-time readers, the key idea is simple: Architecture Diagrams combines documentation quality and operational relevance in one flow.
How It Works
Mermaid / PlantUML / Structurizr DSL / Draw.io XML"] IL[" Integration Landscape
Repository IDs"] LogView[" Grouped Log View
Runtime Investigation"] end subgraph "Architecture Diagrams" ImportPath[" Import"] GeneratePath[" Generate from IL"] Runtime[" Runtime Diagram
Participants or Systems mode"] Set[" Diagram Set"] Drill[" Drill-through"] Lifecycle[" Draft -> Active -> Archived"] end subgraph "Repository" Systems[" Systems"] Services[" Services"] Domains[" Domains"] Integrations[" Integrations"] end Markup --> ImportPath IL --> GeneratePath LogView --> Runtime ImportPath --> Set GeneratePath --> Set Set --> Drill Set --> Lifecycle Systems --> Set Services --> Set Domains --> Set Integrations --> Set style ImportPath fill:#87CEEB style GeneratePath fill:#87CEEB style Runtime fill:#87CEEB style Set fill:#FFD700 style Drill fill:#90EE90 style Lifecycle fill:#90EE90
Architecture Diagrams supports three practical entry points: import existing diagrams, generate from Integration Landscape, or open runtime diagrams from grouped Log Views. All paths connect to the same Repository-first architecture model.
What You Get in a Diagram Set
A Diagram Set is the organizing unit for one architectural subject, such as Order-to-Cash or Supplier Onboarding.
| Diagram type | C4 level | Main question answered |
|---|---|---|
| System Landscape | L0 | How does the broader enterprise system landscape connect? |
| Context | L1 | Who uses this system and what external/internal systems interact with it? |
| Container | L2 | How is this system structured into containers and boundaries? |
| Component | L3 | What integrations/components exist inside a selected container scope? |
| Dynamic | - | How does a specific workflow interact at runtime? |
| Deployment | - | Where does the architecture run in infrastructure terms? |
Tip
Need the deeper mechanics for sets, drill-through rules, lifecycle behavior, and routes? See Diagram Set Fundamentals.
Choose the Right Creation Path
| Path | Use when | Go to |
|---|---|---|
| Import | You already have diagram source in Mermaid, PlantUML, Structurizr DSL, or Draw.io XML | Import |
| Generate from Integration Landscape | You want lossless diagram generation from live Repository IDs and IL topology | Generate from Integration Landscape |
This split is intentional. Import is text-first and flexible. Generate from Integration Landscape is data-first and complete.
Real-World Outcomes
| Outcome | How teams achieve it |
|---|---|
| Faster architecture onboarding for new stakeholders | Start with L0/L1, then drill-through to L2 and L3 by entity |
| Better change impact conversations | Use Diagram Assistance with Add from Set, Coverage, and Review Impacts |
| Faster runtime diagnosis | Open grouped Log View runtime diagrams to inspect related event context instantly |
| More reliable architecture governance | Use Draft, Active, Archived lifecycle and Set-based role permissions |
Runtime Investigation Without Authoring Delay
For incident or analysis workflows, teams can open runtime diagrams directly from grouped Log Views and switch between Participants mode and Systems mode. This keeps investigation speed high while curated diagrams in sets remain focused on communication and governance.
This is a killer capability for operations: users can generate a C4-inspired runtime diagram on the fly without drafting any diagram in advance. The runtime view reuses grouped event context and Repository bindings, including Transport Contract binding where available, to show where the event happened and how the flow moved between participants or systems.
Example of an on-the-fly C4-inspired runtime diagram generated from a grouped Log View, without any pre-authored diagram.
Read the complete flow on Inspect Grouped Log Views as Runtime Diagrams.
Feature Map
Use this page as the hub, then move to the spoke you need:
| If you want to... | Open this page |
|---|---|
| Understand C4 concepts and how they map to Nodinite | What is C4 Diagrams? |
| Understand the C4 Diagram Set concept first | What is a C4 Diagram Set? |
| Understand role-based access and required rights for C4 actions | Role-Based Access for C4 Diagram Sets |
| Run the set lifecycle operations (add, edit, import, sync, hard delete) | Add or manage C4 Diagram Set |
| Learn Diagram Set mechanics and drill-through behavior | Diagram Set Fundamentals |
| Create your first diagram step-by-step | Creating Your First C4 Diagram |
| Build and edit diagrams interactively | C4 Designer - Interactive Canvas |
| Import existing markup or Draw.io XML | Import |
| Generate full diagram sets from IL | Generate from Integration Landscape |
| Review suggestions and impact hints | Diagram Assistance |
| Validate runtime health on architecture nodes | Monitoring - Operational Health on Nodes |
| Export, share, and consume Mermaid source | Export and Sharing and Mermaid View - Read-Only Rendering |
| Understand model mapping and troubleshooting | C4 Model vs Nodinite Concept Mapping and Repository Properties for C4 Diagramming |
Availability and Access
Architecture Diagrams is available in experimental builds and requires the Mapify feature pack.
- Requires the Mapify feature pack
- C4 Diagrams are included when Mapify is licensed
- Component Type icon support for C4 is included with Mapify
- Domains are available for architecture boundaries with Mapify, even without BPM
- All Repository users with Repository access can view and navigate Architecture Diagrams
- Access is controlled by Diagram Set roles using standard role-based security
- Create rights are required to import diagrams, generate diagrams from Integration Landscape, and create diagrams from BizTalk
- New 7.x From Nodinite 7.6.0, new Diagram Sets honour the DefaultRolesInViews system parameter so configured roles are assigned automatically at set creation
See License Options and Feature Matrix for a complete license comparison.
Next Steps
- What is C4 Diagrams?
- What is a C4 Diagram Set?
- Role-Based Access for C4 Diagram Sets
- Add or manage C4 Diagram Set
- Diagram Set Fundamentals
- Creating Your First C4 Diagram
- Import
- Generate from Integration Landscape
- C4 Designer - Interactive Canvas
- Diagram Assistance
- Monitoring - Operational Health on Nodes
- Mermaid View - Read-Only Rendering
- Export and Sharing
- Inspect Grouped Log Views as Runtime Diagrams
- C4 Model vs Nodinite Concept Mapping
- Repository Properties for C4 Diagramming