kint manifest
Move more with less. Provably. The decision layer for operators of asset-heavy logistics nodes that makes expensive capacity, equipment and throughput decisions optimal instead of merely visible.
The decisions nobody computes
Your most expensive decisions are made on gut feel.
How much equipment to run. Which capacity to commit. Berth and yard strategy. The answer is buried in distributed data and in a simulation nobody runs by hand. So planners reach for Excel and heuristics.
Your terminal operating system shows you what is happening. It does not tell you what to do. kint manifest sits above it and answers the capex and operating questions your TOS leaves open.
Terminal & Port Ops
One screen. Every expensive decision, already optimal.
Berth allocation, yard strategy and equipment sizing computed together, not in separate spreadsheets. Each number carries a solver certificate.
All three vessels cleared inside the 3h window. Crane STS-2 freed at 02:00 and reassigned.
One engine, four modules
From the network down to the quay crane.
Each module answers the decisions its layer leaves open. Run one, or run them together on the same optimization brain.
Where capacity should live
Network design across locations and flows. Decide which nodes carry which volume and how cost-to-serve moves when demand shifts.
How many vehicles, which tours
Fleet sizing and vehicle routing with time windows. CVRP, VRPTW, multi-depot. The right number of assets, not the comfortable one.
Storage and yard strategy
Slotting and yard strategy that cuts dwell time and rehandles. Put boxes where the next move is cheapest.
Terminal & Port Ops
Berth allocation, quay crane split, yard strategy, equipment sizing and gate flow. Tuned with the reference customer and exclusive to their segment.
Forecasts tell you a storm is coming. kint tells you which cranes to move, and proves it was the cheapest way to clear three ships by noon.
How kint decides
What is the minimum fleet size to unload three vessels in under three hours?
Same data, different question. The TOS cannot answer this. kint does, in milliseconds, with the reasoning attached.
Minimum fleet to clear 3 vessels < 3h
Why operators choose kint
Built for the people who own the P&L.
We do not replace your systems
kint sits above your TOS and your data. It makes the decisions they leave open. Nothing to rip out.
It works even with no formula
When there is no ready model, kint learns the relationship from your data and finds the best operating point in milliseconds, with confidence gating.
Every answer has a reason and a record
Each recommendation ships with the binding constraint, the sensitivity, and an audit trail you can present to liable management later.
The category gap
The optimization brain above the TOS.
Others execute, model by hand, or predict. None of them decide. Forecasts are not decisions.
| Their approach | kint manifest | |
|---|---|---|
Terminal operating systems TOS / TMS | Run the terminal and show the plan. Leave the sizing open and never improve it. | The optimization brain above the TOS. Decisions, not dashboards. |
Hand-built OR models consultant-built | One model per terminal, built by consultants. Months to adapt, rigid when operations change. | Generates the model from description plus data. Adapted in days, not months. |
Forecasting tools arrivals & congestion | Forecast vessel arrivals and congestion, then hand the decision back to you. | Decides, provably optimal, and answers the capex and equipment-sizing questions. |
Powered by the kint engine
Proof, not promises.
Stop sizing on gut feel.
Bring one shift of your terminal data. We will show you the optimal plan, the reason behind it, and the record you can defend.