The network-layer coordinate for shared freight observability.
A .network home for freight observability conceived as a shared infrastructure layer — the collective visibility fabric that spans carriers, shippers, and logistics platforms.
Matched set · recommended together
Recommended: sold as a set — the matched 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 Freight resolution surface.
7 of 7 primitives held for freight — 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 Freight row holds 37 matched pairs across the seven primitives.
See the full Freight 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
Freight · Vertical-Specific · 2 compound moats. Cross-cutting: Observability.
Layer position: Cross-cutting
Why this is canonical
Observability in freight is most powerful when it operates across the network: a shipment's state is shaped by actions taken by carriers, brokers, shippers, and infrastructure providers. The .network TLD frames this as shared, multi-party infrastructure — a collective observability layer rather than any single vendor's dashboard.
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.