The platform
From system of record to system of visibility
Operational systems know what happened. Neolink turns that raw feed into what it means — where every shipment is, whether it's late, what's threatening it, and what it costs — minutes after the data exists, with no double entry.
Live from day one
CargoWise posts every shipment save straight to Neolink over a secured channel. Delivery is guaranteed — nothing is acknowledged until it's durably stored — and every message imports exactly once, no matter how often it's redelivered.
Meaning, not messages
A pure rules engine computes each shipment's schedule, health, stage, exceptions and KPIs — every date with its provenance. A nightly sweep re-evaluates the whole book, so a shipment that goes quiet gets flagged without a single new message.
One scoped picture
Tracking, map, risk radar, reports and documents — every surface reads the same truth, and every row is filtered server-side to the viewer's own office tree. A customer can never see another customer's cargo.
Control Tower
The tracking screen that replaces the spreadsheet
One live table of every shipment your office can see — shaped by each user, filtered like a database, saved as views the whole team snaps back to. It ends the export-to-Excel ritual and the "where is my container?" email thread.
| Shipment | Route & schedule | Status | Slip | Cargo |
|---|---|---|---|---|
| S00482117 | CNSHA → NLRTM · ETA 24 AUG | On time | ±0d | 3 × 40HC |
| S00481963 | SGSIN → DEHAM · ETA 29 AUG | At risk | +2d | 2 × 40RH |
| S00481720 | KRPUS → USLAX · ETA 19 AUG | Delayed ROLLOVER | +6d | 5 × 40HC |
| S00482201 | BRSSZ → BEANR · ETA 02 SEP | On time | ±0d | LCL · 12 t |
- A 40-column catalog, shaped per user. Identifiers, schedule, route, cargo, carrier & vessel, parties, operations — pick, reorder, resize, and save it as a named view that follows you across devices.
- Filters like a database, not a search box. Compound conditions across 26 fields — (reefer AND via Singapore) OR flagged late — built visually, applied server-side, shown as removable pills.
- Slip, not just status. Every ETA revision is recorded, so the table shows how far a promise has drifted — and a shipment that goes quiet is flagged by the nightly sweep on elapsed time alone.
- Typed exceptions. Ten exception types across four severity bands — rollover, missed cut-off, detention risk, no-update — raised and auto-resolved by rules, not by hand.
- One view, two surfaces. Any saved view opens as this table or as the live map — same filter, same scope, one URL to share.
- Ten tabs deep on every shipment. Details, signals, containers, exceptions, parties, activity, documents, subscriptions, billing and CO₂ — a single page answers the whole "what's the story on this box?" call.
- A route you can trust. The hero map draws the real ocean geometry, splits travelled from remaining at the vessel's position, and the timeline carries the full ETA drift history — not just today's number.
- Containers, honestly. An eight-event lifecycle strip per container; estimates render as estimates and are never promoted to "done".
- Booked28 JUL
- Departed ShanghaiATD 02 AUG
- Transshipment · Singapore09 AUG
- At sea — near ColomboNOW
ETA revised 22 → 24 AUG · slip +2d recorded - Arrival RotterdamETA 24 AUG
Live Map
Your whole fleet, on real ocean routes
Not decorative arcs — genuine sea-lane geometry on a vector map, with shipments grouped by the vessel actually carrying them, world events overlaid, and a simulator that prices "what if the Suez closes?" before it happens.
Real routes
Genuine maritime-network geometry per trade lane — sea legs on real water, air legs great-circle, transshipment nodes at every joint.
Cascade exposure
Shipments sailing on the same vessel collapse into one marker — total TEU, customers, health mix — because one vessel delay cascades to everything aboard.
Price the detour
Suez, Panama, Bab el-Mandeb, Malacca: one click draws the avoidance route and the bill — days, nautical miles, fuel — without touching a single ETA.
Who slips where
Chronic ETA slip painted per lane, with a carrier scorecard on click — worst first, every stat carrying its sample size. 30 / 90 / 180-day windows.
Honest alarm
Signals draw as hollow rings so they can never be mistaken for cargo — and a route only tints red when the risk engine actually matched it.
Filter, then cap
The same saved views and filters as the table, applied server-side before the 5,000-marker cap — "showing X of Y" is always the truth.
Radar · Signals
The outside world, matched to your cargo
Control Tower tells you where a shipment is. Radar tells you what's about to hit it — global news scanned continuously, distilled into ports, lanes and carriers, then matched against your offices' actual live footprint. A risk feed, not a news ticker.
Industrial action announced — Port of Rotterdam
News · 13 Aug · Severity High · 72/100
18 shipments exposed 4 already at risk 610 TEU2 open exceptions
- Concrete exposure, never vibes. Every signal states the shipments, containers and TEU it actually touches — consolidations de-duplicated so nothing is counted twice.
- Deterministic scoring, explainable to an auditor. Event weight × exposure, banded low to critical. AI writes the summary and the suggested action; it never sets the risk number.
- Everywhere it matters. The same signal surfaces on the analyst triage screen, as rings on the fleet map, on the shipment page, on the home dashboard, and inside report narratives.
- Always on. Ingest every 15 minutes, matching every 5 — tuned to each office's own ports, lanes, carriers and counterparties.
- Ingest
Global news, continuously — source-agnostic, ready for congestion & weather feeds.
- Extract
AI distills each story into ports, countries, carriers and event types.
- Match
Deterministic join against each office's live shipment footprint.
- Alert
Severity-ranked feed with impact summary and a suggested action.
Grounded AI
AI that can only tell you the truth
Neolink's AI never invents a number. It phrases figures the platform already computed, drafts filters you approve before they run, and a runtime validator rejects any claim it can't trace. Boring by design — which is what makes it usable in operations.
- temperature controlled
- via = SGSIN
- ETA ≤ 7 days
- health = At risk
- Sentence in, filter out. The draft lands in the same visual builder, row by editable row. A hallucinated field fails validation and degrades to a hint — never to a silently loosened filter.
- Narration without minted numbers. Map insights and report narratives phrase figures already on screen; a sign-aware validator rejects anything else and falls back to deterministic text.
- Private by construction. Prompts carry the field catalog and aggregate counts — never shipment rows, references or party names.
- Metered from day one. Every AI call writes an append-only token ledger, split platform-cost vs per-office — the seed of per-customer AI billing.
- Next: the Neolink Assistant. Ask "how many shipments arrive in Germany next week?" — answered by calling the same permission-checked APIs as you, grounded in a 154-page platform corpus, with citations.
Reporting & Sustainability
Click to the answer, drill to the shipment
Four analytics categories — performance, volume, financial, emissions — where every chart is a filter and every analysis ends in the actual shipments behind it. With coverage honesty built in: a missing figure is excluded with a stated reason, never rendered as a zero.
On-time arrival · sea freight · last 6 months
Every bar is a filter — click to drill · Showing 1,204 of 1,310 · 92% coverage
12.4 t CO₂e
ISO 14083 · GLEC v3.2 · 665 emission factors
Computed in-house on every shipment — within ±1.6% of the commercial engine it replaces — plus a self-serve calculator and a full emissions reporting category. Customer-visible: a shipper's footprint is their data.
- Deterministic first, AI second. Benchmarks, anomaly flags and driver attribution are exact and reproducible; the AI narrative only phrases them — and links the live Radar signals that explain the dip.
- Audience-safe by construction. Cost, profit and margin don't exist in the model a customer composes against — the only financial metric they can even ask for is their own spend.
- Saved & shared. Any analysis becomes a private or office-shared report; three defaults ship out of the box.
- The money view, projected per viewer. Operators see receivables, payables, profit and margin per shipment; a customer sees only the charges their office is party to — with no hint anything was withheld.
Documents
Every document, attached to its shipment — automatically
Bills of lading, booking confirmations, invoices, packing lists: whatever CargoWise saves against a job lands in Neolink on its own, with full revision history and the sender's identity captured. No lost paperwork, no manual filing.
MBL_MSCUKL482117.pdf
Master bill · rev 3 · from Shanghai branch · 12 AUG
Booking_confirmation_0482117.pdf
Booking confirmation · rev 1 · 29 JUL
Packing_list_internal.xlsx
Packing list · rev 2 · 01 AUG
+ 2 earlier revisions kept — superseded, never deleted
- Both CargoWise dialects, one door. The modern Universal schema and the legacy envelope real traffic actually uses — same endpoint, same guarantees, up to 100 documents per delivery.
- Paperwork can arrive early. A document that lands before its shipment waits as an orphan and back-stamps itself the moment the shipment imports.
- Never a record without the file. Metadata is only written after the bytes are safely stored — with a SHA-256 fingerprint on every file.
- Next: the Document Hub. A Drive-like home for every document you're entitled to see — search and preview across all shipments, upload with a review step, bulk zip download, and a three-tier visibility model so internal paperwork never reaches a customer by accident.
Access & Trust
Enterprise access control, freight-shaped
Model the real organisation — HQ, branches, customers, their subsidiaries — and author policies in plain business language: "read shipment tracking, sea freight, France." Every screen and every row honours them, server-side, fail-closed.
- An author can never over-grant. The policy builder offers only what the author themself holds, live conflict pre-checks included — privilege escalation is blocked at authoring time, then re-checked at write time.
- Enforcement that actually bites. Control Tower gates 19 of its 23 API routes on grants before any data is fetched, and the caller's grants narrow the rows inside the query. No grant, no data.
- No existence leaks. A shipment outside your scope is "not found" — never "forbidden" — and a customer's payload simply omits internal fields rather than nulling them out.
- Deactivation means now. Disabling an account revokes its sessions everywhere, instantly; every permission change writes an audit record.
- Admins never learn passwords. New accounts get a single-use, 48-hour emailed set-password link — identity and credential are owned by different services by design.
- Four languages, one platform. English, German, French and Spanish across every surface.
ShipmentTracking : read · scopecountry — FR, DE· modeSEA
ShipmentTracking : list · scopeoffice subtree — Rotterdam
AUG 11 · 14:02 policy #214 attached → account 88 · permissionVersion 41 · sessions revalidated