Security and architecture

Local by design. Auditable by default.

Hosted by us or deployed in your building, the rules are the same: no public model provider sees your data, and every action an agent takes is on the record.

Nothing has to leave the building

For customers whose data cannot leave, the whole stack runs on a server in your rack. Freight rates, carrier data, documents, and driver messages never touch a public LLM provider, in either deployment.

One GPU server, on-prem

The on-prem deployment is a single machine: the web app, the warehouse, the schedulers, and the model. Inference happens in milliseconds because it happens next to the data.

Specialists, not generalists

Smaller models tuned on your own history outperform large general ones on your work, and they fit on hardware you own.

How it fits

Reads everything. Writes like a person.

Sources on the left, your server in the middle, the places work lands on the right. The only thing that crosses back out is a write a person would have made.

Sources

TMS databaseSQL read every 2 min

GPS / ELD pingspositions and geofence events

Microsoft 365mailbox watch, SharePoint

DAT RateView & iQrates, trends, benchmark

Your server

WarehousePostgres, three schemas

Local modelone GPU, zero egress

Outbound guardstaging cannot write out

Access controlSSO, per-page, groups

WRITE-BACK

Surfaces

Web appone login, per-desk access

TMS write-backcall-ins, stops, bookings

Email and SMSagent-drafted, human-approved

Nothing elseno telemetry, no vendor callbacks

Write rules

Guardrails, by rule.

These are enforced in code and hold across every agent. They are the reason a brokerage can let software touch its TMS.

Never overwrite a personIf a value already exists in the TMS, the agent leaves it alone. If someone clears it on purpose, it stays cleared.

Human in the loop where it mattersEmail updates, carrier offers, and final-stop deliveries land in a review queue. One click approves, corrections flow back too.

Every write logged and attributedIdentity comes from single sign-on and is trusted server-side. Each write records who, when, and the evidence that justified it.

Suspicious events flagged, not hiddenA departure minutes after an arrival, or a truck far from the stop, is marked for review rather than written.

Staging that cannot leakA nightly copy of production where every outbound path to the TMS, email, and SMS is blocked in code, not by convention.

Page-level access controlEach person sees only their desk. Groups and per-user grants, enforced in the API and the UI.

Compliance

A smaller scope to audit.

When customer data never leaves your network, the questions in a SOC 2 or customer security review get shorter. We hand you the architecture, the data-flow diagram, and the write log. You hand them to your auditor.

Ask a security question