Cierge Use Cases/Supply Chain Use Cases/FreightCierge
Pilot · Freight Innovation Fund · Sandbox demo

When freight exceptions arise,
FreightCierge turns the response into accountable action.

FreightCierge is a KATLAS-powered governance layer for port-corridor freight. It does not replace terminal, vessel, telematics or customs systems. It coordinates the decisions between them: the right role sees the right evidence, authorised actions produce signed receipts, and an evidence pack forms as the response unfolds.

The problem we are solving

Disruption is rarely a visibility problem. It is a coordination problem.

It is not just a data problem

When a movement is disrupted, the gap is rarely visibility. It is uncertainty over who can decide, on what basis, and with what evidence.

Several organisations, one decision

Port, vessel, terminal, haulage and compliance teams have overlapping stakes — but separate systems and separate authorities.

Existing systems stay in place

Operators do not need another central database. They need a coordination and assurance layer that respects the systems already running.

How it works

Existing systems feed in. Governed actions and evidence come out.

FreightCierge sits between the operational signal layer and the action layer. The KATLAS node performs runtime CAR governance — Custody, Authority, Receipts — before any consequential action is executed.

  1. STEP 01
    Operational issue detected

    ETA drift, congestion, documentation friction or a missed cut-off risk surface from existing systems.

  2. STEP 02
    Recommended actions surfaced

    Predictive signals (e.g. SiftyML) and operational rules surface candidate actions — they do not determine authority.

  3. STEP 03
    KATLAS governance gate

    CAR rules check Custody, Authority and policy. The action is allowed, blocked or escalated for named approval.

  4. STEP 04
    Receipt + evidence pack

    A signed receipt is attached to the event. Downstream parties are notified through purpose-bound channels.

The coordination layer

A thin governance layer over existing systems.

Terminal Ops
Vessel/AIS
Telematics
Customs/Docs
Yard Planning
Haulage TMS
Existing systems · sources of signal
FREIGHTCIERGE · KATLAS NODE
CAR runtime governance
  • Custody controls the evidence.
  • Authority governs the action.
  • Receipts prove what happened.
KATLAS records the governed action — not a copy of everyone's private data. Evidence stays at source.
Output 1 · Governed actions

Right role · right authority · right moment. A governed exception response, not an alert feed.

Output 2 · Clearance-ready evidence

Signed receipts for freight handoffs and decisions · linked event · downstream notifications.

What changes for assessors and operators

Outcomes a non-technical assessor can see and measure.

OUTCOME 01
Faster, cleaner exception resolution

Recommended actions are routed to the role that may decide. Less chasing, fewer dead ends.

OUTCOME 02
Decisions with attributable receipts

Every consequential action produces a signed receipt: actor, authority, basis, evidence.

OUTCOME 03
Audit-ready by default

An evidence pack assembles itself as the response unfolds — ready for regulators, customers and partners.

Ready to see it

Open the live sandbox or take the guided walkthrough.

FreightCiergePilot sandbox for the Freight Innovation Fund
CAR runtime · KATLAS node · Attributable receipts

Made with Emergent