Loading the page. Nothing has gone wrong.
Integrations
Connected where it counts.
Twenty-three providers, five built first. Credentials never reach the browser, and nothing is switched on by default.
5 live-readySimulated until you say so
The directory
Seven categories.
An integration earns its place by removing a re-key somebody currently does by hand. Everything runs simulated first, labelled as simulated.
Carrier data
Who the carrier is, and whether it should be touching your freight.
- FMCSA QCMobilecore
- SAFER
- Highway
- RMIS
- MyCarrierPackets
- Carrier411
Load boards
Where the load goes when you need a truck on it today.
- DATcore
- Truckstopcore
- Loadmatch
Tracking
Where the box actually is — by truck and by vessel.
- Samsaracore
- Motive
- Geotab
- Project44core
- Ferry bookingcore
Mapping
Distance you can rate a lane on, not a straight line between two ZIPs.
- Google Maps
- Mapbox
- PC Miler
Documents
Signature on the paperwork that has to be signed.
- DocuSign
Comms
Telling a person something happened, where they already are.
- Twilio SMS
- Slack
Accounting
Getting the invoice into the books without re-keying it.
- QuickBooks
- Xero
- Stripe
Five connections do most of the work.
Each listed with what it actually returns.
Built first
What each one actually returns.
“Integrates with” means nothing on its own. These are the fields that land on the record.
01
FMCSA QCMobile
Verifies a carrier against the federal registry from its MC or DOT number.
Verified only on a positive authority match — never because a lookup returned something. The registered email then becomes the only address carrier paperwork can go to.
What comes back
- legal name
- mc docket
- usdot
- authority status
- safety rating
- registered email
02
DAT · Truckstop · Loadmatch
Posts a load to the boards you hold accounts with, and receives the offers back by webhook onto that load’s rate board.
Offers sort low to high and stop there — the system never selects on price. An unknown MC creates a carrier in pending compliance before anything can be dispatched.
What comes back
- carrier name
- mc
- dot
- rate
- eta
- source
- safety
03
ELD — Samsara · Motive · Geotab
Pulls truck position and hours of service for the tractor assigned to a load.
Pings attach to the load, not to a separate tracking screen. One record carries the customer’s question, the answer, and when you answered it.
What comes back
- latitude
- longitude
- timestamp
- speed
- hours of service
04
Ocean — Project44
Subscribes a container to vessel milestones from the steamship line and writes them onto the load.
The last free day arrives from the line rather than being typed off an arrival notice. That is the difference between a demurrage clock you trust and one you check by hand.
What comes back
- loaded
- sailed
- discharged
- last free day
05
Ferry booking
Submits a sailing request for lanes with a leg that goes by water, and records the confirmation.
The confirmation lands on the load as a document like any other, so the booking is where the rest of the paperwork is rather than in somebody’s inbox.
What comes back
- sailing reference
- route
- date
- units
- status
Behind every connection
The integration is the easy half.
Anyone can call an API once. What decides whether you trust it on a Friday afternoon is the retry, the timeout, and the disputed call six weeks later.
One shape, every provider
carrierName · mc · dot
rate · eta · source · safety
Whatever a board sends, this is what reaches the rate board.
- Credential vault
- Per-tenant credentials are encrypted in the database and read server-side at the moment of the call. Never in a page, an API response or a client bundle.
- Webhook receiver
- Offers, milestones and positions arrive on a signed endpoint, are validated against the provider they claim to come from, and land on the load without a page reload.
- Normalisation
- Every payload is mapped to one internal shape before it touches a record, so the rate board can sort two boards’ offers honestly.
- Idempotency
- Every outbound request carries a key, so a retry after a timeout cannot double-post a load or book the same sailing twice.
- Rate limiting
- Per-provider limits with exponential backoff. One provider having a bad afternoon slows its own queue and nothing else.
- Audit
- Every call is written to the audit log with the user, the load, the timestamp, the status and how long it took. When a provider says it never received something, that is the record you answer with.
Simulated or live
A simulated response says so, on the screen.
Run the whole system simulated while onboarding, then turn providers live one at a time. Each carries its own mode, credential reference and last-call timestamp.
- Simulated
- Labelled everywhere it appears. A demo response can never be mistaken for a real one.
- Live
- Credentials in the vault, calls audited, rate limits engaged.
The prototype Harbor TMS replaces returned simulated data from the same functions as real data — which is how a screenshot of an invented carrier ends up in front of a customer. Here the two cannot be confused, by construction.
How we know it works
- 01A load posted from the system appears on the target board within sixty seconds.
- 02A rate submitted on the board appears on the rate board without a page reload.
- 03An FMCSA lookup marks a carrier verified only on a positive authority match.
- 04No API credential is retrievable from the browser at any point.
- 05Every outbound call is written to the audit log with the user, the load and the timestamp.
These are the criteria the integration work is signed off against — not a summary written afterwards.