Corviont: Self-hosted offline maps with tiles, routing, and geocoding in Docker.

What it does

Corviont is a self-hosted mapping service that runs locally on edge devices or on-premises infrastructure. It provides three core functions: map tiles for display, routing for navigation, and geocoding for address search. The system is packaged as a Docker container and operates without needing external API calls after initial setup.

Who it is for

The product targets three main groups. Utility and municipal field operations teams need offline maps, address search, and routing for dispatch, inspections, maintenance, and outage workflows where crews operate without reliable connectivity. Organizations in restricted environments—private networks, regulated customer sites, vessels, or low-connectivity gateways—cannot depend on external APIs. Integrators and delivery teams that build field software for multiple customers want to reuse a mapping subsystem instead of rebuilding the cartography layer for each project.

Pricing

The site does not show prices.

How it stands out

Corviont packages maps, routing, and search as a unified local service rather than forcing teams to assemble these components separately. The product ships in regional tiers with published specifications: RAM usage (measured at p95), download size, and on-disk requirements are documented for each tier so teams can estimate deployment footprint before rollout. Examples range from Vienna (200 MB download, 200 MB RAM) to large regions like Spain or California (8.5 GB download, 3 GB RAM). The service is self-contained and requires no external dependencies after deployment, making it suitable for vessels, private networks, and air-gapped sites.

What a founder should check

A founder building a competing offline mapping platform should verify three things. First, examine the switching costs and integration depth: how tightly does Corviont bind into existing field-operations software, and what effort would be required to replace it. Second, assess the data moat: which mapping datasets does Corviont use, how often do they update, and can a rival easily source equivalent tiles, routing graphs, and geocoding data. Third, test pricing pressure in the target verticals—utility and municipal procurement may expect open-source alternatives or negotiated enterprise rates, so model whether Corviont's bundled approach justifies a premium over point solutions or custom integrations.

Thinking of building something like this?

Every launch here is a competitor to somebody's idea. If yours is close, check it against the market before you build: the Full Check names the rivals, the prices and the gaps.