Guides / architecture / reference / evidence
Find what you need. Get to work.
Choose a task, get a result, then go deeper only when you need the architecture, exact reference, or supporting evidence.
Six common jobs.
Start with the path that matches what you need to do today.
Run Honua and publish your first layer
Start one container beside PostGIS, import GeoJSON, publish a layer, and verify it from a browser.
Open quickstart ↗Build an application from a maintained sample
Choose JavaScript, browser REST, Python, or a protocol-specific recipe and inspect the exact source.
Choose a starter →Connect ArcGIS, QGIS, or another client
Check client coverage, SDK install paths, and operation-level limits before changing an endpoint.
Open compatibility reference →Move one service without a big bang
Inventory, import, convert supported code, validate behavior, and run side by side.
Plan a migration →Deploy and operate Honua
Use containers, Helm, health probes, telemetry, identity, backup, and scaling guidance.
Open operations path →Understand how Honua fits
See the platform architecture, security boundaries, capability catalog, and public evidence.
Explore the platform →From clone to a responding server.
The full quickstart covers configuration, publishing, verification, and troubleshooting.
# prerequisites: Git, Docker Compose, curl; port 8080 available git clone https://github.com/honua-io/honua-server.git cd honua-server docker compose up -d curl http://localhost:8080/healthz/ready # ready: continue with import, publish, and map verification
Pin what you evaluate: no versioned server release is published yet, so the quickstart runs trunk. Record the commit (git -C honua-server rev-parse HEAD) or, if you pull the public image, resolve the mutable tag to an immutable digest (docker image inspect --format '{{index .RepoDigests 0}}' ghcr.io/honua-io/honua-server:trunk) — and re-run comparisons against that pin, not whatever trunk has become. Questions go to GitHub Discussions ↗, the public community channel.
Building with a coding agent or IDE assistant? Machine-readable SDK docs ship at /llms.txt (curated index) and /llms-full.txt (single-fetch corpus), commit-pinned with SHA-256 provenance. A live API console runs at demo.honua.io/docs ↗.
Go straight to the answer.
Guides, reference, architecture, and evidence each have a clear home.
Choose the install path that exists today.
This site tracks trunk development @ 0d10b9c63906. JavaScript @honua/sdk-js 0.1.7-beta.0 and Python 0.1.11 are public prereleases. .NET is available from source. See SDK availability and compatibility for exact install details.