Boxes and arrows without a key: the problem addressed
A freely drawn architecture diagram, made of boxes and arrows, can leave its reader without answers. What does each box represent? What does each line mean? At what level of detail are we? The C4 model answers with a small number of conventions. Its official website, c4model.com, written by its creator Simon Brown, starts from these shortcomings: unexplained notation, unlabelled relationships, mixed levels of abstraction.
It compares the resulting diagrams to maps of the code, to be explored by changing the zoom level.
Definition of the C4 model
The C4 model is presented by this website as an approach to visualising software architecture, easy to learn and designed for developers. It brings together hierarchical abstractions, diagrams following the same hierarchy and supplementary diagrams. Its name comes from the four structural diagrams, whose English titles begin with the letter C.
According to the website’s FAQ, the roots of the model go back to around 2006 to 2009, without an exact date, and the name “C4” appeared at the beginning of 2011. The pages cited in this entry were consulted on 12 November 2026.
The four levels and the supplementary diagrams
The original terms are kept; the glosses are suggestions made by this entry.
| Level (original term) | Suggested reading | What the diagram shows, according to the website |
|---|---|---|
| System context | Context of the system | The system under study, its users and the systems it is connected to |
| Container | Container | The applications and data stores of the system, their technologies and their exchanges |
| Component | Component | The components of a container, each grouping functions behind an interface |
| Code | Code | The implementation of a component: classes, interfaces, functions |
The website does not require all four levels to be drawn: it recommends the first two to all development teams and treats the code diagram as optional.
Three diagrams complete the set: system landscape (the landscape of an organisation’s systems), dynamic (collaboration of elements at runtime) and deployment (deployment into a given environment).
C4 model, Docker container, UML, enterprise architecture: not to be confused
The container of the model is not a Docker container, and the website insists on this. The word refers to an application or a data store: something that must run for the system to work.
Nor is the C4 model a notation: the website describes it as independent of any notation, confines itself to recommendations (a title, a key, a type and a description for each element, labelled relationships) and accepts that diagrams may be drawn in UML.
It does not cover the field of enterprise architecture, of IT urbanisation or of a framework such as TOGAF. Its subject, according to the website, is the static structure of a software system: business processes, data models or state machines are described with other diagrams. The landscape diagram is presented there as a bridge to enterprise architecture.
A use case: appointment booking for health centres
Imagine a network of health centres whose appointment booking application must be described to a new team. The system context diagram places the system at the centre, surrounded by patients, reception staff, the messaging service and the patient record software. The container diagram opens the box: a mobile application, a web application, an application programming interface and a database, with the technology of each and the protocol of their exchanges. A component diagram is drawn only for the application programming interface, which carries the booking rules.
The website acknowledges limits to the model: designed for custom-built software, it is less suited to embedded systems and to solutions that rely on heavy configuration rather than on specific development.
These diagrams have their place in a project’s architecture file, alongside the maps that describe the entire information system: our IT architecture page presents both.