/projects/$id/topology, linked from a project’s own detail page) draws a project’s apps, databases, and shared volumes as a diagram, with lines representing every relationship between them. It is read-only and requires no configuration: every fact on the page already exists in the project’s desired state, just arranged as a graph instead of a list.
Network topology groups everything on the mesh by node and draws only app-to-database connections. This page is scoped to one project, groups by resource kind, and draws every edge kind the project’s configuration carries: database bindings, service dependencies, shared volumes, and egress allow-rules.
What you see
An interactive canvas. Drag the background to pan, scroll to pan or hold Ctrl or Cmd while scrolling to zoom, and drag any box to rearrange it. Columns start as Domains, Apps, Databases and Volumes. Each app and database box shows the same status dot used everywhere else in the dashboard (healthy, deploying, failed, no status), refreshed every few seconds, so a deploy in flight is visible without leaving the page. Click a box to open a side panel with its connections and quick links (overview, logs, deploys and rollback, domains, metrics). Positions are remembered per project in this browser; Reset layout returns to the default arrangement. Large projects stay responsive because boxes and lines outside the visible area are not drawn until you pan to them. Keyboard: Tab to the canvas, arrow keys pan, plus and minus zoom. Tab to a box, then arrow keys nudge it (hold Shift for bigger steps), Enter opens its panel, Escape closes it.What each edge means
Every edge is derived from one specific field on the project’s apps and databases. None are inferred or illustrative: an edge only appears when the underlying configuration actually declares the relationship.
Network shares (
/api/v1/network-shares) are left off this diagram: nothing in a project’s stored configuration links a share to an app, so an edge would be a guess.
CLI and API
app, database, volume, domain, load_balancer, node; edge kinds database_binding, depends_on, volume_attachment, egress_allow, routing, load_balances, placed_on); add --json for the raw response, the same JSON the canvas draws. The API is GET /api/v1/projects/{id}/topology (read ability). Whole-mesh data comes from levelrail-cli nodes topology, covered on Network topology.
Multi-service apps
A multi-service app (created from acompose: build or POST /apps/{name}/compose) shows one box per member service, not one collapsed box for the whole app: dependsOn and database bindings are declared per service, so collapsing them would hide exactly the relationships this page exists to show.
See also
- Network topology - the whole-mesh, node-grouped view with live mesh reachability
- Projects and organizations - what a project is and how apps/databases get filed under one
- Connecting apps to databases - how a database binding is created in the first place
- App spec reference -
dependsOn:,volumes:, andenv: { from: ... }syntax - API reference -
GET /api/v1/projects/{id}/topology’s full request/response shape