GraphHopper vs MapProxy
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
MapProxy
Tile cache and proxy for geospatial web services
| Feature | GraphHopper | MapProxy |
|---|---|---|
| Category | Maps & GIS | Maps & GIS |
| License | Apache-2.0 | Apache-2.0 |
| Language | Java | Python |
| Setup difficulty | Medium | Medium |
| Min. RAM | 4,096 MB | 1,024 MB |
| Deployment | docker, bare-metal, binary | docker, bare-metal |
| GitHub stars | ★ 6,619 | ★ 667 |
| First released | 2012 | 2010 |
| Replaces | Google Directions API | ArcGIS Server |
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 MapProxy if…
- Released under the Apache-2.0 license
- First-class Docker support for quick deployment
- Written in Python
Frequently asked questions
Is GraphHopper or MapProxy better?
Neither is universally better. GraphHopper has the larger community; both share a medium setup difficulty, so the decision comes down to features and licensing.
Are GraphHopper and MapProxy free and open-source?
Yes. GraphHopper is licensed under Apache-2.0 and MapProxy under Apache-2.0. Both can be self-hosted at no software cost.
Can I run GraphHopper and MapProxy with Docker?
GraphHopper: yes. MapProxy: yes.