Platform overview

One authorization plane for physical custody.

Freight Passport connects customer policy, current operational facts, verified evidence, protected changes, and an attributable custody record.

Capability map

How this part of Freight Passport is structured.

Explore the interactive demo →
01

ReleaseLock

Evaluates the current shipment relationship before pickup authority can exist.

  • Persisted evidence snapshot
  • Exact policy version and digest
  • Server-authoritative release decision
02

ChangeLock

Places protected shipment facts behind an attributable request and approval boundary.

  • One-field application
  • Stale authority revoked first
  • Fresh evaluation required
03

Policy Engine

Applies bounded, versioned controls for evidence, assignment, place, time, and risk.

  • Immutable published versions
  • Evidence freshness and assurance
  • Fail-closed required controls
04

Custody Ledger

Projects durable outbox events into attributable, ordered audit and custody history.

  • Decision provenance
  • Credential and replay history
  • Change and transfer timeline
05

Role-specific interfaces

Customers, gates, carriers, drivers, investigators, and auditors receive distinct views and actions.

  • Minimum gate disclosure
  • Scoped carrier operations
  • Evidence-oriented investigator views
06

Integration boundary

Existing business systems remain systems of record while Freight Passport turns their evidence into one policy decision.

  • TMS and WMS inputs
  • Identity and carrier evidence
  • Telematics and facility signals

Provider integrations shown here are categories, not claims of active commercial partnerships.

See it in context

Test the handoff decision yourself.

Use fictional shipment data to explore a valid arrival, a blocked mismatch, a protected change, and a replay attempt.