headwaymaps/headway

Self-hostable maps stack, powered by OpenStreetMap.

View on GitHub ↗Jump to charts ↓

headwaymaps/headway has 3k+ stars and 70+ forks on GitHub, is written in Rust, and was last pushed on Oct 15, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 23rd, 2026
Created on November 15th, 2020
Open Issues & Pull Requests: 27 (+0)
GitHub issues: Enabled
Number of forks: 78
Total Stargazers: 3,007 (+0)
Total Subscribers: 15 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1.4 hours
Mean response time: 4.6 hours
90th percentile: 19.7 hours
Tracked items: 5

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 288 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Headway is a self-hostable maps stack that provides mapping, geocoding, and routing capabilities powered by OpenStreetMap data.

The tool addresses the need for organizations and individuals to operate mapping infrastructure independently rather than relying on third-party services. It bundles together a frontend interface, basemap rendering, geocoding for address and point-of-interest search, and a routing engine into a single deployable package. Users can either select from over two hundred predefined city extracts or supply their own OpenStreetMap data covering any geographic area, from a neighborhood to the entire planet. The stack supports multiple travel modes including driving, cycling, and walking, with transit directions under active development.

Headway suits projects requiring self-contained mapping infrastructure with control over data and deployment. It works well for organizations that want to avoid vendor lock-in or need mapping functionality in environments without reliable external API access. The tool is appropriate for medium-sized deployments; a metro-area instance typically requires around four gigabytes of memory to run, though the build process for generating data files demands substantially more resources, with eight gigabytes minimum and potentially more for larger areas. Disk space needs during build can reach fifty to one hundred gigabytes.

The project maintains active development with regular commits and passing automated checks across formatting, linting, and tests enforced through pre-commit hooks. The codebase is written primarily in Rust and accepts community contributions through pull requests for enhancements and bug fixes.