The navigation platform you can take in-house.
A complete routing and guidance platform for fleets and AI agents, online or fully offline. Car, van, bus, two-wheeler and pedestrian routing come as standard. Our edge is where it gets hard: commercial truck routing with ADR dangerous-goods tunnel enforcement and dimensional restrictions.
Profiles: car · van · truck · bus · two-wheeler · pedestrian.
Agents start here: /llms.txt · /pricing.json · /agents
One platform. Three ways to consume it.
The same routing and compliance core, delivered however your product needs it. Start on the hosted API today, embed the offline SDK when you ship an app, and open it to agents when you are ready. All three read from the same signed data layer.
Call our routing and compliance API
Point your stack at our gateway. Metered API keys, pay as you go, routing and ADR compliance for every profile. Start in minutes with a card-free key, no sales call.
Embed our navigation SDK in your app
Turn-by-turn guidance that runs fully offline inside your Android or iOS app. Signed territory packages, on-device routing and ADR enforcement, over-the-air map updates. One Rust core, Kotlin and Swift bindings.
Let AI agents route and check compliance
An MCP server, llms.txt discovery, one-call API keys and machine payments. Agents can find us, price us, get a key and route without a human in the loop.
Signed, versioned territory packages
Every deployment routes on the same territory packages: signed with ed25519, content-addressed with BLAKE3, delivered over the air as differential updates. Maps and truck-restriction data stay fresh without a full re-download.
If you can’t self-host it,
you don’t control it.
Most navigation licences forbid the things fleets actually need: offline operation, caching, self-hosting, audit. MapMap is built the other way. First-party Rust, a machine-enforced licence gate in CI, an SBOM with every release, and a Docker distro so the whole stack runs inside your network.
| What you get | How it’s proven |
|---|---|
| Truck and ADR routing (height, weight, tunnel codes) | Enforced in costing, not post-filtered; cross-validated with differential route tests |
| Offline territory packages | ed25519-signed manifests, BLAKE3 content hashes, over-the-air differential updates |
| Licence-clean distributables | Permissive-only dependency gate in CI; lineage documented per component |
| Supply-chain transparency | CycloneDX SBOM and licence inventory published with every tagged release |
| Engineering rigour | 700+ automated tests across the Rust workspace and the Kotlin/Swift bindings |
No customer logos and no invented benchmarks. Every claim above is checkable in the repository.
An agent can discover, evaluate and use it unaided.
One-call key issuance, llms.txt on the site and on every gateway deployment, machine-readable pricing, RFC 9457 problem+json errors, an MCP server with routing and ADR-compliance tools, and a 402 response shape ready for per-call machine payments. Nothing gated behind a sales call.