Honua 2026.1 rc.1

Honua 2026.1 rc.1

Status: Release Candidate. This is the 2026.1 Release Candidate. General availability follows
FOSS4G North America (November 2-4, 2026). Use the RC to evaluate and to run pilots. The GA
release record will state which qualification evidence was collected against which candidate;
until then, the GA tier below describes the commitment, not a completed qualification.

Honua is a geospatial platform built for AI agents and people to use together: the server, SDKs
for JavaScript, Python and .NET, an MCP server for agents, and Honua Studio for AI-assisted map
making.

Honua 2026.1 is the first release of Honua Server, the server-side platform for teams that run
their own GIS infrastructure and want AI agents and people to work on it through the same
vocabulary. It replaces the proprietary or GeoServer-based serving tier organisations run today
with one server that speaks the protocols their clients already use.

Honua Server is Fair Source. The source is published under the Fair Core License, Version 1.0,
ALv2 Future License (FCL-1.0-ALv2): run it yourself, including on air-gapped infrastructure, read
it, modify it, and redistribute it for any purpose except offering a competing product. Each
release becomes Apache-2.0 two years after it is published. The SDKs, Console, Studio and the open
protocol projects are Apache-2.0 today.

This document is the human description of the release. The sections that follow it are generated
from the certified platform manifest and are the authoritative record of what was pinned, which
gates passed, and how to upgrade.

What ships

One server image serves PostGIS-backed data through every surface below. Clients connect
to the protocol they already speak; nothing has to be re-authored for Honua.

Area	What 2026.1 delivers	Reference
GeoServices REST serving	FeatureServer (query, editing, attachments, replicas), MapServer, ImageServer, GeocodeServer, GPServer, VectorTileServer, Geometry Service and portal token issuance. Desktop and web GIS clients connect to Honua as they would to any GeoServices REST server.	GeoServices REST
OGC APIs and classic OGC	OGC API Features (with CQL2 and the Part 2 CRS class), Tiles, Maps, Coverages, Processes, Records, Styles; WMS 1.3 and 1.1.1, WFS 2.0/1.1/1.0 with transactions, WCS 2.0, WMTS 1.0, WPS 2.0. Fourteen OGC CITE suites run weekly against trunk with recorded all-pass evidence.	OGC APIs, CITE status
Web and BI access	Vector tiles with TileJSON and generated styles, PMTiles archives over HTTP range requests, Terrain-RGB and elevation, STAC, OData v4 for Excel and Power BI.	Vector tiles, OData
Cloud-native data	Reads and serves GeoParquet, GeoArrow, GeoBuf and FileGDB; cloud-optimized GeoTIFFs in S3 or Azure served through ImageServer, WCS and OGC Coverages without conversion.	Cloud-native formats
Geoprocessing (Preview)	A built-in catalog of 101 processes, every one backed by an execution-content proof, exposed as GPServer, OGC API Processes and WPS over one job runtime. Custom-code workers run Python and .NET jobs in separate images.	Geoprocessing
Spatial analytics	Server-side clusters, spatial joins, buffer aggregation, density and H3 binning over published layers.	Query and analyze
Publishing and migration	Publish files, databases, rasters and tiles through the admin API, CLI or an agent. The honua-migrate CLI discovers a GeoServices REST or GeoServer service, produces a reviewable plan, applies it with explicit acknowledgement and records parity evidence.	Migration guides
Agents and the shared vocabulary	The Open Knowledge Format (OKF) names 119 capabilities; the same keys appear in the docs, the capability manifest and the MCP tools, so a person and an agent describe the same operation with the same words. A bounded MCP profile and the honua admin CLI drive the control plane from one terminal.	OKF, Connect AI agents
Operate safely	Production enables a typed operation policy with a fail-closed default: built-in rules allow administrators and scoped admin keys, and operators can require approval or a dry run per operation. Creating, rotating or revoking API keys, changing user roles and managing OAuth clients require full-administrator authority. Protected updates check the recovery plan before they activate, and the schema-reader guard refuses to boot across an unreviewed contract migration.	Operating Honua
SDKs and authoring	JavaScript/TypeScript, Python and .NET SDKs with public packages (versions under Supported clients); Honua Console for administration; Honua Studio (Preview) for AI-assisted map and app authoring.	SDKs

The exact component versions, image digests, contract versions and database schema floor for this
release are in the Components section generated below. Deploy by digest, never by a floating tag.

Editions and licensing

2026.1 ships with licensing disabled (Licensing__Mode=Disabled), and that is the documented
deployment posture for every target, including Production. No license file, signing key or edition
selection is required, every catalog entitlement is active, and no serving-unit metering or band is
measured or enforced. Authentication, authorization, resource limits and capability maturity
still apply. The Community, Pro and Enterprise editions, signed license
envelopes and capacity metering are implemented and will be hardened and enabled in 2026.2.

