Docklyx splits the company (billing, users, audit) from the DC (docks, yard, hours, service levels). A user can work Bajio in the morning and Tultitlan in the afternoon without logging out. Carriers only see the DCs they're allowed in. Billing stays as one.
Switch DCs, check per-site KPIs, and manage per-user permissions — all without reloading.
The company holds what it buys from Docklyx (plan, integrations, audit, user list). The DC holds how that yard runs (docks, hours, policies). Every operation — booking, check-in, alert — is born tied to a specific DC.
Your active DC is stored on your profile. Refresh and you stay there. Switch and the whole panel re-filters without re-auth.
Bookings, docks, yard, check-ins, alerts and incidents are tied to the DC where they happen. A Bajio manager will not — cannot — see Tultitlan's ops.
If you're admin or manager at the company level, you don't need a grant per DC: you can activate any site and see the rolled-up view.
Hours, booking slot length, buffer between bookings, on-time window, detention rate, dwell calculation model. What varies by ops lives on the DC.
Each carrier is assigned to the DCs where they can operate. To book at a yard, they need explicit access to that yard — a company account is not enough.
One dashboard gives you one site's KPIs; another rolls them up across the company. Every booking is stamped with its company and its DC, so cross-site reporting is free.
Deactivating a DC reassigns affected users to another site, clears their active session, marks the yard inactive. Historical ops stay audited.
One company = one subscription. The plan caps how many DCs can be open (Trial 1, Starter 1, Pro 3, Enterprise unlimited). No crossed invoices, no per-yard account.
Golden rule: what varies by how a yard runs lives on the DC. What represents the company as a Docklyx customer lives on the company.
No one needs emails or spreadsheets to coordinate sites. Everything ties to the DC where it happens.
Onboards Bajio with timezone, hours and slot. Inherits base config from the company.
Mario and Lourdes get email. Each comes with Bajio permissions. Lourdes also Sonora and Tultitlan.
Drags docks, zones and gates until it matches the real yard. Saved per site.
His active DC is Bajio. Sees only Bajio bookings, alerts and tasks.
One click to swap the active DC. Panel reloads: different bookings, yard, alerts.
Via portal; the system validates the carrier has access to that DC. Booking is born tied to Tultitlan and the company.
Analytics roll up per-DC. Sees who's doing well, who needs help, without context-switching.
One subscription per company. Plan caps how many DCs can be open. Billing doesn't know about yards.
One admin who used to run one site now runs three without opening more tabs.
Stop emailing rollups between sites. Consolidated KPIs are native.
The system prevents a manager from seeing bookings or incidents at the wrong DC — filtered in the backend, not trusting the front end.
Spin up a new DC with base config. Layout and docks no longer rebuilt by hand.
If it's not here, sales replies same-day — not a form into the void.
Monthly or annual billing (save 17%).
21 days free · No credit card required · 1-day setup
We stand up an environment with your real DCs, users and policies. In 21 days you see consolidated operations without crossed emails.