GraphHopper vs Stadia Routing Engine

A side-by-side comparison of two self-hosted maps & gis options — licensing, setup difficulty, resource needs, and what each one replaces.

Not the right match-up?
FeatureGraphHopperStadia Routing Engine
CategoryMaps & GISMaps & GIS
LicenseApache-2.0Apache-2.0
LanguageJavaShell
Setup difficultyMediumHard
Min. RAM4,096 MB4,096 MB
Deploymentdocker, bare-metal, binarydocker, source
GitHub stars★ 6,619★ 318
First released20122019
ReplacesGoogle Directions APIGoogle Directions API, Mapbox Directions

Why pick each one

Choose GraphHopper if…

  • Released under the Apache-2.0 license
  • First-class Docker support for quick deployment
  • Mature project with 6.6k GitHub stars
  • Written in Java
GraphHopper details

Choose Stadia Routing Engine if…

  • Released under the Apache-2.0 license
  • First-class Docker support for quick deployment
  • Written in Shell
Stadia Routing Engine details

Frequently asked questions

Is GraphHopper or Stadia Routing Engine better?

GraphHopper is the stronger all-round pick: it has both the larger community and the simpler medium setup. Consider Stadia Routing Engine if its specific feature set fits your needs better.

Are GraphHopper and Stadia Routing Engine free and open-source?

Yes. GraphHopper is licensed under Apache-2.0 and Stadia Routing Engine under Apache-2.0. Both can be self-hosted at no software cost.

Can I run GraphHopper and Stadia Routing Engine with Docker?

GraphHopper: yes. Stadia Routing Engine: yes.

Related comparisons