Skip to content

50,000 free calls a month, card-free. Get an API key →

Solutions / On-Demand Delivery

Dispatch the best driver. Keep the delivery promise.

Travel-time matrices answer who should take the job, optimisation plans the round against time windows and capacities, and along-route search prices every detour. All on infrastructure you host.

From the order to the doorstep, one engine.

Each job below maps to one shipped tool: the same routing engine prices the dispatch decision, the round and the detour.

A dispatch view over a real MapMap map of Soho: three courier positions with engine-computed ETAs of 2 and 3 minutes, and a card assigning the nearest to a new order
Dispatch

Pick the right driver with a matrix

One many-to-many matrix call answers which driver reaches the pickup soonest. The card here is a mock-up; the three ETAs in it are real engine output. Self-hosted, recomputing the board costs nothing per element.

A real optimised scooter round through central Manchester with four numbered drops and cumulative times
Rounds

Plan rounds that respect reality

Multi-vehicle optimisation plans stops against time windows, capacities and vehicle profiles. A 3.5-tonne with a tail lift gets a round planned for that van.

Optimisation docs
A real eight-minute scooter reachability polygon over central London from a Soho kitchen, shaded blue over the MapMap map
Coverage

See your delivery zone honestly

Travel-time zones show what a promise actually covers, computed on the real road network rather than a circle on a postcode. This is a real eight-minute scooter zone from a Soho kitchen.

A Manchester delivery leg with a cafe marked directly on the route and a card showing its real detour cost: zero minutes
Along the route

Every detour has a price

Search along a route returns stops with their real engine-computed detour cost, so adding a pickup to a live round is a number, not a guess.

the whole stack, inside your own network
$ docker compose up -d --build
→ tiles · geocoder · router · guidance · territories
→ 0 external map dependencies
Self-hosted

Your order flow never leaves your network

Where your couriers are is your order book. Self-hosted, none of it transits a third party, and the live-feed architecture proven on thousands of London buses carries courier positions the same way.

Ink illustration of a delivery scooter on a route line with chat bubbles and dispatch lines running to a distant kitchen
Agent-first

Dispatch tools your agents can call

Matrix, optimisation, routing and along-route search are all callable from AI agents through the hosted MCP server, with a card-free API key in one call.

Known limit

ETAs come from the routing engine's speed model, not a live-traffic feed, and the optimiser runs as a configurable sidecar. Treat ETAs as what the road network supports, and pair them with your own service-time data.

Agent-first

A day of anonymised orders is enough to start.

That is enough for our AI agents to build round planning against your real depots and fleet profile. You will be looking at your own rounds, not a demo dataset.

The offer

What you are actually being offered.

On the page, not in the small print: the scope, the deliverable, the timetable and how the money works, before you spend an hour on a call finding out.

Who it is for
An on-demand or same-day operation choosing drivers and promising delivery times.
What is in scope
A day of anonymised orders is enough to start. We build round planning against your real depots and fleet profile.
What you get
Round planning on your own orders, with the dispatch ranking and the ETA model shown rather than hidden, so you can see what the promise rests on.
How long
Days rather than months, with the date agreed on the call.
What it costs
Scoped on the call. Routing and matrix calls are metered on the published rate card.
Next step
Send a day of anonymised orders and we will plan them against your depots.
Send us a day of orders