Hi balena folks - sharing a project I’ve been building and would love feedback on whether this is useful in real balena deployments.
Corviont is a self-hosted/offline maps stack for edge/on-prem setups:
- vector tiles (PMTiles) + MapLibre UI
- offline routing (Valhalla)
- offline geocoding + reverse (SQLite index)
- single gateway (Nginx) on one port
Goal: after the initial images/data are present, it runs fully locally (no external API calls).
Try it:
- Live demo (Vienna)
- Small offline sample pack repo (Monaco, docker-compose)
- Docs (API usage + MapLibre integration)
I also published hardware footprint + p95 latency benchmarks across multiple regions:
Questions for the community:
- Do you ever need maps/routing/search to work fully offline on your devices (field crews, kiosks, gateways, secured sites)?
- If yes - what’s usually the production blocker: data updates, auth/RBAC, custom overlays/POIs, address quality, storage/RAM constraints?
- Would a balenaHub-ready ”Deploy with balena” version be useful, or is docker-compose enough?