The network-layer position for shipper connectivity across the freight ecosystem.
The .network coordinate naming the relational infrastructure that connects shippers to the carriers, brokers, and platforms that move their freight.
Matched set · sold together
Held and transacted as one position — the matched set across TLDs closes together, not piecemeal.
The set
Part of the Freight resolution surface.
5 of 7 primitives held for freight. The unheld primitives complete the row.
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
Architectural context
Freight · Vertical-Specific · 2 compound moats. Architectural surface: Connectivity.
Layer position: Cross-cutting
Why this is canonical
The .network TLD is architecturally apt for a connectivity concept: it names the relational substrate, not just a single product or service. 'Shipper connectivity' on .network positions this as the network-level coordination surface — where shippers are nodes and the domain names the connecting fabric.
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.