Every container.

Every charge.

Every carrier.

Customers, carriers and loads import from CSV or XLSX with column mapping, so you map them rather than re-type them. Nothing commits until you have seen a validation preview, and an import applies completely or not at all.

On one server you control, running Postgres, object storage and the application in containers — self-hosting is the design constraint, not a deployment option. Every table carries an organisation id and Postgres row-level security enforces it inside the database, not only in a query somebody wrote in a hurry.

Because a general TMS has no field for the parts of a drayage move that cost money. The last free day is a date with a clock against it, and the advance you fronted the steamship line is a ledger entry the container cannot release without.

Your company profile, letterhead and people take an afternoon, and that is what makes the first document the system generates carry your docket rather than ours. Your own records set the real timeline: a customer list with three spellings of one consignee does not import in a single pass.

You can still build the load — the carrier is created in pending compliance and the compliance team is notified. What you cannot do is paper it, because dispatch documents refuse to generate until authority, insurance and W9 are on file and a reviewer has approved in writing.

Eleven roles ship as defaults over a grid of twenty-four modules by six actions, and that grid is yours to edit. A sales agent sees their own book only, enforced in the query layer on the server rather than by hiding a menu item.