The network-layer coordinate for visibility as infrastructure.
Where observability becomes a network primitive — a foundational position for any platform that delivers visibility as a shared, connective layer rather than a point tool.
Matched pair · recommended together
Recommended: sold as a pair — the matched .app + .network TLDs cover one coordinate. Each name can be acquired on its own; the set inquiry is the path to the whole position. Click a name to view its lander.
The set
Part of the Supply Chain resolution surface.
7 of 7 primitives held for supply chain — a complete resolution surface. One operator holds the row agentic systems resolve to; every competitor who arrives later works with what is left.
Held as a matched pair — the Supply Chain row holds 19 matched pairs across the seven primitives.
See the full Supply Chain opportunity →Coordinated sets this position belongs to — the coverage it extends. Counts are the live cluster size in the graph.
Primary home
Also appears in
Surfaces this position also reads to — addressability, not exclusivity. A name applicable to a category is not a claim to own it; these are the buyer pools the coordinate speaks to, beyond the clusters it is held in.
Architectural context
Observability · Cross-Vertical · 3 compound moats. Cross-cutting: Observability.
Layer position: Substrate (L1)
Why this is canonical
'Visibility.network' frames observability not as a product feature but as infrastructure: something the network itself provides. This is the architectural framing that matters to platform builders, not end-users — the coordinate that names the layer beneath the apps.
Where it fits
A few directions this coordinate opens —
Illustrative, not exhaustive — held as a transferable canonical position, open to the buyer's own use.