Your activity. Your rules. Your route.
The engine changes with the sport, and so does everything it optimises for.
Not one router with a label swapped on top. A hiking engine that looks for paths and reads SAC grades has nothing in common with a skating engine whose whole job is to keep you on smooth tarmac — so they are not the same engine.
Each of these has its own page: what the engine is tuned for, the presets it actually ships with, and what is worth checking before you leave.
A tempo session wants even ground and no junctions. A long trail run wants the opposite of that. Same planner, different instruction.
You will take a T5. The friend you walk with stops at T3. Tell the engine which of you is planning, and the route is different — not the same line with a warning on it.
Flowing itineraries on sealed roads, with the gradient of every ramp on the line readable before you turn the pedals.
Trails, tracks and descents. Read how hard the ground gets and where the climbing is stacked, and take the GPX with you for the part where there is no signal.
More gravel, white roads and farm tracks — or less of them, on the day the legs are not there. The surface is the setting, not the surprise.
The narrowest engine on the planner, and deliberately so: gravel, steps and broken tarmac are not a compromise here, they are the end of the session.
Some outings are not one sport, and one sport cannot be routed at all. Both still belong here.
Planned on the road or gravel engine, then held together as a multi-day story with one set of totals.
Several tracks in one post — including the swim, which no router can draw and which is recorded rather than planned.
The engine changes with the sport, and so does everything it optimises for.