Skip to main content
Stacklane

Route optimisation, VRP solvers, real-time re-routing, a dispatcher's day measured in minutes saved.

Routing problems compound, every stop you add multiplies the search space. We build the solver layer (OR-Tools VRP with time windows, capacity constraints, driver shifts) plus the operational surfaces dispatchers actually use when the day breaks the plan.

What we build

  • OR-Tools VRP solvers with real constraints

    Vehicle Routing Problem solvers configured with time windows, driver shifts, vehicle capacity, restricted zones, and cost-per-mile penalties. Solver runs on a background job; large fleets get partitioned solvers running in parallel.

  • PostGIS for the geography

    Service areas, depot locations, and customer stops all live in PostGIS. Distance and travel-time matrices computed via OSRM or vendor routing APIs (Google, HERE, Mapbox) depending on the cost ceiling. The geography stays in the database the rest of the platform uses.

  • Real-time re-routing on disruptions

    Cancellations, late orders, vehicle breakdowns trigger partial re-optimisation in seconds. The unaffected portion of the route stays put; the impacted stops get reassigned with minimal disruption to other drivers.

  • Driver app surfaces what matters next

    Native mobile app showing the next stop, navigation handoff to the driver's preferred app, proof-of-delivery capture (signature, photo, barcode scan). Offline-first: the route persists locally so dropped signal doesn't lose progress.

  • Dispatcher console for the live day

    Map-first interface showing where every driver is, which routes are running late, and which can absorb a late add. Drag-and-drop reassignment with constraint feedback so dispatchers don't accidentally violate driver shifts.

  • Reporting + reconciliation

    Per-route metrics on plan-vs-actual (time, distance, fuel) feed back into the solver's cost parameters. Reconciliation against payroll and customer billing happens in the same system, not a separate spreadsheet pipeline.

Where this fits

  1. Your fleet grew past the point where a person with a whiteboard can keep up with daily routing.

  2. Your current routing software is a vendor SaaS that doesn't fit your business rules and the workarounds have become the work.

  3. You're operating across multiple service areas and the dispatcher cost is scaling linearly with volume.

Tech stack

  • TypeScript
  • PostGIS
  • OR-Tools
  • OSRM
  • BullMQ

Want this for your team?

30 minutes with a founder or senior engineer. We'll scope what you need and tell you straight whether Stacklane fits.

Book a Free Call