Offline maps for field deployments
Corviont is a self-hosted local mapping service for utility, municipal, and other field deployments where connectivity is weak or everything needs to run on-prem.
Corviont is a self-hosted local mapping service for utility, municipal, and other field deployments where connectivity is weak or everything needs to run on-prem.
When a field workflow needs local maps, search, and routing, the hard part is not getting a map on screen. It is packaging the data, exposing a clean local interface, fitting it onto target hardware, and reusing that setup across deployments.
Corviont packages that into one self-hosted service your app can call locally.
Maps, routing, and search behind one local interface.
Self-contained regional packs for amd64 and arm64 edge/on-prem targets.
After setup, tiles, routing, and geocoding are served locally.
Use the same mapping subsystem across customer deployments instead of rebuilding the mapping layer case by case.
Corviont fits products and deployments where maps are part of the workflow, but not the subsystem your team wants to build and maintain.
Dispatch, inspections, maintenance, public works, and outage workflows where crews need local maps, address search, and routing.
Private networks, regulated customer sites, vessels, gateways, and other low-connectivity deployments where relying on external APIs is awkward or unacceptable.
A reusable local mapping subsystem for teams that do not want to rebuild the mapping layer for each project.
Corviont is packaged in regional tiers with published RAM, download-size, and on-disk benchmarks so you can estimate footprint before rollout.
Each tier includes example regions so you can choose the closest fit before deployment.
CityVienna, Berlin, DC
|
StateAustria, Bavaria, Colorado, Texas
|
LargeSpain, Poland, UK, California
|
ComplexGermany, Western US
|
|
|
RAM usage
p95 of Corviont containers, OS overhead not included
|
200 MB
|
500 MB
|
1.5 GB
|
3 GB
|
|
Download size
Tiles + routing + search, does not include container images (0.5 GB)
|
200 MB
|
2 GB
|
4.5 GB
|
8.5 GB
|
|
On-disk data
Tiles + routing + search, does not include container images (1.5 GB)
|
300 MB
|
3 GB
|
7 GB
|
13 GB
|
CityVienna, Berlin, DC
|
|
RAM usage
p95 of Corviont containers, OS overhead not included
200 MB
|
|
Download size
Tiles + routing + search, does not include container images (0.5 GB)
200 MB
|
|
On-disk data
Tiles + routing + search, does not include container images (1.5 GB)
300 MB
|
StateAustria, Bavaria, Colorado, Texas
|
|
RAM usage
p95 of Corviont containers, OS overhead not included
500 MB
|
|
Download size
Tiles + routing + search, does not include container images (0.5 GB)
2 GB
|
|
On-disk data
Tiles + routing + search, does not include container images (1.5 GB)
3 GB
|
LargeSpain, Poland, UK, California
|
|
RAM usage
p95 of Corviont containers, OS overhead not included
1.5 GB
|
|
Download size
Tiles + routing + search, does not include container images (0.5 GB)
4.5 GB
|
|
On-disk data
Tiles + routing + search, does not include container images (1.5 GB)
7 GB
|
ComplexGermany, Western US
|
|
RAM usage
p95 of Corviont containers, OS overhead not included
3 GB
|
|
Download size
Tiles + routing + search, does not include container images (0.5 GB)
8.5 GB
|
|
On-disk data
Tiles + routing + search, does not include container images (1.5 GB)
13 GB
|
A pilot means Corviont running on your region and constraints. After you submit, you-ll also receive a Vienna eval pack link by email so you can test the full offline setup on your own hardware while we scope the pilot.
The form has been successfully submitted.
