A Routing Engine on Our Own Servers
Route calculation with per-activity cost models and no external dependency.
Overview
Tying route calculation to a third-party service meant both a per-request cost and a loss of control. We stood Valhalla up on our own servers.
The challenge
A hiker's route cannot be the same as a mountain biker's. Off-the-shelf services are usually limited to two modes: driving and walking.
The solution
We installed Valhalla with Docker and defined a separate cost profile for every activity type. The engine's state is watched through a health endpoint; if it stops responding, the app falls back to a degraded mode. The data source is OpenStreetMap, and the attribution requirement is met in the interface.
Results
- No third-party cost per request
- Activity-specific routing profiles
- An engine observable through a health endpoint
- A controlled import pipeline for OSM data
Shall we turn your idea
into a real product?
Let's write the scope together and give you a day-by-day schedule. The first call is free; we reply within one business day.
Written scope · Fixed price · You own the source code