Notices arrive as documents
Port omissions, blank sailings and rotation changes land as PDFs, web pages and emails, each in its own format.
Commercial intelligence for ports & terminals
Turn fragmented ecosystem data
into commercial decisions
Corridor Twin is a living model of the trade corridors behind your volumes. It reads carrier notices, partner feeds and market news as they happen, shows your commercial team where untapped demand sits and why, and lets you test a move before you commit to it.
- Starts on a synthetic copy of your data
- Scores you can explain
- Named review and approval
Corridor · on the map▲ 6 this quarter
Shanghai → Rotterdam
74of 100 · ranked #1
Carrier noticeReviewed
Port omission · Asia–Europe loop
“Voyage 214W will omit Port A; cargo will be relayed via Port B on the next feeder.”
- Effective
- Week 41
- Evidence
- 2 quotes, checked
- Corridors touched
- 3
- Boxes relayed
- +1.4k TEU / yr
Scenario · current → proposed
Feeder loop + inland rail shuttle
TEU a year through your terminals
- Commercial impact
- +38k TEU / yr
- Opportunity captured
- 6 points
- Approval
- Commercial lead
Illustrative network, names and figures
Built for
Container terminal operators
Port authorities
Transhipment hubs
Inland & rail terminals
Logistics & free zones
The challenge
The data is there. It is just scattered.
Shipping lines, forwarders, cargo owners, inland operators and authorities each hold part of the picture. Commercial teams stitch it together by hand, and by the time the analysis is ready, the cargo has moved.
Partners guard their data
Forwarders, carriers and inland partners can't hand over commercially sensitive data, so whole stretches of each corridor stay out of view.
Opportunity hides between systems
Volumes, network plans and customer records live in separate tools, so nobody sees where untapped demand actually sits.
Decisions trail the network
When a service changes or a trade route shifts, the window to respond is short, and spreadsheets take longer than that.
Most of this comes down to one problem: getting the data at all. Industry-wide data platforms have stalled on exactly that. Corridor Twin starts where it needs nobody's permission: your own data.
How it works
The platform
One decision loop, from signal to action
Six workspaces in four steps. Each answers one question, and hands its answer to the next.
Where should we look?Every corridor in your network, ranked by the opportunity you have not captured yet. Filter by trade lane and by your footprint.
Opportunities across the network
All lanesFootprint: any
| # | Corridor | Lane | Opportunity | Δ qtr |
|---|---|---|---|---|
| 1 | Shanghai → Rotterdam | Asia → Europe | 74 | +6 |
| 2 | Busan → Los Angeles | Asia → North America | 69 | +2 |
| 3 | Singapore → Jebel Ali | Asia → Middle East | 66 | +4 |
| 4 | Rotterdam → Santos | Europe → Latin America | 61 | −1 |
| 5 | Antwerp → Lomé | Europe → Africa | 57 | +3 |
Shanghai → Rotterdam
Asia → Europe lane
74opportunity score
Flow density86 · +21.5
Growth66 · +13.2
Footprint fit72 · +14.4
Headroom80 · +12.0
Inland potential55 · +5.5
Partner readiness70 · +7.0
Read it as a sentence: dense, growing flows and plenty of headroom drive this corridor's score; thin inland reach holds it back. Each part is a value from 0 to 100, times a weight your team can see and change.
Scenario: win more of Shanghai → Rotterdam
2 levers on
New feeder loop
Weekly relay to two secondary ports.
Inland rail shuttle
Three departures a week to an inland hub.
Data partnership
Shared forecasts with a forwarder.
Current412kTEU a year
Proposed450kTEU a year
Impact through your terminals+38k TEU a year6 points of the corridor's open opportunity captured
Real-world event from today's news: chokepoint diversion
Who the change reaches
Feeder loop + rail shuttle
Customers
COCargo owner · electronicsGains · 3 days faster
FWForwarder · regionalExposed · extra call
COCargo owner · retailGains · inland reach
Advisory approved by the commercial lead, with a reason on record
Ecosystem
Feeder operatorRail operatorInland depotCustoms broker
Signals
Every service change, read, checked and sized
Carrier notices and partner feeds become structured events your team can trust, with the source one click away.
Reads any format
Web notices, PDFs and pasted text are read by the AI into structured events: carrier, service, voyage, ports and dates.
Keeps the evidence
Every fact carries the exact passage it came from, and code checks each quote against the source.
Sizes the effect
Ports and services are matched to your corridors, and the effect is sized by what the affected sailings carry.
Waits for a person
A named analyst reviews each extraction. Only reviewed notices change the model.
Customer advisory · Carrier A · PDF
Please be advised that voyage 214W will omit Port A due to congestion. Cargo for Port A will be relayed via Port B on the next available feeder.
Read by the AI, quotes checked by code
Port omissionReviewed by an analyst
- Service
- Asia–Europe loop · 214W
- Omitted
- Port A
- Relayed via
- Port B
- Evidence
- 2 quotes, both found in the notice
Effect on the Twin · 3 corridors+1.4k TEU a year
Your data
Your data stays put.
Your data stays put.
A synthetic copy does the work.
The hard part is rarely the model. It is getting the data at all: it sits with many parties, in many countries, under rules that limit what may move. So Corridor Twin starts with your own records, through a copy that carries their patterns and none of their secrets.
Your records stay locked
Terminal and customer data never leave your environment. When partners join later, their data goes into a clean room and never leaves it either.
A copy leaves, not the data
A model writes a synthetic copy: the same totals and the same patterns, but no real shipper, carrier or cargo inside it.
Teams try before they trust
Commercial teams in every country work on the copy, without a legal approval for each dataset.
Two numbers decide whether a copy may leave
Accuracy: are its totals close enough to the truth for a commercial team to rely on them? Privacy: can any record in it be traced back to a real one? A release check tests both, and a named person signs off.
Accuracy · gap to the real totals1.9%must stay under 8%
Privacy · records traceable to a real one0.4%must stay under 5%
Release check passed · signed off by the data owner
Governance
AI interprets. Rules compute. People decide.
Commercial decisions need an owner and a trail. Corridor Twin keeps each part of the work where it belongs.
AI interprets
The AI reads notices, news and plain-language questions, and always shows where each statement came from. It drafts; it never decides.
Rules compute
Scores, scenarios and effects follow rules anyone on the team can read and challenge. Same inputs, same answer, every time.
People decide
Reviews and approvals carry a name and a reason, and they are kept, so every decision has an owner and a history.
- Access by invitationNamed accounts only; no public sign-up.
- Evidence on every factEach extracted fact links to its passage.
- Review historyCorrections, reasons and reviewers are kept.
- Explainable scoresSix readable parts and visible weights.
Illustrative
Ecosystem
Partners share answers, not their data
When you are ready to bring shipping lines, rail operators or forwarders in, their data joins yours in a clean room. It works like a ballot box: everyone drops their data in, nobody can open it, and only the count comes out. The partners agree in advance which questions may be asked.
- Sealed on the way in. Each partner encrypts its data with a key only it holds.
- Checked before anyone joins. The room proves it runs exactly the program every partner approved, or no key is handed over.
- Only totals come out. Answers about many boxes, slightly blurred, never about one customer; small counts are withheld.
- A privacy–utility setting and a release check decide how much detail an answer may reveal before it is shared.
Partners join through the clean room when you are ready: step 3 of getting started. Getting started →
Who it's for
Built for the teams that grow a port's business
Commercial & business development
Find the corridors worth chasing, and build the case for each with numbers anyone can check.
Network & capacity planning
See how service changes and new levers move volumes across your network before they happen.
Customer & key account teams
Know which customers a change touches, and tell them first, with an advisory someone approved.
Partnerships & ecosystem
Pick the partners a move needs, and share data with them at the level of detail you choose.
Getting started
Up and running without a data-sharing agreement
Start with your own data, in your own environment. Widen it at your own pace.
-
Start here
Step 1
Connect
Connect your terminal data inside your environment, starting with two or three terminals. It is checked before anyone works with it, and it never leaves.
-
Step 2
Roll out
Bring in your commercial teams in every country, on one shared twin. Your team sets the scoring weights and the scenario rules.
-
Step 3
Extend
Bring in partners and customers when you are ready, through the clean room: partners add their feeds, customers see their own network.
Request access
See your network in the Twin
Corridor Twin is available by invitation. Tell us about your organisation and what you would like to explore, and we will get back to you to arrange access and a guided walkthrough. Most teams start with two or three terminals in one region.
- Tell us about your networkYour terminals, the trades you serve and the questions on your desk.
- We confirm your accessWe review each request and reply to the email you give.
- Your team signs inEach person gets a named account; reviews and approvals carry their name.