About
Harbor TMS was written by the people who were losing the demurrage — not by a software company that read about drayage and built a product around the word.
0
Customers we can name
When there are some willing to go on record, they will appear here with their names on them.
No logos, no testimonials, no invented statistics anywhere on this site.

Status
In build. The platform launches on an empty database — no legacy dataset behind it, no history being migrated.
First tenant
The brokerage the system was written inside. Multi-tenant from the first table, because a second brokerage was always the point.
Origin
A working brokerage moving ocean containers, running its book across a load board, a shared spreadsheet and an email thread per container. The failures were never exotic: a chassis charge nobody billed, four days of demurrage absorbed because the statement arrived three weeks late, an invoice that quietly turned ninety days old.
So the workflow got written down as a working prototype — never a production system, and no business ever ran on it. Its value was as a record of how the work is really done. Harbor TMS is that behaviour rebuilt on foundations that can be trusted with a company: a real database, tenancy on every table, permissions resolved on the server, an audit event behind every change, and the gates written once where they cannot be bypassed.

What we build to
Not values on a wall. Each one costs something, written down so it survives the week somebody wants it relaxed.
A gate in the browser is a suggestion. Carrier compliance, credit limits, the advance ledger and the finance gate are enforced where they cannot be clicked past, and every one names who did what.
The last free day clock, the advance ledger, the empty return and the demurrage rebill are not features you bolt onto a truckload TMS. They are the shape of the work.
An accessorial that exists is billed, or it is written off by a named person. There is no third state. Money is integer cents throughout, so totals do not drift.
The whole system runs on one server you control. No component depends on a hosted service that could not be replaced.
No customer logos, no testimonials, no statistics — because there is nothing yet that could honestly go there.
The company
Rather than invent bios: domain and product decide what the software refuses to do, engineering keeps the rules in one tested package, and compliance and finance own the paperwork a brokerage is legally on the hook for. On a demo call you meet them — there is no layer in between.
The brokerage holds its own operating authority, which is why the compliance model in this software is written from inside the problem rather than from a regulation summary.