Glossary
C4 model
The C4 model is an approach to diagramming software architecture, created by Simon Brown. It describes a software system through four nested levels of diagrams, from the most general to the most detailed: system context, containers, components and code.
Updated
What is the C4 model?
The C4 model is a way of drawing the architecture of a software system at successive zoom levels. Its official website describes it as an easy to learn, developer friendly approach to software architecture diagramming. It was created by Simon Brown.
The name comes from the four core diagrams: context, containers, components and code.
The model starts from an observation about the boxes-and-lines diagrams that pile up over projects: they mix levels of abstraction, leave their notation unexplained and carry unlabeled arrows. The model asks for little: a small set of abstractions (person, software system, container, component), one diagram per level, and a key. It is notation independent and tooling independent.
What are the four levels of the C4 model?
Take a work-order application used by field maintenance technicians.
Level 1 is the system context diagram. It shows the system in scope as a single box, surrounded by its users and the other systems it exchanges with: technicians, planners, the ERP that supplies work orders, the corporate directory, the SMS gateway.
Level 2 is the container diagram. It opens the box and shows the applications and data stores inside: a mobile app, an API, a relational database, a file store for photos. The word causes confusion. In C4, a container is an application or a data store, something that has to be running for the system to work. The site is explicit that it does not mean a Docker container, although the two sometimes line up.
Level 3 is the component diagram. It zooms into one container, the API for instance, and shows its components: authentication, scheduling, synchronization with the ERP.
Level 4 is the code diagram. It shows how a component is implemented, for example as a UML class diagram. The site does not recommend it for long-lived documentation, since most development environments can generate that detail on demand.
You do not need all four. According to the official site, the system context and container diagrams are sufficient for most software development teams.
Which diagrams complement the four levels, and what does C4 leave out?
Three supporting diagrams sit alongside the four levels. The system landscape diagram shows the software systems of an organization and how they relate; the site calls it a bridge into the enterprise architecture world. The dynamic diagram shows how elements collaborate at runtime for a given use case. The deployment diagram shows what the systems and containers run on.
That last one is the one infrastructure teams care about. It uses deployment nodes, which can be a physical server, a virtual machine, cloud infrastructure or an execution environment such as a database server, and infrastructure nodes such as a DNS service, a load balancer or a firewall. For our application, it would show the API running on two virtual machines behind a load balancer and the database hosted on a managed service.
C4 remains a software architecture model. Its focus, the site says, is the static structures that make up a software system at different levels of abstraction. Business processes, workflows, state machines, domain models and data models are out of scope, and the site suggests supplementing C4 with other notations.
On the network side, the deployment diagram can place a firewall or a load balancer on the picture. The model does not set out to describe an addressing plan, VLANs or firewall rules: its abstractions are the person, the software system, the container and the component. That detail belongs in a low-level design and a flow matrix.
How does C4 compare with ArchiMate and UML?
The three are aimed at different readers.
UML (Unified Modeling Language) is a specification of the Object Management Group, at version 2.5.1 since December 2017. The OMG describes it as a graphical language for visualizing, specifying, constructing, and documenting the artifacts of distributed object systems. C4 was inspired by it: the site presents C4 as a simplified version of the same underlying concepts, and level 4 is often drawn in UML. If a team already uses UML and that works, the C4 site itself advises sticking with it.
ArchiMate is an open and independent modeling language for enterprise architecture, published by The Open Group, whose version 4 is dated April 27, 2026. It ties business, applications and technology together in one model. C4 describes one software system from the inside. ArchiMate describes a set of applications in their context without going into each one.
When the question is C4 or ArchiMate, the practical answer is often both. The enterprise architect keeps the map of applications, business capabilities and technology platforms in ArchiMate. The team that builds one of those applications describes it in C4. Application names then need to match on both sides.
Which tools can you use to draw C4 diagrams?
Before naming any tool, the official site asks a question: diagramming or modeling?
Diagramming means drawing boxes and lines in a general-purpose drawing tool, or on a whiteboard during a design session. The barrier to entry is low and the result is immediate. The limit is well known: the tool does not know what the boxes stand for. Renaming an application means renaming it on every diagram where it appears, and you cannot ask the diagram what depends on a component.
Modeling means describing the elements and their relationships once, then creating views on top. Diagrams at different levels stay consistent because they come from the same model. A common variant is a model written as text, stored in the code repository next to the software and reviewed with it. Structurizr, created by the author of the C4 model, works this way: its site presents it as a "models as code" tool, where you define the elements in a text-based language and then declare the views.
To choose, the site offers plain questions: who writes the diagrams, who reads them, is the data format open, is the tool self-hosted or a cloud service.
How do you keep C4 diagrams current?
A C4 diagram goes stale like any architecture diagram, each level at its own pace. The context moves slowly. Containers change with every architecture change. Components follow the code, and a hand-drawn level 3 rarely stays accurate for long.
A few habits hold up over time. Draw only the levels you are prepared to maintain, usually the first two. Keep the model close to the code, so that changing the diagram is part of the same change as the software. Review the context and container diagrams before any project that relies on them, the way you would review an architecture document.
The deployment diagram is the most fragile, because it depends on infrastructure and the development team does not see infrastructure changes. A virtual machine moved, a second node added, a managed service replaced: none of that goes through the code repository unless the infrastructure itself is described there. For this diagram, the useful check is to compare it with what the hypervisor, the cloud inventory and the CMDB say.
What Uncia brings, and what it does not do
Uncia reads the sources of your IT estate in read-only mode (connectors to clouds, hypervisors, CMDB, firewalls and scanners; dropped-in files such as an RVTools export, a flow matrix or an architecture document) and reconciles them in a knowledge base. It also reads the diagrams you already have (draw.io, Visio, ArchiMate, C4, SVG, PDF), without a language model, and compares them with the sources. Gaps are shown with the source of every value, for example a host that changed or an application missing from the exports (see documents and diagrams checked against the sources).
Uncia does not produce C4 diagrams. The maps it generates are Architecture, Infrastructure and Network maps, which export to ArchiMate, draw.io, PNG and SVG. It does not read your code and knows nothing of the internal structure of an application: the component and code levels stay with the development team. It changes neither your diagrams nor your systems, and the comparison is updated at each collection.
Sources
- c4model.com, official website of the C4 model by Simon Brown: overview, core and supporting diagrams, license, accessed
- c4model.com, FAQ: background of the model, C4 and UML, ArchiMate and SysML, what the model does not cover, accessed
- c4model.com, "Diagrams": the levels most teams need, accessed
- c4model.com, "Code diagram": not recommended for long-lived documentation, accessed
- c4model.com, "Container": definition of a container in the C4 model, accessed
- c4model.com, "Deployment diagram": deployment nodes and infrastructure nodes, accessed
- c4model.com, "Tooling": diagramming or modeling, questions for choosing a tool, accessed
- Structurizr, official website, accessed
- Object Management Group, Unified Modeling Language (UML), version 2.5.1, December 2017, accessed
- The Open Group Library, ArchiMate 4 Specification (C260), April 27, 2026, accessed
Frequently asked questions
What does C4 stand for?
The name comes from the model's four core diagrams: context, containers, components and code. According to the official site, the fourth was originally called "classes" and was renamed "code" during 2015-2016.
Who created the C4 model?
Simon Brown. The official site traces the roots of the model to somewhere between 2006 and 2009, the naming of the diagram types to early 2010 and the first use of the name "C4" to early 2011.
Do you need all four levels?
No. The official site states that the system context and container diagrams are sufficient for most software development teams, and it does not recommend the code diagram for long-lived documentation.
Is a C4 container a Docker container?
No. In the C4 model, a container is an application or a data store: a web application, a mobile app, a database, a file store. The term refers to something that has to be running for the system to work, however it is deployed.
Does C4 replace UML or ArchiMate?
That is not its purpose. The official site advises teams that already use UML, ArchiMate or SysML successfully to stick with them, and others to try C4. It also suggests supplementing C4 diagrams with other notations for what the model does not cover.
Can the content of c4model.com be reused?
The website and its example diagrams are published under a Creative Commons Attribution 4.0 International License; the terms of reuse are those of that license. The model itself imposes neither a notation nor a tool.