I’m building Corviont, a self-hosted offline maps appliance (tiles + routing + search) for edge/on-prem devices.
Hosted demo (no install): https://demo.corviont.com/
Self-host (Docker Compose repo): https://github.com/corviont/monaco-demo
Docs: https://www.corviont.com/docs
What’s inside:
- Vector tiles served locally (PMTiles)
- Routing served locally (Valhalla)
- Offline geocoding/search + reverse (SQLite Nominatim-based index)
- MapLibre UI wired to the local endpoints
Next (if people need it): a signed on-device updater for regional datasets (verify → atomic swap → reload).
I’d love feedback: where offline maps/routing/search matters for you, and what constraints bite (hardware, fleet size, update windows, regions, deployment style).
packet_mover•1mo ago
A key goal is consistency: tiles, routing data, and the geocoder index are built from the same extract/version for a region.
If you’ve seen Atlas/SDK approaches: this is intentionally smaller and “appliance-like” (PMTiles + Valhalla + SQLite geocoder) to be friendlier to edge hardware and simple ops.