Skip to content

OpenMapX

A mapping and mobility platform assembled entirely from open-source services and open data, that anyone can run on their own hardware.

Overview

Most general-purpose map apps make money from advertising. Open alternatives have existed for years in separate pieces: OpenStreetMap for the data, Valhalla for routing, Photon for search. Nobody had put them together into something you would use as your everyday map. OpenMapX does that. It combines search, road and EV routing, live public transport, street-level imagery and weather in one interface. It has no third-party analytics, and the only server you have to trust is your own.

OpenMapX landing page: self-hostable maps, built on open data and open source
The project's landing page.

Manifests in, deployment out

OpenMapX runs twenty-three backend services. Wiring them together by hand would have meant maintaining a huge compose file, so nothing is maintained by hand. Each service describes itself in services/<slug>/service.json, each app feature in integrations/<id>/manifest.json, and the CLI generates the whole Docker Compose deployment from these manifests. Adding a routing engine means adding one file. The same mechanism lets the community publish extensions without forking the project.

In the repository

  • services/<slug>/service.json23 backend containers, one file each
  • integrations/<id>/manifest.json95 app features, one file each

Generated

openmapx renders docker-compose.yml Never edited by hand.

Running

TraefikReverse proxy and TLS, the only open port

  • Web app
    • Next.js 16
    • React 19
    • MapLibre GL
  • API
    • Fastify 5
    • Drizzle
    • Integration host
  • Routing
    • Valhalla
    • OSRM
  • Transit
    • MOTIS
    • OpenTripPlanner
  • Search
    • Photon
    • Pelias
    • Nominatim
  • Tiles
    • TileServer GL
    • Martin

Storage PostgreSQL with PostGIS, Valkey, Elasticsearch

Internal Docker network

Open data in OpenStreetMap, GTFS via Transitous, Wikidata, Mapillary, DWD, NOAA, OpenAQ

Twenty-three services and ninety-five integrations, none of them written into a compose file by hand.

Privacy in the architecture

All containers talk to each other over an internal Docker network. Only Traefik is reachable from outside, unless you deliberately publish another service. OpenMapX never shipped third-party analytics, so there is nothing to switch off. The optional personal timeline runs on your own instance. Self-hosting is the deployment the code was written for, and the public instance is one more copy of the same setup.

Stack and current state

OpenMapX is written in TypeScript throughout. The frontend uses Next.js 16 and MapLibre GL, the backend Fastify 5 with Drizzle, on top of PostgreSQL with PostGIS and Valkey, all in a Turborepo. The application is licensed AGPL-3.0, and the reusable libraries Apache-2.0. The project is still early, and its own banner calls the live deployment experimental. The architecture is settled, and a lot of polishing work is still ahead.