Routing that costs a fraction of the price, runs on your own servers, and that you can prove, line for line. Same distances as the big maps, updated the moment a road changes.
A captured side-by-side, measured June 2026. Each Elara figure is from our engine; each Google figure was read off Google Maps for the same route on that day.
| Route | Elara distance | Elara ETA | Google distance | Difference |
|---|---|---|---|---|
| Johannesburg · Sandton → Soweto | 37.6 km | 55.9 min | 37.5 km | 0.3% |
| Midrand → Sandton | 15.94 km | 21.3 min | 16.1 km | 1.0% |
| Tokyo · Shibuya → Tokyo Station | 7.44 km | 7.7 min | 7.4 km | 0.5% |
Eight reasons teams move their route calls off metered map APIs, same distances, far more control.
| What matters | Elara Route | Metered map APIs |
|---|---|---|
| Cost at fleet or matrix scale | ~$0 per route, you host it | Metered per call and per matrix element |
| Run offline / air-gapped | Yes, on your own network | No, cloud only |
| Your location data stays in-house | Yes, nothing leaves your network | No, every query leaves your network |
| Same route every time (auditable) | Yes, deterministic, inspectable | No, live black box |
| Store and reuse routes freely | Yes, no caching limits | Restricted by terms |
| Custom rules (truck, drone, mine) | Yes, your own cost layers | Limited or none |
| Instant reroute when a road changes | 302× faster, 97% of changes need no recalculation | Re-asks from scratch every time |
| Distance accuracy | Level with the big maps (0.3–1.0%) | Level |