// claims and evidence · /claims
Claims you can inspect. Gaps you can see.
This page separates what is available from how it has been verified. Exact numbers link to dated evidence, compatibility is scoped by operation, and prerelease packages, private-beta capabilities, and planned work remain labeled. Start here, then inspect the full documentation ↗.
OGC CITE · 11 suites
952 / 952
Honua-run CITE snapshot · 2026-05-17
OGC API · GeoPackage · GML · KML
243 / 243
Features 137 · Tiles 16 · GPKG 31 · GML 17 · KML 42
WFS · WMS · WMTS · WCS
709 / 709
WFS 368 · WMS 199 · WMTS 60 · WCS 82
GeoServices REST
partial
per-service gaps tracked
// status vocabulary
Availability and evidence are different questions.
Availability says whether you can use something today. Evidence says how the stated scope was verified.
Source evaluation
Honua Server's public trunk can be built and run through the local quickstart. No immutable public server release artifact is currently published.
Public prerelease
Installable without an invitation, but the interface or package may still change before a stable release.
Private beta
Available only to selected evaluators, with scope and support agreed for the beta.
Source preview
A separately versioned SDK, tool, or plugin can be inspected or run from source, but it lacks a public registry package, release bundle, or supported integration window.
Preview
An implemented pre-GA path that may be publicly runnable, disabled by default, or available only by explicit opt-in. Behavior and support may change; it is not a generally available production commitment.
Planned
Not available today. Evaluate the current product without depending on it.
Evidence
The evidence column identifies public source, a registry check, a dated snapshot, or a pending artifact for the exact claim.
// claims by area
What the current evidence supports.
Each row states the useful claim, its limit, current availability, and the best evidence you can inspect.
| Claim area | Supported claim and boundary | Current status | Evidence |
|---|---|---|---|
| Runtime & single-binary platform | One runtime in the public source serves the documented protocol and gRPC surfaces. Coverage still varies by protocol and operation. | Source evaluation Partial coverage | Architecture docs ↗ |
| OGC & standards conformance counts | 952/952 CITE assertions pass across 11 suites (2026-05-17 snapshot): OGC API Features 137/137, OGC API Tiles 16/16, GeoPackage 1.2 31/31, GML 3.2 17/17, KML 2.2 42/42, WFS 1.0 162/162, WFS 1.1 39/39, WFS 2.0 167/167, WCS 2.0 82/82, WMS 1.3 199/199, WMTS 1.0 60/60 — each suite in its scoped profile (applicable/basic/core). STAC, Records, Processes, and SLD are supported surfaces outside the 952 count. This is our own CITE evidence run, not a formal OGC certification. | Source evaluation | CITE status ↗ · OGC conformance ↗ |
| GeoServices REST · ArcGIS · GeoServer compatibility | FeatureServer, MapServer, ImageServer, GeocodeServer, NAServer, and GPServer have documented, operation-level coverage and gaps. Geometry Service covers the documented operations, with parameter and spatial-reference caveats. Validate every required workflow before moving an endpoint. | Source evaluation Partial coverage | Parity matrix ↗ · Clients & limitations ↗ |
| Migration wedge & cutover automation | Public assessment tooling and scoped migration evidence cover supported source families. Automated cutover and SDK-driven conversion remain limited by language, package availability, and the published parity matrix. | Source preview Partial coverage | Compatibility & migration evidence |
| gRPC & SDKs | Typed gRPC services and SDK source are available for evaluation. JavaScript has a public prerelease npm package; .NET and Python remain source previews without public registry packages. No cross-version SDK-to-server support window is published yet. | Public prerelease Source preview | Ecosystem & SDKs ↗ |
| MCP & AI agent surface | The MCP surface provides discovery, schema inspection, supported filtered queries and statistics, and bounded spatial tools. Coverage remains partial and no certification is claimed. | Source preview Partial coverage | geospatial-mcp |
| Mobile · field · offline · MAUI | Mobile SDK source is available for evaluation. Connected field workflows are pilot-scoped and private beta; offline sync, conflict handling, and broader device workflows remain planned. | Source preview Private beta Planned | honua-mobile |
| Deployment & AI DevOps loop | The public Helm chart, health/readiness endpoints, and OpenTelemetry integration are available in source. No stable SemVer Terraform module bundle is published yet. GitOps operation of one environment is private beta; cross-environment promotion and broader remediation remain planned. | Source preview Private beta Planned | public Helm chart · operator evidence program · Terraform evidence is private and not linked |
| Performance benchmarks | An April 28, 2026 GeoBench snapshot is published with its methodology and limitations. Its exact Honua image and full run directory are not publicly pinned, so it is historical evidence—not a current, independently reproducible release result. | Dated snapshot Current run pending | GeoBench harness · historical snapshot and limits |
| Commercial tiers & pricing | Honua Server is source-available under the Elastic License 2.0 (ELv2) ↗; the SDKs are Apache-2.0 open source. Capacity bands, edition prices, and worked examples are public. Preview capabilities remain labeled in the pricing table. | Published | The pricing page |
// go deeper
The evidence, page by page.
Each page pairs a decision with the strongest evidence currently available—and states what that evidence cannot establish.
| Page | Claim it backs | Primary source |
|---|---|---|
| Benchmarks | How Honua and GeoServer performed in one dated, disclosed test profile | GeoBench harness + April 28, 2026 historical snapshot |
| Compatibility Matrix | Which client workflows and protocol operations are documented, partial, or unverified | Public GeoServices parity matrix ↗ + client limitations ↗ |
| SDK availability | Which SDKs are publicly installable, which remain source previews, and how compatibility is checked | Deployed availability snapshot + public registry checks |
| Head-to-head | Where Honua, GeoServer, and QGIS Server fit—and where this comparison stops | Official product documentation + the dated GeoBench snapshot |
| Migration Evidence | How to inventory an Esri estate and verify a scoped migration | honua-esri-assess footprint scanner |
| Reference Architectures | Which Honua deployment shapes can be evaluated today | honua-server / honua-helm / honua-iac deployment evidence |
// Compatibility evidence on these pages is project-produced and operation-scoped — not certification by Esri, OGC, or another standards body.
// try it live
The fastest proof is the running system.
A seeded API instance runs at demo.honua.io; the host root is not a landing page. Use the specific public surfaces: REST + interactive docs ↗ · OData surface ↗ · STAC root ↗ · SDK samples — runnable, one concept each →
// evidence bar
How to read a Honua claim.
01 · Numbers carry dates
Counts and performance figures identify the snapshot, profile, and source that produced them.
02 · Compatibility is operation-scoped
A supported product name never substitutes for testing the operations, parameters, version, and authentication flow you use.
03 · Migration is verified per estate
Inventory, parity checks, and workload tests determine whether a workflow can move; no universal cutover promise replaces them.
04 · Availability stays explicit
Source evaluation, public prerelease, private beta, source preview, opt-in Preview, and planned work are identified separately.
05 · Evidence limits are part of the result
A missing package, unpinned image, unavailable report, or unsupported operation is stated beside the claim it limits.
06 · Examples prove only their scope
A demo, transcript, or code sample shows the named path—not every client, dataset, or deployment.
07 · Benchmarks include conditions
Performance figures travel with the dataset, resource limits, configuration, test duration, and reproducibility caveats.
08 · Pricing is public
Capacity bands, edition prices, and worked examples are published on the pricing page; a signed agreement controls the purchase.