Docker Compose Topology Viewer
See service dependencies, networks and volumes from a Compose file as a graph, without running Docker.
Compose file
549 characters · 30 lines · up to 1,024 KiB
Topology
Analyzed in your browser. The file is not uploaded or stored. Environment values, commands and secrets are never read.
Related Tools
How to use
- 1.Paste Compose YAML, open a file or load an example.
- 2.Choose a view with the switch above the graph.
- 3.If some services have profiles, pick the profiles you would start so inactive services are shown as inactive.
- 4.Search for a service, click it to inspect it, and use Focus to follow what it depends on or what uses it.
- 5.Export the current view as SVG, PNG, graph JSON or Mermaid.
Docker Compose Topology Viewer
A Compose file declares services and how they relate, but reading that from YAML is slow once a project has more than a handful of services. This viewer turns the file into a graph. The Dependencies view shows depends_on and links, including conditions such as service_healthy. The Networks view shows which services join which networks, including the implicit default network. The Volumes view shows named volumes, bind mounts, anonymous volumes and tmpfs mounts as different kinds of node. The graph is a picture of what the file declares. It is not a live view of a running project.
What the lines mean
A depends_on line means one service waits for another at startup, and shows the condition when the file declares one. It does not mean the services talk to each other. Services on the same network can reach each other if they choose to, but a shared network is not a recorded connection, so the Networks view links each service to its networks and never draws a line between two services. A published port is a mapping on the host, not proof that a service is reachable from the internet. A volume or bind mount line shows storage that is attached, not data flowing.
Supported syntax and limits
The viewer reads the Compose Specification subset that describes relationships: services, depends_on in short and long form, links, networks, network_mode, volumes in short and long form, profiles, healthcheck presence, and the top-level networks and volumes. It does not evaluate variable interpolation, merge several files, resolve include or extends, or read env files. When a file uses one of these, the viewer says so instead of guessing. Input is limited to 1 MiB.
Privacy
Your YAML is analyzed in a background worker in your browser. This tool does not upload, store or log it. Environment variable values, commands, build arguments, labels and secret contents are never read, so they cannot appear in the graph, the inspector or an export; only the names of environment variables, secrets and configs are shown.
Frequently asked questions
- Is my Compose file uploaded?
- No. The YAML is analyzed in a background worker in your browser. It is not uploaded, stored or logged by this tool, and environment values, commands, build arguments and secret contents are never read.
- Does a depends_on line mean the services talk to each other?
- No. depends_on controls start order and, with a condition such as service_healthy, when a dependent service may start. The viewer draws it as a dependency, not as traffic.
- Why are there no lines between services on the same network?
- Sharing a network lets services reach each other if they choose to, but it is not a recorded connection. The Networks view links each service to its networks, so shared networks are visible without implying traffic.
- What happens to services in profiles?
- Services with a profile are shown as inactive until you select one of their profiles. If an active service depends on an inactive one, the viewer warns instead of hiding the problem.
- Does it merge several Compose files or evaluate variables?
- No. It analyzes one file. include, extends and variable interpolation are not resolved, and the viewer says so when a file uses them instead of guessing the final configuration.
