RoutePlanAddresses → driver routes

About

A route optimiser for people running a handful of vans, who need a route once, today, without signing up for anything.

Who it is for

A dispatcher or owner-operator with twenty to eighty stops and two to six vehicles. Route optimisation at that scale is usually sold as a per-seat monthly subscription bundled with driver tracking, proof of delivery and a customer-notification suite. If all you want is the route, that is a lot of product to buy and a lot of onboarding to sit through.

What it deliberately is not

The absent features are choices, not a roadmap. Each one is a separate product, and adding them would turn a tool you can use in two minutes into one you have to adopt.

  • No accounts. Nothing to sign up for or cancel.
  • No database. Addresses are never stored. A share link carries the whole plan in the URL itself, and only exists if you make one.
  • No driver tracking, no proof of delivery, no customer notifications. This plans routes.
  • No analytics or trackers. Nothing follows you around.

Where it falls short

Worth knowing before you rely on it, and easier to say plainly than to have you discover:

  • 99 stops per plan. The road-distance service takes 100 coordinates per request and the depot uses one. Self-hosting lifts it.
  • No time windows yet. If a customer only accepts deliveries between two and four, the plan does not know. The data format already carries the field, so adding it is not a rewrite.
  • No vehicle capacities yet. Same story — the field exists, the solver ignores it.
  • One depot. Every van starts and ends in the same place.
  • Traffic is not modelled. Distances and times are free-flow. A round planned for rush hour will run long.

How it is built

Next.js and TypeScript, with the map on MapLibre and road distances from OSRM. Addresses are resolved by Photon or Nominatim, both built on OpenStreetMap. The routing engines are described on the algorithms page.

The map is a client of the same public API you can call yourself, so the API is exercised on every single plan and cannot quietly rot. It is documented on the API page.

Licence and data

MIT licensed — use it, change it, run your own copy. Map data is © OpenStreetMap contributors, under the Open Database Licence.

Plan routes