Who lands
Terminal / berth / gate ops, freight forwarding supervisor, 3PL ops, warehouse lead, logistics IT.
Logistics
Private models on the turn — berth, terminal, freight clock.
The work is the cycle time you already stamp, plus the documents around it. We run open-weight models on infrastructure you control: live tracking and delay remarks from timestamps, and extraction/exceptions into the TMS, WMS, or sheet you already run.
Who this page is for
The desk that already stamps the cycle
Who buys
Ops + IT. Commercial and movement data leaving to a US API is the compliance objection.
What we do
The same three services, on the logistics wall
On-premise & private AI
Models on the operator’s servers or private cloud. Movement stamps and commercial files do not go to a public API.
- Model selection and serving (vLLM, Ollama, or your stack)
- Private retrieval over SOPs and approved document sets
- Access control, audit logs, encryption in transit and at rest
- Default-deny outbound when policy requires it
Custom models
Terminal / location codes, commodity codes, customer aliases, SOP language.
- Fine-tuning on your corpus if needed
- RAG evaluated on real ops prompts
- English and Bahasa Malaysia
- Quantisation to the hardware you have
LLM automation workflows
Clock engine + documents.
- Timestamp-to-slip/delay remarks into the ops sheet/chat
- Exception classify (delay, hold, short-ship) into the shift’s WhatsApp or email
- Invoice / BL / packing-list extraction into the TMS or sheet, where you approve write-back
- Guardrails: we do not replace the TOS/WMS/TMS
First workflows
The turn, then the paper around it
Example scope
Terminal / berth / truck-cycle clock
Timestamps to delay/slip prediction and operational remarks into the ops sheet or chat the shift already uses. Same clock engine as aviation; different yard.
Example scope
Exception classify
Delay, damage, short-ship, hold — into the WhatsApp or email the shift already uses.
Example scope
Document extraction
Customs / commercial invoice / packing-list / BL into the TMS or sheet — secondary to the turn, not the only story.
These are first workflows we would scope. They are not case studies. No invented clearance percentages. No named terminals.
Data & security
Why on-prem on this desk
Where it runs
On-prem or private cloud you control. We do not require a public model API.
How we handle data
Encrypted in transit and at rest. We do not train a third-party model on your corpus, and we do not pool client data. Customer commercial files stay on your side of the wall.
How we integrate
Read the TOS/TMS/WMS/sheet first. Write-back only where you approve it. We do not claim a named TOS connector.
Who it belongs to
Weights, prompts, evaluations, and logs stay yours. NDA before deeper scoping.
Built in Malaysia · data residency as a design constraint · English and Bahasa. Why Malaysia
Get in touch
If this is terminal or freight ops, write to us
Berth, yard, warehouse, or 3PL IT — if the stamps and the documents cannot leave, say so.
[email protected]Public contact for projects, partnerships, research, and investor conversations.