RobustRoute
One platform · Two products

It designs your zones 6 ways, then shows you why it picked one.

RobustRoute plans balanced delivery zones and real-road routes for distribution and field teams. It evaluates a batch of designs, scores them against your constraints, and recommends one — and writes nothing until you apply it.

Start freeSee a real run
6
designs evaluated
1
parallel batch
0
written without you
The run

One request. A batch of candidates. A recommendation you can audit.

This is a real run against the Riyadh demo dataset — 50 stops, captured 2026-08-03. Same three views of it: what was considered, what the planner said, and how it scored.

Run · Riyadh · 50 customers · read-only

6 designs · one parallel batch

RECOMMENDEDPolar sectors · 4 zonesbalance 0.856 · 1.20× mean

· awaiting apply · nothing written

Candidate zone designs evaluated in one batch, ranked by balance score, each checked against the fairness ceiling of 2.00×
#MethodBalance scoreLargest ÷ mean (≤ 2.00×)Verdict
01Polar sectors4 zones · 15 · 13 · 12 · 10
0.856
1.20× passes the fairness ceilingADOPTED
02Constrained clustering6 zones · 11 · 9 · 9 · 7 · 7 · 7
0.821
1.32× passes the fairness ceilingREJECTED
03Constrained clustering4 zones · 15 · 14 · 13 · 8
0.785
1.20× passes the fairness ceilingREJECTED
04Polar sectors6 zones · 11 · 10 · 9 · 8 · 6 · 6
0.774
1.32× passes the fairness ceilingREJECTED
05Polar sectors8 zones · 9 · 8 · 7 · 6 · 6 · 5 · 5 · 4
0.750
1.44× passes the fairness ceilingREJECTED
06Constrained clustering8 zones · 9 · 7 · 7 · 7 · 6 · 6 · 5 · 3
0.738
1.44× passes the fairness ceilingREJECTED
Polar sectors at 4 zonesADOPTED

Rank 01 · Polar sectors

Tightest spread in the batch — 15 down to 10, and every zone clears the ceiling.

Fairness ceiling: the largest zone may not exceed 2.00× the mean. Every candidate above clears it — ranks 02–06 are rejected on balance score alone. Real run, Riyadh, 50 stops, captured 2026-08-03. The record is kept with the run.

Six ways to cut a zone

Different operations need different shapes.

Each method produces a characteristic geometry. The planner picks between them on your data — you are not committing to one at the start.

  • Constrained clustering — schematic geometryBALANCED

    Constrained clustering

    Natural groupings, balanced by workload.

  • Polar sectors — schematic geometryANCHORED

    Polar sectors

    Wedges anchored on a depot.

  • Isochrone bands — schematic geometryDRIVE TIME

    Isochrone bands

    Cut by drive time, not distance.

  • Balanced grid — schematic geometryPCA-ALIGNED

    Balanced grid

    Rotated rectangles aligned to the data.

  • Manual polygons — schematic geometryHAND-DRAWN

    Manual polygons

    Draw the boundary yourself.

  • Fixed ERP format — schematic geometryFIXED FORMAT

    Fixed ERP format

    Uniform cells where a downstream system demands them.

In the product

Zones, routes and the co-pilot on one screen.

Command Center after a full run on the Riyadh demo file: three zones, one route per zone with the stop order numbered, and the scope fixed at ingest. The panel on the right is the co-pilot mid-conversation — it asks which zone to isolate and offers the choices rather than deciding for you.

The RobustRoute Command Center. A map of Riyadh carries three delivery routes in blue, red and green, each stop numbered in visit order. Above the map, scope filters show the city fixed to Riyadh. A side panel tracks the run — fifty customers, three zones, dispatch phase four of four, exports ready — and below it the co-pilot asks which zone to isolate, offering the three zone names as choices.
Command Center · 50 stops · 3 zones · dispatch phase 4 of 4 · exports ready
Why you can trust the pick

Every candidate is scored, checked against a ceiling, and kept on the record.

Scored, not guessed

Balance score is computed from the actual spread of stops per zone — for the adopted design, 15 · 13 · 12 · 10.

A ceiling, not a preference

The largest zone may not exceed 2.00× the mean. A design that breaches it is rejected regardless of how well it scores.

The record is kept

Every candidate, its score, its constraint check and the reason it lost stay attached to the run.

How RobustRoute fits together

Plan the territory. Dispatch the day.

Co-equal products, one customer dataset. Use either on its own, or run both against the same data — no forced bundle, no extra integration step.

RobustRoute Command CenterStrategic planning

Command Center

Build balanced delivery zones and save real-road route plans you dispatch from week after week.

  • AI-assisted zoning
  • Real-road routing
  • Versioned plans
Explore Command Center See pricing
RobustRoute Last Mile DeliveryDaily operations

Last Mile Delivery

Drop today's orders, set your drivers, get optimized routes in seconds.

  • Stops-based pricing
  • Per-agent caps
  • Full dispatch history
Explore Last Mile See pricing
Control

It proposes. You apply.

A run reads your data and produces a recommendation. Nothing is written to your zones, routes or agents until you press apply — so exploring a different shape costs you nothing but the time to look at it.

· awaiting apply · nothing written

Run it on your own data.

Upload a customer file and see the batch it produces. Start on the free tier — no card.

Start freeSee pricing