Honua
// pillar 07 · ai-ready

GIS analysis. Map & report making.
DevOps.
All with AI assistance.

Honua treats AI as a workflow primitive, not a bolt-on chatbot. Analysts get spatial analysis from a sentence. Cartographers and app teams build maps, dashboards, and reports by describing them. Platform teams hand operations themselves to an AI DevOps agent. Same audit log, same governance, same MCP plumbing for all three.

Talk to us MCP spec ↗ Honua-GIS evals
mcp://honua.example.govanalysis · english → spatial query● EXAMPLE
USER
How many parcels in the SFHA flood zone, and what's the total acreage?
AGENT · tool_call
honua.spatial.query({
  service: "Parcels",
  intersects: "FloodZones/SFHA",
  aggregate: ["count", "sum(area_acres)"]
})
HONUA · result
{
  count: 1284,
  sum_area_acres: 518.4,
  cited_services: ["Parcels@v8", "FloodZones@v3"]
}
AGENT
1,284 parcels intersect the SFHA flood zone — about 518.4 acres in total. Sources: Parcels v8, FloodZones v3. Want me to draft notification letters or render a map?
// the gis workflow

AI across the whole workflow.

Three jobs that used to need a specialist desktop tool, a developer, or an ops team — each one now AI-assisted on the same governed platform.

01 · GIS analysis Spatial analysis from a sentence.

Analysts ask questions in plain English; Honua's MCP tools turn them into typed spatial workflows — intersects, buffers, network analysis, aggregations — with cited source layers and reproducible query records on every answer. The transcript above is this mode running through an MCP-connected agent.

Analysts · field teamsvia MCP
Cited services + provenancealways
Reproducible query recordsaudit-logged
02 · Map & report making Maps, dashboards, reports — prompted.

Describe the map you need; Honua composes the layers, styles, and layout against your real services. Same for dashboards and PDF / HTML reports — produced from typed services, with the exact source service versions baked into every export so the output is auditable, not just pretty.

Cartographers · app teamsvia SDK + MCP
Layouts, dashboards, reportstyped inputs
Source versions in every exportcited
03 · DevOps Honua operates Honua.

honua-devops is the operations agent that watches your Honua deployment. It triages alerts, files Terraform PRs against your IaC repo, runs migration tools, and walks the GitOps loop — governed by your OIDC roles, never bypassing them.

Platform team · SREvia Terraform + GitOps
Alerts → triage → PRaudit-logged
OIDC-governed, no bypassalways
// surfaces underneath

What all three modes share.

SurfaceWhat it doesUsed by
MCP serverTyped tool definitions for spatial query, render, geocode, route, and write-back. Service discovery built in.Claude, ChatGPT, custom agents.
gRPC serviceStreaming spatial queries, bulk operations, and back-pressure for long-running jobs.Internal services, batch pipelines.
REST + SDKSame surface as ArcGIS JS, plus modern Promise + typed responses for app code.Web apps, mobile, scripting.
Governed write-backAgent writes go through the same OIDC roles and audit log as human edits.Field ops, analysts, agents.
Citations + provenanceEvery response carries the source service, version, and query that produced it.Compliance, auditing, evals.
// related pillars
01 Compatibility Esri-compatible service surface, OGC standards, and SDKs. Read pillar 01 qgis Honua QGIS Plugin Early-preview local assistant workflow for QGIS with explicit privacy boundaries. Open plugin page 05 Simple operations Terraform, OpenTelemetry, and GitOps. Read pillar 05 06 High performance AOT-compiled engine, benchmarked, cloud-optimized. Read pillar 06 GIS Honua-GIS Open-weights GIS model/eval track, status table, and release gates. Read Honua-GIS
// next

Run your whole
GIS workflow with AI.

Talk to us MCP spec ↗