Can one carrier see another’s lanes?

No. Policy scopes each agent to its own carrier or 3PL, so a partner only ever sees the shipments it operates.

What about consignee PII?

Contact details are masked in the compiler before a response leaves, so a routing agent gets the stop, not the person.

Does this replace our TMS?

No. Nightshift sits in front of your TMS, WMS, and carrier APIs and serves a governed view of them. Your systems of record stay where they are.

Nightshift for Logistics

Every partner’s agent sees only its own lanes.

Your TMS, WMS and carrier APIs holds the data a routing agent needs and lots of data it simply does not. Nightshift serves each system agent a cataloged and scoped view to its lanes. Agents gain broader context while data remains governed, segmented and secure.

Get started freeTalk to sales

Network catalog4 sources

TMtms.shipments2.4M rows3.1kGoverned

WMwms.inventory840K rows1.5kGoverned

TEtelematics.streamlive5.2kLive

CAcarrier.apiread only280Read only

Governed catalog · scoped per carrier and lane

See it work

Why delivery slipped, across every system.

An agent connects Nightshift over MCP and attributes a $1.9M freight overage and the on-time-delivery miss across Manhattan, Oracle OTM, Samsara telematics, and the warehouse.

How a request moves

From request to ETA.

Agent asks

routing-agent requests its lane data

Policy runs

compiler scopes to the carrier and masks PII

Endpoint minted

a governed URL, scoped to this request

ETA back

the agent gets only its lanes, live

Partner isolation

Every partner sees only its lanes.

ACME Freight

Carrier

Its own shipments and rates, nothing from other carriers.

Vantage 3PL

3PL

The lanes it operates, with consignee contacts masked.

Northwind

Carrier

Live telematics for its trucks, no commercial fields.

What agents do

Agents that move freight, not data.

Quote a lane

Price and plan against live shipment and rate data, scoped to the carrier the agent works for.

Track to the door

Answer where-is-my-load from telematics streams, with consignee contacts masked.

Rebalance the network

Read inventory and capacity across the WMS to suggest moves, never seeing another carrier’s margin.

Isolation, in one view

Who sees what, by partner.

One catalog, but every carrier and 3PL gets its own slice. Policy decides each cell, so a partner reads its lanes, never another’s rates or margin.

Partner	Rates	Consignee	Lane margin	Other carriers
ACME FreightCarrier		masked	—	—
Vantage 3PL3PL	masked	masked	—	—
NorthwindCarrier	—	masked	—	—

Policy that knows the lane

Scope to a partner, mask a contact, hide a margin.

Policy reads like a routing rule. Scope an agent to one carrier's lanes, mask the consignee contact, and hide commercial fields like lane margin. It compiles into every endpoint, so there is no way around it.

Allow and deny by carrier, lane, or 3PL
Mask consignee PII and contact details
Hide commercial fields like rates and margin

policies/carrier-scope.policypolicy

# broker-agent sees its own lanes, customer PII masked
policy "broker-agent" {
  identity = "broker-agent"
  source   = tms.shipments
  allow where carrier = "ACME-FREIGHT"
  mask column consignee_contact
  deny column lane_margin
}

Questions the network asks

What dispatch wants to know.

Can one carrier see another’s lanes?: No. Policy scopes each agent to its own carrier or 3PL, so a partner only ever sees the shipments it operates.
What about consignee PII?: Contact details are masked in the compiler before a response leaves, so a routing agent gets the stop, not the person.
Does this replace our TMS?: No. Nightshift sits in front of your TMS, WMS, and carrier APIs and serves a governed view of them. Your systems of record stay where they are.

Put an agent on your supply chain data.

Start free, connect a TMS or telematics feed, and watch governed reads flow to your agent in minutes. Scope every partner to its own lanes from the first request.

Get started free Talk to sales

Want to look first? Take the product tour