Install osrm-backend with Homebrew, Nix

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• osrm-components
• osrm-contract
• osrm-customize
• osrm-datastore
• osrm-extract
• osrm-io-benchmark
• osrm-partition
• osrm-routed

Project history

OSRM began as Dennis Luxen's attempt to bring high-performance academic route-planning algorithms to OpenStreetMap data. Wired reported in November 2013 that Luxen started OSRM around 2010 while working as a PhD candidate at Karlsruhe Institute of Technology, after a discussion with OpenStreetMap contributor Frederik Ramm led him to apply his routing research to OSM.

The OpenStreetMap wiki records the initial public release on July 9, 2010, and an ACM GIS 2011 presentation by Dennis Luxen and Christian Vetter. The same history notes later project phases involving Mapbox's Directions team and a period of slower maintenance after Mapbox shifted routing investment toward Valhalla.

Adoption history

OSRM's adoption came from its speed and self-hostability. The official site advertises continental-sized road networks served within milliseconds, while the README documents a Docker-first quick start for turning an OSM extract into a running HTTP routing server.

The OpenStreetMap wiki lists services and applications powered by OSRM, including FOSSGIS routing, Cycle.travel, Maps.Me, Mapbox Directions components, Geofabrik-hosted routing, and commercial hosted OSRM APIs. That makes osrm-backend one of the most visible OSM packages outside the data-processing niche because it sits directly behind user-facing routing applications.

How it is used

Operators typically download an OSM PBF extract, run `osrm-extract` with a Lua profile such as car, bicycle, or foot, preprocess with the MLD pipeline using `osrm-partition` and `osrm-customize` or the CH pipeline using `osrm-contract`, then run `osrm-routed` to expose the API.

Application developers call OSRM for fastest-route geometry, nearest-road snapping, many-to-many duration or distance tables, noisy GPS trace matching, heuristic trip ordering, and vector tiles containing routing metadata. Profile customization is a key operational feature because it lets a deployment encode vehicle, bicycle, pedestrian, or custom routing rules.

Why package nerds care

osrm-backend is package-nerd catnip because it is both a research-to-production story and a packaging stress test: modern C++, heavy preprocessing, Lua profiles, Docker images, Node bindings, and a public HTTP API wrapped around graph algorithms such as contraction hierarchies and multi-level Dijkstra.

Timeline

• July 9, 2010: Dennis Luxen announced the initial public release on the OSM-dev mailing list. November 2011: Luxen and Christian Vetter presented real-time routing with OpenStreetMap data at ACM GIS. November 2013: Wired profiled OSRM as a self-hostable alternative routing stack. 2015 onward: project leadership and maintenance became more community and Mapbox influenced, with later maintenance transitions documented by the OSM wiki.

Related projects

• The Project-OSRM organization also maintains osrm-frontend for the demo map, osrm-text-instructions for turn instructions, and Docker images for backend deployment. Valhalla is the other major open routing engine named in OSRM's maintenance history.

Sources

• https://formulae.brew.sh/formula/osrm-backend
• https://github.com/Project-OSRM/osrm-backend
• https://project-osrm.org/
• https://project-osrm.org/docs/v5.24.0/api/
• https://wiki.openstreetmap.org/wiki/Open_Source_Routing_Machine
• https://www.wired.com/2013/11/osrm/