About Navo24

We build the freight tools we wished we had.

Navo24 makes the things ocean freight runs on: container tracking, sailing schedules, spot rates and load planning. It ships them as components your software and your AI can call directly. One data layer, four products, adopt them a piece at a time.

The shape of it

A trunk and its leaves.

Tracking is the trunk. It writes down what really happened to a container: the events, the delays, the arrivals, normalised to the industry standard so it means the same thing on every carrier.

Schedules and loading are leaves that feed it. Schedules reads the arrivals tracking recorded and turns them into lane reliability you can book on. Loading plans the box that fills those sailings, to the rules cargo actually ships under. The data flows one way, toward the thing you ship, and the parts make each other smarter.

None of them depend on another to run. That is deliberate. You should be able to start with the one that hurts most today and never be told to buy the other two.

In numbers: the tracking layer covers 233 carriers through 125 direct connectors and recognises 186 SCACs, with 2–3 independent fallback data sources per carrier and positions fused from 4 live AIS networks. The schedule layer holds 5,000+ lanes, 255 ports and 72,000+ forward sailings, and is cross-checked against every tracked container. The loading engine plans to the CTU Code, IMDG segregation, EN 12195 lashing and road limits in the EU, US and China. Everything ships three ways: web, REST API, and first-party MCP servers your AI agents can call, with events normalised to the DCSA standard.

What we hold to

Three things we won't trade.

Show the truth, never hallucinate

A status is "done" only when a real event backs it. An ETA is a prediction that moves, with a reason attached. "No data" and "nothing happened" are different states, and we never blur them to look more finished than we are.

Components, not a platform

You should be able to take one tool, whether a tracking webhook, a schedule lookup or a load plan, and wire it into what you already run. No migration, no rip-and-replace, no front-end of ours you are forced to adopt.

Speak freight, not SaaS

The copy, the fields and the defaults read like a freight desk wrote them, because one did. If a feature would not survive a conversation with an operations manager, it does not ship.

Start with one component.

Pick the tool that solves your loudest problem today. The rest of the spine is here when you want it.

Explore the suite Talk to the desk