How Outrouted works
What Outrouted's trip data comes from
Every map and every number on this site comes from somewhere. This page names the sources category by category, so you can judge how grounded an answer is instead of taking it on trust.
Updated 24 Aug 2026about 4 minutes
On this page
1.Maps and terrain
One tile server and two maps the site draws itself, for three jobs. All of them are open and keyless, which is why the maps need no account, no tag and no permission from anybody to draw.
| What | Source |
|---|---|
| The map inside the product | OpenStreetMap data, served as vector tiles by OpenFreeMap |
| The route maps on pages like this one | Natural Earth outlines and terrain, drawn by the site itself as vector graphics, with no tile server |
| The globe and world map behind the home page | Natural Earth country outlines, drawn by the site itself with no tile server at all |
2.Places, cities and coordinates
Hand-picked destinations, their highlights and their hotels are Outrouted's own catalogue. Countries, cities and airports outside that set are generated from open geographic data, which is what makes anywhere in the world plannable, not just the places somebody has written up.
Turning typed text into coordinates goes through LocationIQ, Geoapify and geocode.maps.co, tried in order until one answers. A highlight's position is hand-checked where it matters and geocoded otherwise, and a geocoded hit is only kept if it lands inside the destination's own country and within ninety miles of it. A place that survives neither check has no position, and Outrouted draws nothing rather than a pin in the wrong country.
3.Accommodation
Nuitee's liteAPI supplies hotel search prices on the Stay tab when it answers for your dates and party. The result shows its age and tax basis. A failed check says nothing about room availability. The budget keeps a separate lodging estimate based on a share of the country's daily rate, or a fallback allowance. You book elsewhere.
4.Flights
Flight searches try Nuitee first, then SerpApi's Google Flights results. They need dates and airport codes. These results inform planning; no provider flight fare is currently displayed. Flight costs in the budget are estimated from distance and estimated connections.
Flights are priced here, not sold.
5.Exchange rates
European Central Bank reference rates, fetched through Frankfurter. When that is unreachable a pinned table is used instead, and it is indicative, not a rate anybody trades at.
6.Weather
Long-run monthly normals for each stop's own coordinates, from NASA POWER where the archive answers and from a pinned indicative table where it does not: typical highs and lows, wet days, daylight hours. Each stop is read for the month it falls in, which is not always the month you leave home. Not a forecast, and deliberately not one. Somebody planning six months out wants to know whether to bring a coat, and a ten-day forecast cannot tell them.
7.Photography
Destination photographs come from Pexels, and from Openverse under open licences where Pexels has no good match, with the licence shown beside the picture. The photographs on the landing page's own map are held in this repository rather than hot-linked, so the first screen anybody sees does not depend on somebody else being up. Their credits are on the about page.
8.The language model
A hosted language model proposes places, order and nights per stop. It receives trip inputs and the candidate pool, with no account identifiers. Code checks the total nights and calculates dates, distances, travel estimates and costs. The model also writes guarded explanations; it does not supply prices or budget totals.
9.When a provider changes
Every provider above sits behind an interface, so swapping one is a configuration change, not a rewrite. The health endpoint reports which arrangement is actually running, and this page is updated when one changes.
None of them is told which page you are on, and none of them is paid for placement in a result.