Vexolis. Drayage Logistics Platform

Multi-tenant by the database, not by the app

Vexolis serves many carriers, brokers, and fleets from one platform, and every one of them treats their lanes, rates, and equipment as competitive information. The classic way to keep them apart is to sprinkle tenant checks through the application code, and the classic failure is the one query somebody forgot to filter.

So Vexolis pushes tenancy down into Postgres itself with row-level security. Every table carries a tenant boundary, and the database enforces it on every read and write, no matter which service or endpoint issued the query. A forgotten filter in application code returns nothing instead of returning someone else's freight. That single decision turned tenant isolation from a code-review hope into a property of the system, and it is why the four Vexolis products can safely share one platform.

Telemetry that streams from the server

The fleet console shows many vehicles moving at once, and the naive approach, polling an API from the browser on a timer, falls apart quickly: either the map lags behind reality or the server drowns in identical requests.

Vexolis streams instead. The server holds the connection open and pushes updates down as positions change, so the console reflects the fleet without the browser ever asking twice. Position updates are geo-quantized before they ship: a truck parked at a warehouse does not need to emit a fresh coordinate every second, while one moving on the highway does. Quantizing by movement keeps the stream light enough to run all day in a dispatcher's browser tab, and a sidebar detail rail lets that dispatcher drill into any single unit's history and alerts without leaving the live view.

The same telemetry feeds the mobile app, so a dispatcher at a desk and a carrier on the road are watching one stream of positions, not two systems that agree most of the time.

Built for the cab, the yard, and the dead zone

Drayage work happens in exactly the places mobile coverage is worst: container yards ringed by steel, port terminals, warehouse docks. A driver app that assumes a clean connection is an app that fails at the moment of proof of delivery.

The Vexolis mobile app treats connectivity as a maybe. Drivers claim and manage loads, follow live equipment tracking, and photograph documents from the phone, and the app is offline-friendly where it matters most: work done in the yard syncs with the platform in real time once a connection is there to carry it. Push alerts close the loop in the other direction, so a status change made by dispatch reaches the cab without the driver ever pulling to refresh.

Money moves with the load

A cross-carrier marketplace only works if claiming a lane means something, and it only means something if the commercial side is wired in rather than bolted on. Vexolis runs its plans and billing on Stripe, so a carrier's standing on the platform and the subscription behind it live in one system instead of a spreadsheet reconciled at month end.

Lane claims themselves are audit-trailed. When two carriers want the same freight, the platform can show exactly who claimed what and when, which turns disputes from arguments into lookups. That record-keeping instinct runs through the whole product: in freight, the paperwork is the product as much as the software is.

Four products that feel like one

The Drayage TMS, the Live Tracking console, the Broker Portal, and Driver Profiles each run on their own subdomain with their own audience: carriers, dispatchers, 3PLs and brokers, and drivers carrying their CDL records with them. Splitting them keeps each product simple enough to learn in an afternoon.

What makes them a suite is what they share underneath: one login across all four, one tenant boundary enforced in the database, and one stream of truth about where every load and unit actually is. A broker watching a container and the driver hauling it are looking at the same row, scoped to what each is allowed to see.