Fleet work
Tracking, live dispatch and trips with rerouting.
Routing you run yourself, from an OpenStreetMap extract.
Give it an extract and it answers over HTTP: routes, trips, isochrones, matrices, map matching, transit and fleet optimization. Its web client shows the request, response and curl behind every result.
From extract to answers
Car, bicycle, foot, truck with height and weight limits, motorcycle and emergency profiles.
Isochrones as polygons or H3 cells, matrices, GTFS transit with realtime, and fleet optimization.
Every result shows the request, the response and the curl, so your developers can wire it in straight away.
AI variant: MCP server and assistant
An MCP server lets an agent ask the engine directly, and the web client includes an AI assistant.
For teams that need routing they control
Your servers
It prepares a graph per profile and keeps no database.
Wires into your product
Scoped keys, webhooks, automations, end-user tokens, a TypeScript SDK and OpenAPI.
Switch on what you need
Traffic-aware ETAs and ride-hailing, off until enabled.
Routes for your product and your agents
Your apps call it over HTTP. Agents ask it through MCP.
Routes
OSM extract
Your app
Dispatch
Webhooks
MCP
Nominatim
Under the hood
- Elixir and Phoenix with Rust NIFs, and a Svelte client
- Contraction Hierarchies and Customizable CH per profile
- Geocoding through a Nominatim you run
- GTFS with realtime updates
Paying per route for something you could run?
We’ll show it to you working, using the product and its demo materials, and talk through your case.
Ask for a demo