GraphHopper vs Pelias
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?
GraphHopper
Fast and flexible open-source routing engine
VS
Pelias
Modular open-source geocoder powered by Elasticsearch
| Feature | GraphHopper | Pelias |
|---|---|---|
| Category | Maps & GIS | Maps & GIS |
| License | Apache-2.0 | MIT |
| Language | Java | Twig |
| Setup difficulty | Medium | Hard |
| Min. RAM | 4,096 MB | 4,096 MB |
| Deployment | docker, bare-metal, binary | docker, kubernetes |
| GitHub stars | ★ 6,619 | ★ 3,562 |
| First released | 2012 | 2014 |
| Replaces | Google Directions API | Google Geocoding API, Mapbox Geocoding |
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
Choose Pelias if…
- Released under the MIT license
- First-class Docker support for quick deployment
- Kubernetes-ready with Helm charts available
- Active community (3.6k GitHub stars)
Frequently asked questions
Is GraphHopper or Pelias better?
GraphHopper is the stronger all-round pick: it has both the larger community and the simpler medium setup. Consider Pelias if its specific feature set fits your needs better.
Are GraphHopper and Pelias free and open-source?
Yes. GraphHopper is licensed under Apache-2.0 and Pelias under MIT. Both can be self-hosted at no software cost.
Can I run GraphHopper and Pelias with Docker?
GraphHopper: yes. Pelias: yes.