Honua
// honua · cloud-native, open-core

Spatial infrastructure,
evolved for cloud and AI.

Broadly compatible by design./Low-risk migration by automation.

Honua is a modern, cloud-native, open-core geoplatform — predictable in cost, simpler to operate, fast at scale, and ready for agents.

Move legacy GIS services to modern cloud infrastructure without a risky cutover. Keep the maps, apps, and data your teams rely on while reducing infrastructure, operations, and licensing overhead. Give developers, analysts, and field teams faster spatial services through the tools, APIs, and workflows they already use.

Talk to us $ docker compose up ↗ → docs · github · terraform
~/honua-migration · zsh
# 1. Scan an ArcGIS portal for hosted content.
$ honua-migrate content scan \
--portal https://gis.example.gov/portal
✓ scanned FeatureServer · MapServer · ImageServer
✓ webmaps, hosted layers, and portal items catalogued
ℹ dry run · use `content export` + `content import` to migrate
 
# 2. Convert ArcGIS JS apps with the SDK codemod.
$ honua-migrate codemod ./webmap-app \
--target honua-compat --write --report parity.json
analyzing source files...
✓ rewrote ArcGIS JS imports → @honua/sdk-esri-compat
✓ rewrote FeatureLayer / MapView / Query constructors
✓ rewrote reactiveUtils.watch accessors and event names
~ remaining call sites annotated TODO(honua-migrate)
 
# 3. Validate parity gates, then ship side-by-side.
$ honua-migrate fixtures --report parity.json
no-manual-todos · no-unhandled-modules · no-blocking-flags
$ _
// compatibility surface

If your stack speaks it, Honua speaks it back.

Three compatibility surfaces — GeoServices REST for the Esri-compatible clients already in production, open standards for everything in between, and SDKs with parity for the apps your team builds.

GeoServices REST · Esri-compatible

Honua Server speaks GeoServices REST as a first-class protocol, hosted on open infrastructure. Covered Esri-compatible clients can point at a Honua endpoint for the scoped wire protocols and response shapes in the parity matrix; see the parity matrix for current coverage.

FeatureServer✓
MapServer✓
ImageServer✓
GPServer✓
Geometry Service✓
Open standards & protocols

OGC services, the Cloud-Native Geospatial format set, and open agent protocols. Anything that speaks them, Honua speaks back. CITE-evidence wording rules govern conformance numbers in writing.

OGC API · Features, Tiles, Coverages, Maps, Records, Processes✓
Legacy OGC · WFS, WMS, WMTS, WCS✓
gRPC services✓
OData✓
PMTiles · GeoParquet · COG · FlatGeobuf · STAC · Zarr✓
Files · Shapefile, GeoPackage, KML, GML, GeoJSON, FileGDB✓
Agent protocols · MCP✓
SDKs · parity by design

Each Honua SDK is shaped around familiar GIS workflows — a compatibility-by-design surface, not a fork. Convert supported app surfaces with the honua convert codemod and keep review markers where automation cannot prove parity.

JavaScript SDK✓
Python SDK✓
.NET SDK✓
iOS + Android SDKs✓
// the platform

How Honua is built.

Compatibility is how you adopt Honua. The other six are why you keep it.

01 Compatibility Esri-compatible service surface, OGC standards, and SDKs that match the ones your team already builds against. READ 02 Low risk migration Import services. Convert apps with automation. SDK parity means migrations stop being rewrite projects. READ 03 Predictable cost Open-core engine, elastic runtimes, marketplace billing. Pay for the work, not the peak — with no surprise licensing. READ 04 Cloud-native Container-first deployment, serverless functions, and elastic scalability. Built from cloud primitives, not retrofitted onto them. READ 05 Simple operations Terraform, OpenTelemetry, and GitOps, with an optional AI devops loop — no GIS-admin console required, just the toolchain your platform team already knows. READ 06 High performance Cloud-optimized formats, columnar reads, and edge-cacheable tiles. Fast at any zoom — without hand-tuning a server pool. READ 07 AI-ready Your whole GIS workflow with AI assistance — spatial analysis, map and report making, and DevOps. Same audit log as the rest of the platform. READ + Walkthrough with your stack We'll point Honua at your ArcGIS / GeoServer setup and ship a pilot-scoped migration plan in two weeks. BOOK A CALL →
// adoption model

Run old and new together.

01 · IMPORT
Import.
Pull existing ArcGIS, GeoServer, file, and database-backed services into Honua. Schemas, styles, permissions, and service references come along.
02 · CONVERT
Convert.
Run the SDK converter against your ArcGIS JS apps. Imports, FeatureLayer constructors, portal references, and styles rewrite automatically. The hard judgment calls stay flagged for review.
03 · EXPAND
Expand.
Keep legacy clients on the compatibility surface. Move new work to Honua's SDKs, gRPC, MCP, and AI workflows at the team's pace.
// next

Compatible with your stack.
Built for what's next.

Talk to us Browse GitHub
// talk to us

Tell us which workflows need continuity.

Replacing ArcGIS or GeoServer. Moving apps to gRPC. Standing up GitOps for publishing. Any of these is a fine first thread — or skip the form and launch the quickstart.