Keep the interfaces that work.
Migrate one workflow at a time.
Honua exposes documented GeoServices REST, OGC, OData, tile, gRPC, MCP, and SDK surfaces. Existing clients can keep using familiar interfaces where their required operations are supported. Check each protocol, operation, client version, and evidence boundary before planning a cutover.
Check the operation, not just the protocol name.
Published support claims link to a public test suite, parity matrix, or evidence document. The summaries below separate partial GeoServices REST parity, a dated OGC CITE snapshot, and SDK package maturity. Use the claims matrix for the underlying evidence.
Honua targets selected FeatureServer, MapServer, ImageServer, Geometry Service, GeocodeServer, NAServer, and GPServer operations. Coverage differs by service and operation. The public parity matrix and JSON file in honua-server identify implemented, pending, and deferred behavior.
The 2026-05-17 snapshot reports 952/952 passing applicable, basic, or core assertions across 11 CITE suites. This is Honua's own test evidence, not formal OGC certification. The link below records the suite profiles, run scope, and audit trail.
The JavaScript SDK and migration companions are public prereleases. Python and .NET remain source previews, and Honua does not yet publish an automated .NET or MAUI source rewriter. Review the migration page and package evidence before choosing a path.
// availability and evidence are separate: a passing snapshot is not a support window or certification
Connect the data sources your workflow actually needs.
Use PostGIS as the operational store, import supported exchange formats, or serve supported cloud-native formats from object storage. Confirm provider and operation coverage for your workload before deployment.
// review provider, format, and operation coverage in the public documentation before production use