quick answers
Frequently asked questions.
Short answers to the questions we get most. When an answer has a longer story behind it, the link goes to the engineering deep dive.
- Do I need an account?
- No. There is nothing to sign up for and nothing to log into. Your saved trips, moods, and settings live on your device, not on our servers.
- Does it work offline?
- Yes. You can download map regions to your device and switch the app to its local engine; route planning and place search then run entirely in your browser with no network at all. It is the same routing code the server runs, compiled for your device.
- What data do you collect about me?
- None that we can help. The public routing server is stateless and configured to log nothing, with no accounts and no request history. Trips you save stay on your device. The deeper answer, including the parts enforced in code rather than by policy, is in Private by architecture.
- Where does the map data come from?
- From OpenStreetMap, the free volunteer-built map of the world, plus public elevation data. We process it ourselves into the scored road graph the router uses. The whole pipeline is described in the bake, and the freshness of what is currently live is public on the build report.
- What areas are covered?
- The contiguous United States plus Hawaii. Routes work across state lines within that area; one-shot plans are capped at about a long day's drive. The build report shows exactly what is on the public mirror right now.
- Why doesn't it know about traffic?
- Because a live-traffic query tells the provider where you are and when, and we decided that trade was not ours to make for you. Instead there is an optional field where you type the ETA your usual maps app is already showing; the time budget anchors to it. The reasoning is in the architecture article.
- Why is my route different from Google's?
- Partly on purpose: astray optimizes for the best drive inside your time budget rather than the quickest arrival, and a different objective gives a different route. Partly as a side effect: without live traffic, our travel times assume free-flowing roads, so our "fastest" can differ from a traffic-aware one. How a time budget becomes a route has the full story.
- Can it plan a drive that ends back at home?
- Yes. Set the start and end to the same place and it plans a loop: you say how long the tour should be, and it goes out on one road and back on another. Loops are genuinely harder than regular trips; the loop problem explains why.
- What exactly is a "mood"?
- A named set of preferences (more coastline, fewer stoplights, nothing you have driven recently) that the router turns into arithmetic. You can use the shipped ones (Balanced, Coast & water, Peaks & passes, Back roads, Cruise, Gentle), tweak them, or build your own with the equalizer.
- Why did my scenic route include a boring stretch?
- Usually because that stretch was the connector: an unavoidable bridge or valley crossing costs its travel time and nothing more, so the router crosses it quickly and spends your budget where the map offers something better. And on some corridors there is genuinely no worthwhile detour, in which case the engine returns a smaller one rather than inventing a pointless drive. See the routing engine.
- What happens to my saved trips if I clear my browser data?
- They are gone. That is the honest cost of keeping everything on your device instead of on our servers. The app includes a backup export so you can save your trips and moods to a file first and restore them later.
Curious past the short answers? Start with the engineering story, a few minutes of reading with deep dives into every corner.