Skip to content

C4 deployment diagram

Map a system's containers onto the infrastructure they run on.

Diagram · origin tag c4/deployment · The C4 Model

Availability

Availability per host
HostStateHow to get it
StandalonePrototypeNot yet released
DesktopPrototypeNot yet released
IntelliJ PlatformNot plannedNot planned
Visual Studio CodeNot plannedNot planned
EclipseNot plannedNot planned
ThinkRailNot plannedNot planned
NotionNot plannedNot planned
ClaudeNot plannedNot planned

What it is for

Deployment (supplementary)

Why a specialized view helps

C4 views are zoom levels of one model; a dedicated tool keeps each level consistent with the next instead of redrawing boxes by hand.

File formats

Not described yet.

Screenshots

Courier Tracking's production deployment: dashed deployment nodes nested around the load balancer and the container instances they host, fitted and then **zoomed in once** so the nesting reads, so the top and bottom of the drawing are cut off; Toolbox showing Deployment Node, Infrastructure Node, Container Instance and Software System Instance. The industrial plant's deployment is denser and fits to a picture too small to read, hence the other corpus. Nothing selected.

Standalone, at 5ac81b3

What is visible: Courier Tracking's production deployment: dashed deployment nodes nested around the load balancer and the container instances they host, fitted and then **zoomed in once** so the nesting reads, so the top and bottom of the drawing are cut off; Toolbox showing Deployment Node, Infrastructure Node, Container Instance and Software System Instance. The industrial plant's deployment is denser and fits to a picture too small to read, hence the other corpus. Nothing selected.

Why it matters: The production deployment nests each deployment node around what it hosts, from the load balancer down to the container instances, so the infrastructure is read straight from the Structurizr workspace the other C4 views come from.

Licence: Apache-2.0

Background

Focus areas

Sources