ZQX — Zero Queue Exchange

Container status your yard, your hauliers, and your customers can all trust.

One deterministic answer — Ready, Not Ready, Blocked, or Conditionally Ready — backed by evidence, not a phone call. Every status is explainable and every human override is accountable.

Go to app.zqx.io

Why status is usually a phone call

Container status information travels by phone and email, with no shared, structured record either side can point back to. Trucks arrive against bookings that turn out to be blocked. Compliance holds get resolved verbally, with no attributable evidence trail when a dispute or an audit comes later.

One deterministic status, always explainable

Every container carries a status of Ready, Not Ready, Blocked, or Conditionally Ready, computed from its recorded evidence and open holds — never guessed, never AI-decided. A human can always override it, and every override is recorded: who, when, and why.

Check before you queue

A haulier linked to a booking can check whether a scheduled pickup or drop-off is actually ready before leaving the yard, instead of finding out after joining the queue.

Everyone sees only what concerns them

Shippers, receivers, hauliers, and compliance reviewers each get access scoped to the specific containers they have a stake in — filtered to what their role actually needs to see, not your whole operation.

The ZQX platform

One account, one container-centric system. Status below reflects what actually exists today, not a roadmap dressed up as a feature list.

In development

app.zqx.io

The core application: bookings, jobs, container status, evidence, and holds. Sign in with your ZQX account.

Live

status.zqx.io

Public uptime status for every ZQX service, updated independently of the rest of the platform.

Planned

control.zqx.io

The tenant admin surface: users, integration credentials, and account-level configuration.

Planned

api.zqx.io

A documented, external-facing API for integrating your own systems with ZQX.

Planned

portal.zqx.io

Reserved in ZQX's URL model. Not yet built or scoped in detail.

Planned

connect.zqx.io

Reserved in ZQX's URL model. Not yet built or scoped in detail.