The yard is the operating unit.
Public marketplace inventory and unlisted private yards run on one platform. Visibility controls discovery; DHQ’s operating model controls who handles arrivals, access, exceptions, hardware, and service.
External provider actions remain simulated until activation.
Built around what happens next.
Every reservation, arrival, access decision, payment event, and exception becomes one scoped operational record—ready for people and AI to act on safely.
Onboard deliberately
Every owner applies. DHQ reviews the property, scopes gate work, installs required hardware, commissions the site, and activates it manually.
See the live yard
Assigned spaces, incoming drivers, dwell, tasks, incidents, gate health, and service levels share one operations view.
Keep private yards private
A private yard is returned only to explicitly granted fleets, drivers, or managed access groups—never because someone guessed a URL.
Put the first location on DHQ.
We’ll map the operating workflow, define the visibility and authorization model, then commission the software and hardware in controlled stages.