AI-ready geospatial platform

One geospatial foundation for AI tools, fast apps, and cloud operations.

Honua replaces aging GIS infrastructure with one runtime that keeps your current clients working, gives developers a fast gRPC API to build on, lets AI agents query spatial data directly, and deploys like the rest of your cloud. No separate products. No seat fees.

Launch the Quickstart See the Modernization Path Explore the Platform

ArcGIS and GeoServer compatible Native gRPC transport OGC conformance published Open core with no seat fees

Query Features

Give agents a safe way to discover layers, inspect schemas, and run spatial queries.

curl "http://localhost:8080/ogcapi/collections/parcels/items?
  limit=50&
  bbox=-122.42,37.77,-122.40,37.79&
  f=json"

Operational Proof

137/137 OGC API Features tests passing.

gRPC Typed Protobuf contracts for app traffic.

OTel Traces ready for your existing dashboards.

SDK

from honua_sdk import HonuaClient

with HonuaClient("https://gis.example.com") as c:
    parcels = c.query_features(
        "parcels", where="status='active'"
    )
    print(f"{len(parcels)} features")

What Changes

What modern geospatial teams need from the platform layer.

Most GIS stacks force teams to choose between compatibility, performance, and operational simplicity. Honua brings those requirements together in one runtime.

AI Agents

Let assistants work with spatial context directly.

Honua exposes collections, schemas, filters, and topology tools through an MCP-based agent interface so automation can access maps and spatial rules without scraping ad hoc REST endpoints.

See AI agents

Application Runtime

Move high-volume traffic onto typed, binary contracts.

New apps can use gRPC and SDKs for lower overhead, clearer contracts, and faster integration while legacy GIS clients keep using the interfaces they already know.

See the runtime

Operations

Run GIS with version control, rollout discipline, and traces.

Publish services from manifests, review changes in Git, and trace requests through the runtime and into PostGIS using the same operational tools you already trust.

See DevOps workflows

The Bridge

Keep your current clients working. Change the foundation underneath them.

You do not need a clean-room rewrite to modernize your GIS stack. Honua keeps ArcGIS, QGIS, and other standards-based clients connected while you move new work onto faster interfaces and more reliable operational patterns.

Day One

Import services and preserve the client surface your teams depend on.

Keep ArcGIS Pro, existing web maps, and GeoServer-facing clients online through GeoServices REST, WFS, WMS, WMTS, OGC API, and raster services while you validate output and performance on the new runtime.

After Cutover

Move new work to better tooling when your team is ready.

Ship new applications with gRPC and SDKs, expose governed spatial tools to AI agents, and manage publication and rollout with Git-backed changes instead of manual admin steps.

Compatibility buys you time. The real value is what your team ships once the pressure of a forced rewrite is off the table.

Comparison

See where Honua fits against the stacks teams usually stitch together.

Capability	Honua	ArcGIS	GeoServer	Mapbox / Carto
Primary app protocol	Binary gRPC plus standards and compatibility APIs	REST and JSON	WFS / WMS and REST add-ons	REST and tile APIs
AI-ready tool access	Native AI agent tooling	No native AI agent layer	No native AI agent layer	API access only
Operations model	Git-friendly rollout, OTel traces, serverless or containers	Manual and scripted administration	Manual configuration and JVM operations	SaaS-first controls
Licensing model	Open core, no seat pricing	Seat and extension pricing	Open source with heavier ops burden	Usage and seat pricing
Modernization path	Service importers, migration automation, parity checks	Not applicable	Mostly manual migration	Mostly manual migration

Who Uses Honua

Different teams start from different problems.

GIS Teams

Keep ArcGIS Pro and QGIS working while the backend modernizes.

Service importers bring your existing services into the new runtime so you can validate before anything changes for users.

See the modernization path

Application Teams

Build on typed contracts instead of scraping REST endpoints.

Use gRPC and language SDKs for new services, mobile sync, and internal integrations with clearer contracts and lower overhead.

See the runtime

Platform Engineers

Deploy GIS through the same CI/CD and observability stack as everything else.

Publish from manifests, trace requests with OpenTelemetry, and run containers or serverless without inventing a separate operational model.

See GitOps + OTel

Build Paths

Start with the part your team needs now.

Launch the runtime locally

Bring up Honua in Docker, make a request, and inspect the runtime behavior yourself.

Open the quickstart

Pick an SDK

Choose JavaScript, .NET, or Python for applications, automation, and field workflows.

View SDKs

Review the standards work

See the conformance evidence and the open submission path for the gRPC work.

View OGC submission

Request an Assessment

Tell us what needs to keep working and what you want to improve.

We can help scope ArcGIS and GeoServer migration, application cutover, rollout sequencing, and where gRPC, AI agent tooling, or GitOps workflows fit into the move.

If you prefer to start hands-on, use the quickstart first and come back when you have concrete questions.

ArcGIS and GeoServer replacement Application migration automation AI and automation workflows Deployment and rollout planning