Edition (when licensing is enabled)	Adds
Community	The documented Community protocol surfaces, publishing, one-shot file import, portal tokens
Pro	GeoServices editing, spatial analytics, real-time streams, Redis caching, geocoding, single-provider OIDC, routing (NAServer), core branch versioning (Preview)
Enterprise	Multi-provider OIDC governance, claim-to-role mapping, organisational approval and policy controls, specialised scene ingest and I3S (Experimental)

See Editions and licensing
for the entitlement model, and LICENSE and
NOTICE for the source terms.
Third-party components and their licenses are listed in
THIRD-PARTY-NOTICES.md,
which is also shipped inside every image and NuGet package.

Compatibility and support

Dependency or client	2026.1 position
PostgreSQL / PostGIS	PostgreSQL 16 with PostGIS 3.4, 17 with 3.5, 18 with 3.6 are tested. AWS Aurora PostgreSQL 16 and Azure Database for PostgreSQL Flexible Server 16 and 17 are tested through CI proxies.
Other data providers	SQL Server, Oracle, MySQL/MariaDB, Amazon Redshift, Snowflake, Databricks and embedded DuckDB. The Oracle provider is bundled in 2026.1 and becomes an optional package in a later release.
Deployment	GA: Docker Compose on a single host and AWS ECS. Preview: AWS Lambda, and the Helm chart on Amazon EKS or other Kubernetes distributions. Every supported deployment is single-tenant on x86_64. Terraform modules for AWS and Azure and the Helm chart ship with the release; Azure and ARM64 deployments are not qualified for 2026.1. The RC is qualified on AWS with the honua-iac v0.4.6 Terraform modules.
Third-party desktop GIS client	Compatible with FeatureServer and MapServer, tested with 3.4. Third-party desktop client certification is advisory for 2026.1, not a release gate.
QGIS	OGC API Features, WFS 2.0, WMS, WMTS, tested with 3.40 and nightly PyQGIS runs.
Web clients	Honua works with MapLibre GL JS, a compatible Leaflet-based client, and CesiumJS; automated browser suites exercise each of them.
BI clients	Power BI Desktop and Excel over OData v4, with recorded evidence. Tableau uses the same surface but has no checked-in evidence.
GDAL/OGR	OGC API Features and WFS 2.0 with GDAL 3.4 or later.
SDKs	See Supported clients. Each SDK also has a supported client range per surface in the compatibility matrix in the release record; the floor is the oldest client still supported, and the pin is what shipped. The SDK checks the server capability contract at connect time.

Supported clients

SDK	Package	Version for 2026.1
JavaScript / TypeScript	@honua/sdk-js (npm)	0.2.10
Python	honua-sdk (PyPI)	0.1.19
.NET (net10.0)	Honua.Sdk (NuGet)	1.12.0

These are the client versions the release is qualified with. The generated Components and
compatibility sections below are authoritative if they ever differ. The .NET SDK has no OGC...

Honua 2026.1

Status correction (2026-09-01, operator ruling): This tag is a pre-release engineering snapshot. The 2026.1 GA cut has not yet occurred — Honua has not shipped its first release yet. Gate claims below predate the per-gate truth rendering fix; see the attached gate-report.json for actual per-gate status (cloud-parity: skipped).

Honua 2026.1

A certified platform release — the pinned, interoperable set of component versions known to work together. Operate this one label, not N independent versions.

Certified by the release train: https://github.com/honua-io/honua-release/actions/runs/32391462332

Components

Component	Version	Pinned commit	Artifact / image
geospatial-grpc	0.2.0-alpha.1	73fc882b1ae0	—
geospatial-mcp	pre-release	5e052a76b648	—
honua-console	pre-release	2cd3a73a6b10	ghcr.io/honua-io/honua-console:candidate-2cd3a73a6b10-32369440068-1
honua-helm	pre-release	4c0a5d2d4da1	oci-chart:honua
honua-iac	pre-release	cace70f7b592	terraform-registry:honua
honua-sdk-dotnet	1.6.0	a5fb6f54a345	nuget:Honua.Sdk
honua-sdk-js	0.1.7-beta.0	7cb892e2de43	npm:@honua/sdk-js
honua-sdk-python	0.1.10	953f2b3ba2cb	pypi:honua-sdk
honua-server	pre-release	f897700159e2	ghcr.io/honua-io/honua-server:nightly-aot-f897700

Contract versions

• admin: v1
• metadata: metadata.honua.io/v2alpha1
• grpc: v1
• geoservices: 1.0.0
• ogc: 1.0.0
• stac: 1.0.0

Database schema

• requires 106 (preflight refuses to start below this).

Compatibility window

• server supports clients within N-2 minor of its contract version; deprecated surfaces carried ≥ 2 releases.

Breaking changes & upgrade actions

None recorded for this release. Per-component breaking changes are generated from change metadata (conventional-commit + change-class labels) once that pipeline lands (PLAN §8); until then, consult each component's own release notes.

Verification & provenance

• Every wired release gate passed (manifest validity, per-repo CI on the pinned SHAs, artifact-consumption, cross-component seam, cross-cloud parity, cross-repo conformance).
• The pinned platform-manifest.yaml + compatibility-matrix.yaml are attached and OIDC-signed; verify the signature before deploying.