Cold-chain control tower

One operational picture for temperature-controlled freight.

Quayfold brings shipments, sensor traces and exceptions across ocean, air, road and rail into a single workspace, with a named human decision and a tamper-evident record behind every release.

Contact sales Open the live demo

Sandbox with fictional data. No sign-up required. Early access is open to forwarders, shippers and 3PLs.

Control tower / OverviewLive · demo data

Active shipments47+6 vs last week

On-time rate93.8%+1.2 pts

Open excursions31 needs review

Pending approvals2Median wait 38 min

Live network · great-circle routesOn trackAt riskExcursion

Alerts

QF-24777Set-point excursion, 38 min

3 min ago

QF-24811Release approval requested

2 h ago

QF-24765Temperature recovered

5 h ago

QF-24741Port dwell above plan

7 h ago

Shipment	Lane	Mode	Temp	Status	ETA
QF-24803	Rotterdam → New York / NJ	Ocean	−19.2°C	In transit	Oct 9
QF-24777	Shanghai → Hamburg	Ocean	−0.4°C	Excursion	Oct 18
QF-24790	Frankfurt → Chicago O’Hare	Air	+4.8°C	In transit	Oct 6
QF-24811	Valparaíso → Rotterdam	Ocean	+2.1°C	Awaiting approval	Oct 21

4transport modes in one view

28ports and airports in the demo network

4roles enforced on the server

1hash-chained audit trail

Platform

Built for the gap between an alert and an answer.

Three capabilities carry most of the day-to-day work. Each is available in the sandbox with representative data.

Visibility

See the temperature, not just the position.

Every shipment carries its permitted band. Readings are plotted against it, so a drift is visible while there is still time to act.

Per-shipment bands and set-points
Position and temperature on one timeline
Risk score ranked across the network

QF-24803

Frozen salmon fillets · Rotterdam to New York / New Jersey

In transit

1 excursion · 38 minBack in rangeLogger L-7741

Exceptions

Decisions that arrive with their evidence.

An excursion becomes a brief: trace, carrier record, cargo value and cost impact. A manager approves or rejects with a note; requesters cannot approve their own requests.

Four-eyes approval rule
Notifications on every decision
Outcome written to the audit trail

QF-24811 · Excursion release

Requested by Lena Okafor · 2h ago

Awaiting approval

Logger shows 38 minutes above the upper limit during a plug swap. Pulp temperature stayed in range; QA recommends release with a shortened shelf-life flag.

Cost impact$0

Carrier on-time94.2%

Cargo value$212,400

Four-eyes enforced

Network

Know which lanes and carriers earn their place.

Weekly on-time and excursion rates roll up by lane and carrier, so contract reviews start from data rather than anecdote.

Lane and carrier scorecards
CSV export for finance and quality
Role-scoped read-only access

On-time performance, last 13 weeks (demo data)

CLSAI → NLRTM

Cherries · ocean

94%

NZAKL → USLAX

Butter · ocean

91%

DEFRA → USORD

Insulin · air

97%

CNSHA → DEHAM

Pharma · rail

89%

Nordlys Reefer Line96%

Skerry Air Freight92%

Tidewell Chill Co84%

Halvard Rail Lines78%

Workflow

From sensor drift to signed decision.

What the product does in that gap, step by step, with the data an operator would see.

03:12 UTC · Reefer 44 of 61

A reading drifts at the dock.

The logger on a pallet of frozen salmon reports −16.4°C against a −18°C ceiling. Quayfold marks the trace, scores the risk and puts the shipment at the top of the overview before anyone is awake.

03:20 UTC · Brief assembled

The decision arrives with its evidence.

A planner raises the release. The approver sees the cause, the cost of each option, the carrier record and the cargo value on one card. Nobody approves their own request.

03:41 UTC · Recorded

Signed, linked, and impossible to quietly edit.

The outcome updates the shipment and lands in a hash-chained audit trail. Every entry commits to the one before it, and the Audit page verifies the chain on demand.

Set range -22.0°C to -18.0°C · six probes along the boxReading outside range

QF-24803 · Logger L-7741

Frozen salmon · Rotterdam to New York / NJ

Excursion · 38 min

Security architecture

Controls you can inspect, with an honest compliance posture.

Every control below is implemented in the sandbox today. No third-party certification is claimed; planned work is labelled as planned.

01 · Client

Browser or API consumer

Session cookie (httpOnly, SameSite)
CSRF token header on writes
No secrets in client storage

02 · Edge

Transport and browser policy

TLS and HSTS (over HTTPS)
Content-Security-Policy with nonces
Frame denial, no MIME sniffing
Per-IP and per-account rate limits

03 · Application

Server-side enforcement

Opaque session, SHA-256 at rest
Origin and CSRF verification
Role checks on every endpoint
Strict schema validation

04 · Data

Storage and evidence

Parameterised statements only
argon2id credential hashes
Hash-chained, append-only audit
Verification on demand

Trust boundary starts at the edge. Everything to its right is verified server-side regardless of what the interface shows.

Read the security overview

API and integrations

The console is built on the API.

Every screen is backed by validated JSON endpoints. Integration targets are listed with their real status, so nothing is promised that does not exist.

Explore the API preview

RequestGET

curl -s https://api.example.com/api/shipments \
  -G --data-urlencode "status=delayed" \
  -H "Cookie: qf_session=…"

Response200 OK

{
  "items": [{
    "ref": "QF-24777",
    "lane": "Shanghai → Hamburg",
    "status": "delayed",
    "temp": { "last": -0.4, "min": -22, "max": -18 },
    "risk": 82
  }],
  "total": 3
}

REST and JSON APIAvailable in the demo

CSV exportAvailable in the demo

Webhooks for exceptionsPlanned

Telematics and logger feedsPlanned

EDI status messagesPlanned

Transport management systemsPlanned

Single sign-on (SAML, OIDC)Planned

Data warehouse syncPlanned

FAQ

Straight answers.

More detail is on the resources page.

Is Quayfold a shipping product I can buy today?

Not yet. It is a product concept in early access, running here as a sandbox against fictional data so you can evaluate the workflows, permissions and audit behaviour.

Which security certifications do you hold?

None. We describe the controls that are implemented in the code and those that are planned, and we do not claim SOC 2, ISO 27001 or any other attestation.

Where does the temperature data come from?

In the sandbox, readings are simulated. In a deployment they would be ingested from logger and telematics feeds, which are listed as planned integrations.

Can we run it on our own infrastructure?

The reference build is a Node service with an embedded database and a Docker image. Production tenancy on PostgreSQL is on the roadmap.

Early access

Join the first cohort.

We are onboarding a small number of forwarders, shippers and 3PLs with temperature-controlled lanes. Tell us about your network and we will be in touch before launch.

#a91fshipment.excursionby system · prev #0000linked

#3c07approval.requestedby L. Okafor · prev #a91flinked

#e5b2approval.approvedby M. Adeyemi · prev #3c07linked

#7d40shipment.releasedby system · prev #e5b2linked