• Route planner
  • My activities
  • Blog
  • FAQ
Instagram Buy me a coffee
Connect with Strava
All posts

Building a cycling route planner for the whole planet

12 November 2026

Also available in: Deutsch · Français · Nederlands

RouteCycle started as a one-day hack and slowly turned into a route planner that works on every road in the world. This is the story of how that happened, and of the parts nobody sees: the data, the servers, and doing it without a company behind it.

A prototype in one day

The first version came together in summer 2022, in a single day. It found attractions in OpenStreetMap and linked them together into a route through a third-party routing API. It was very basic, but it worked, and that was exciting. For the first time I could say "give me a ride past interesting things" and get something back.

Then life happened: moving to another country, a new job, a new language. The project sat untouched for almost two years.

Coming back, and quitting

In summer 2024 I came back to it, and this time it stuck. In July 2024 I quit my job as a software engineer. It was a well-paid job, but I had come to really dislike corporate work, and I had some savings to live on for a while. I wanted to see if I could build something useful on my own.

In spring 2025 I showed the project to a local community for the first time. I got feedback, some followers, and the first donations: 115 €. A small part came from people I knew, and the rest from people I'd never met.

I'd never felt anything like it. It felt better than any salary I'd had. Strangers paying a little because they liked something I made was a completely new feeling, and a lot of motivation.

Why a route planner needs so much data

From the outside, a route planner looks like a map and a button. Underneath, it needs the whole road network of the planet, prepared in a form that can be searched in seconds.

The raw data is OpenStreetMap: every road, path and track in the world, with all its tags. On top of that comes elevation for every point, estimates of traffic and surface where the map doesn't say, sights, water points, and a lot of custom processing so loops can be built quickly.

Preparing all of that is the expensive part. At some point a full preparation run needed something like 256 to 512 GB of memory. With enough memory a run took about 10 hours. On my own machine, with 64 GB of RAM and a big SSD as swap, the same run dragged on for about a week of painful swapping. Every time I wanted to update the data, I either waited a week or rented a big server for a day, and those costs add up quickly for a free project.

I even asked on r/homelab whether anyone had a spare high-memory machine to lend for a few hours. It felt like a strange thing to ask, but at the time I didn't have a better solution.

Running it every day

After the data is ready, the planner itself has to run somewhere. Every route you generate is real work: building a loop means many route searches, checking and scoring each candidate, and choosing the best few. I wrote more about that in why loops are harder than A-to-B routing. Doing that for the whole planet, for anyone who opens the site, takes real servers.

Hosting is the main cost of the project. RouteCycle is free to use, and donations and supporters on Buy Me a Coffee help keep the servers running.

Where it is now

Since that one-day prototype, a lot has been added:

  • loops or A-to-B routes on quiet roads, anywhere in the world,
  • road and gravel modes,
  • sights, springs and cafes, and up to five stops of your own,
  • planning by ride time, with a cap on climbing,
  • exploring roads and sights that are new to you,
  • one-click sending to Garmin Connect,
  • an iOS app.

And a lot is still ahead. The one I care about most is long trips: building a multi-day route of thousands of kilometres with places to sleep on the way, in one click.

Doing it without a boss

The best part of building something alone is that you decide what matters. The hardest part is the same thing. Nobody else does the marketing, the support, the servers or the bug reports. I'm a very technical person, and things like marketing are completely new to me. I'm learning as I go.

What keeps me going is the feedback. Every report about a bad road, every "this found me a road I never knew about" message, makes the project better.

If you ride, try it: open RouteCycle, pick a start and a distance, and tell me what you think.

Read next

  • How do you know a road is quiet? Where cycling traffic data comes from
  • Why generating a loop is much harder than routing from A to B
  • Why some roads look wrong on the map, and how you can fix them

Want a quiet ride from your door? Pick a start and a distance, and RouteCycle builds the loop.

Open the route planner
FAQBlogRoutesTerms & ConditionsPrivacy Policy