GraphHopper vs Overpass API
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
Overpass API
Read-only query API for OpenStreetMap data
| Feature | GraphHopper | Overpass API |
|---|---|---|
| Category | Maps & GIS | Maps & GIS |
| License | Apache-2.0 | AGPL-3.0 |
| Language | Java | C++ |
| Setup difficulty | Medium | Hard |
| Min. RAM | 4,096 MB | 2,048 MB |
| Deployment | docker, bare-metal, binary | bare-metal, source |
| GitHub stars | ★ 6,619 | ★ 911 |
| First released | 2012 | 2011 |
| Replaces | Google Directions API | Google Places API |
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
Frequently asked questions
Is GraphHopper or Overpass API better?
GraphHopper is the stronger all-round pick: it has both the larger community and the simpler medium setup. Consider Overpass API if its specific feature set fits your needs better.
Are GraphHopper and Overpass API free and open-source?
Yes. GraphHopper is licensed under Apache-2.0 and Overpass API under AGPL-3.0. Both can be self-hosted at no software cost.
Can I run GraphHopper and Overpass API with Docker?
GraphHopper: yes. Overpass API: check the project docs for container support.