2026.1 ships with licensing disabled.
Set Licensing__Mode=Disabled in the server and worker environments. After startup, authenticate to GET /api/v1/admin/license and require data.mode: disabled. Use the release installation settings.
All catalog entitlements are active. No license file, minting or edition gating is required; serving-unit bands are neither measured nor enforced. Authentication, authorization, safety limits and capability maturity still apply. Multi-tenancy, alerting and offline sync remain Preview.
Edition assignments, license pricing and capacity bands on this page describe 2026.2 intent, not requirements for 2026.1. Licensing hardening, metering and marketplace automation are deferred to 2026.2. The supported operating envelope defines qualification limits. ELv2 source-license terms and paid service agreements still apply.
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 v2, Python 3; ports 8080, 8081, 5432 and 6379 free git clone https://github.com/honua-io/honua-server.git cd honua-server # a public preview image by digest (see "Pin what you evaluate") export HONUA_SERVER_IMAGE=<CANDIDATE_SERVER_IMAGE> # writes per-install credentials to .env, then starts the stack and waits until it is healthy python3 scripts/docker/quickstart.py docker compose ps # healthy: continue with import, publish, and map verification
Pin what you evaluate: the fast lane runs the server image you name, not a build of the checkout. The 2026.1 release is not yet cut. Choose a public server image from GitHub Packages ↗, copy its digest-qualified ghcr.io/honua-io/honua-server@sha256:... reference, and set it as HONUA_SERVER_IMAGE. A nightly image is a preview, not a qualified customer release. Record the digest it resolves to (docker image inspect --format '{{index .RepoDigests 0}}' "$HONUA_SERVER_IMAGE") and re-run comparisons against that pin. 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 @ bfbe96ead011. JavaScript @honua/sdk-js 0.2.0, Python honua-sdk 0.1.16 and .NET Honua.Sdk 1.11.1 are public packages. See SDK availability and compatibility for exact install details.