Today
Batch planning
One solve before the shift. Changes after that are manual.
Real-time route optimization
Morning plans go stale by eleven. Routite keeps a live model of your vehicles, orders and depots, and re-solves the whole network on GPUs when a van breaks down, orders land late or a road closes.
Try the example dispatch board below
Dispatch board · Zone 4
ExampleExample A toy city of 42 stops solved in your browser with a simple heuristic, so you can see what a re-plan looks like. It is not Routite's GPU solver; every number on this board is illustrative.
Next stops for Van 2
Dispatch log
Clock 10:40
Throw a disruption
Stop 01 · Targets
Routite is pre-launch. These are targets and assumptions we will measure in pilots, not results.
To re-solve a regional fleet of about 1,000 stops after a disruption, warm-started on one GPU.
Default re-solve cadence when nothing has gone wrong, so ETAs stay honest.
Every executed change waits for a dispatcher unless you set a rule that it may go through.
The first number a pilot reports: distance per delivered stop against your own plan.
Stop 02 · Problem
Most fleets plan once, overnight, on CPUs. Routes, dispatch and slotting come out of a batch job and are fixed before the first van leaves the depot.
Then the day starts. Traffic builds, a customer adds forty cases, a van will not start, a bridge closes. By mid-morning the plan is wrong, and re-solving a vehicle routing problem of that size on a CPU takes too long to help.
So dispatchers patch the plan by phone and spreadsheet, and the waste shows up as empty kilometres, missed delivery windows, overtime and idle vehicles.
Today
One solve before the shift. Changes after that are manual.
Today
A dispatcher moves stops by hand and hopes the van after it still makes its windows.
With Routite
Each change to the live model triggers a re-solve of the affected routes, with a reason attached.
With Routite
The dispatcher sees what moves and why, approves, and drivers get the new stop list.
Stop 03 · The loop
Twin senses, Optimize re-solves, Copilot explains, Edge executes. Warehouse and API use the same engine.
Return leg Edge sends real arrival and service times back to Twin. ETA and demand models retrain on them, so tomorrow's first plan starts closer to reality.
Stop 04 · How it works
A telematics feed reports a breakdown, an order arrives, or a traffic service closes a road. Twin updates the live model.
Forecast services estimate which stops will now miss their windows and by how much. Small slips wait for the next cadence; big ones trigger a re-solve now.
Optimize warm-starts NVIDIA cuOpt from the current plan and re-solves routing and dispatch with every constraint you have encoded.
Copilot shows what moved and why: “Van 3 down, 11 stops moved to vans 1 and 4, two windows widened by 10 minutes.” Approve, edit or reject.
Edge pushes the new stop order to driver apps and logs real arrival times for the return leg.
Stop 05 · Who it's for
Last mile
Hundreds of stops per depot, tight windows, late orders all day.
Distribution
Multi-drop trucks, dock schedules, several clients sharing a network.
Field service
Jobs with skills, parts and appointment slots that slip.
Grocery
Temperature zones, short windows and same-day substitutions.
Retail
Peak weeks that double volume with no extra planners.
Planning
Slotting, labour and depot questions that use the same solver.
Stop 06 · Stack
Stop 07 · Developers
Everything the console does goes through the same API. Send the change, get back the new routes, the diff against the current plan and the reasons.
The API is in design. The request below shows the shape we are building toward; see Routite API for the draft.
curl -X POST https://api.routite.com/v1/plans/pl_zone4/resolve \ -H "Authorization: Bearer $ROUTITE_KEY" \ -d '{ "event": { "type": "vehicle_down", "vehicle": "van-3" }, "keep": ["time_windows", "driver_hours"], "approve": "dispatcher" }' # returns: new routes, moved stops, reasons
Stop 08 · Questions
No. Routite is pre-launch. We are looking for design partners to replay their own historical days through the solver before anything touches live dispatch.
No. Routite sits beside your TMS or WMS: it reads orders and constraints from it and writes approved routes back.
Vehicle routing is NP-hard. NVIDIA cuOpt runs many candidate improvements in parallel on a GPU, which is what makes re-solving a whole region during the day practical rather than overnight.
Not unless you say so. By default every executed change waits for a dispatcher. You can allow narrow rules, such as swaps inside one van's route.
One or more past days of orders, vehicles, depots and what actually happened. See the pilot page for the full list.
Stop 09 · Destination
Next step
We replay one of your past days through Routite: the plan you had, the disruptions that hit it, and what a live re-plan would have done. You keep the report.