The canonical namespace for driver-as-a-service freight models.
A .com coordinate for platforms that deliver professional driving capacity on demand — abstracting driver recruitment, dispatch, and compliance into a managed service layer.
Matched pair · sold together
Held and transacted as one position. A matched .ai + .com pair forecloses its own most common confusable — one coordinate, not two names.
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
Service · Cross-Vertical · 2 compound moats. Architectural surface: Service.
Layer position: Cross-cutting
Why this is canonical
'Driver as a service' names the freight and logistics industry's shift from asset ownership to on-demand capacity procurement. The .com TLD gives this string broad commercial reach across carriers, shippers, and freight-tech platforms building the next generation of flexible driver networks.
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.