Drop your build machine.Designed for
Send your configuration and custom models: our infrastructure builds the graph, faster and for less than a cloud machine. Compare with GraphHopper
This way to speed
| Build | Europe | Planet |
|---|---|---|
| GraphHopper | ≈ 1 day | ≈ 3 days |
| RouteBaker | ≈ ½ day | ≈ 1 day |
- 1 car profile with turn costs, contraction hierarchies and elevation
- Loaded as is by an unmodified GraphHopper server
Coming soon
No build machine to manage
No server to size, rent, patch or watch for days: send your config, take back the graph.
Delivered faster
Our high-performance infrastructure builds the planet in under two days, where a GraphHopper import takes more than a week.
Cheaper than the major clouds
Less than renting, for days at a time, a machine large enough for a GraphHopper import at AWS or OVHcloud.
GraphHopper build delivered faster
| Region | GraphHopper | RouteBaker |
|---|---|---|
| Europe · 1 profile | ≈ 1 day | ≈ ½ day |
| Planet · 1 profile | ≈ 3 days | ≈ 1 day |
| Europe · 6 profiles | ≈ 4 days | ≈ ½ day |
| Planet · 6 profiles | ≈ 10 days | ≈ 2 days |
- Compared on our build machines.
Planet, 6 profiles: what a GraphHopper import needs
| Build | Storage | Smallest machine, one CH profile | Build time, 6 profiles |
|---|---|---|---|
| GraphHopper | MMAP | 128 GB | ≈ 10 days |
| GraphHopper | RAM_STORE | 192 GB | ≈ 9 days |
| RouteBaker | — | None to manage | ≈ 2 days |
Cheaper than a cloud build machine
Building it yourself means renting a machine large enough for GraphHopper's import, for days at a time. Two builds a month, per year:
| Build machine | GraphHopper | RouteBaker |
|---|---|---|
| Europe · AWS x2iedn.xlarge · 4 vCPU · 128 GB x2iedn.xlarge · 4 vCPU · 128 GB r7i.2xlarge · 8 vCPU · 64 GB r7i.2xlarge · 8 vCPU · 64 GB | €2,110 / year€8,100 / year€1,250 / year€4,790 / year | Revealed soon |
| Europe · OVHcloud r3-128 · 16 vCPU · 128 GB r3-128 · 16 vCPU · 128 GB r3-64 · 8 vCPU · 64 GB r3-64 · 8 vCPU · 64 GB | €1,210 / year€3,950 / year€600 / year€1,970 / year | Revealed soon |
| Planet · AWS r7i.12xlarge · 48 vCPU · 384 GB r7i.12xlarge · 48 vCPU · 384 GB x2iedn.xlarge · 4 vCPU · 128 GB x2iedn.xlarge · 4 vCPU · 128 GB | €17,320 / year€28,740 / year€5,320 / year€8,100 / year | Revealed soon |
| Planet · OVHcloud r3-512 · 64 vCPU · 512 GB r3-512 · 64 vCPU · 512 GB r3-128 · 16 vCPU · 128 GB r3-128 · 16 vCPU · 128 GB | €11,180 / year€15,770 / year€3,050 / year€3,950 / year | Revealed soon |
- By the hour: an instance for each build, 24 a year. For the year: one instance kept all year, with a 12-month commitment at OVHcloud
- Euros excluding VAT, on-demand prices of 25 September 2026 (AWS Paris, OVHcloud Public Cloud)
- Storage and traffic not included
- Under each row, the machine rented for GraphHopper's import, sized for the storage chosen
From profile to server
Bring your config.yml, take back a graph.
Write your profiles right in RouteBaker
With completion of GraphHopper configurations and profiles.
Start a build
Pick a GraphHopper version and a region: a country, Europe or the planet.
Deploy
Download the graph and switch to it without downtime.
rbake login rbake list <project> rbake download <tag> rbake rollout-server <tag>
Questions
- Will my GraphHopper server load the graph as it is?
- Yes. An unmodified GraphHopper server of the same version loads it and returns the same routes: every graph is checked with GraphHopper before it is delivered.
- Which configurations can it build?
- Car profiles defined by custom models, with turn costs, contraction hierarchies and elevation. Landmarks (LM) and other vehicles are not supported yet; a
config.ymlthat needs them is flagged before the build starts. - Which GraphHopper versions?
- 10.2, 11.0 and 11.1, chosen per project. Newer versions will follow; older ones will not be supported.