Honua Server's public trunk exposes documented GeoServices REST, OGC, OData, tile, gRPC, and MCP surfaces over shared policy, catalog, query, rendering, and job paths. Coverage varies by protocol and operation, and no immutable public server release artifact is currently published.
A shared runtime handles authentication, policy, catalog lookup, query planning, encoding, and telemetry. Protocol adapters translate supported operations into that core; they do not make every protocol operation interchangeable.
Illustrative sequence only. Latency and response behavior depend on the operation, data, and deployment.
Existing clients can retain familiar service shapes when their required operations, parameters, versions, authentication, and extensions are covered.
Documented surfaces converge on common policy, catalog, data, analytics, publishing, and job components. Capability flags make the available surface inspectable.
PostgreSQL/PostGIS is the read/write operational store. Covered relational connectors, file imports, and object-storage formats have provider- and operation-specific boundaries.
Showing documented capabilities across all editions. Maturity labels still apply.
Documented GeoServices REST, OGC, OData, STAC, tile, gRPC, and MCP operations with scoped coverage.
CommunityPostGIS-backed catalog and data paths, API keys, health probes, Prometheus, and OpenTelemetry.
CommunityFeatureServer editing, spatial analytics, geocoding, cloud raster paths, and multi-node caching.
ProReal-time streams and alert evaluation are pre-GA, disabled by default, and require explicit opt-in.
ProMulti-provider OIDC, claim-to-role mapping, branch versioning, service imports, and extension hooks.
EnterpriseThe catalog separates implemented, Preview, private-beta, and planned behavior instead of flattening it.
All editionsFeatureServer, MapServer, ImageServer, GeocodeServer, NAServer, GPServer, and Geometry Service have documented operation-level coverage and gaps. Validate every required workflow before moving an endpoint.
Run the open, read-only assessment tooling against the service inventory. Record services, layers, client versions, authentication, extensions, data sources, and workflows without modifying the source.
honua-esri-assess → local inventory and capability map
Compare every required operation and parameter with the public parity matrix. Unsupported renderers, symbols, attachments, extensions, and authentication flows stay visible for manual review.
Open the compatibility evidence →Copy selected layers from supported queryable FeatureServer or MapServer roots into PostGIS and publish the pilot. Unsupported content is reported rather than silently treated as compatible.
Review migration evidence →Exercise the actual clients, operations, and data that must continue to work. Keep the existing service available while gaps are fixed or accepted. Estate-wide behavioral parity reporting remains planned.
Evidence per workflowRepoint a service after its required workflows pass. Preserve the source service as a rollback path, observe the moved workload, and repeat service by service instead of scheduling a big-bang replacement.
Read the full migration playbook →Supported import and call-site transformations are available through the published prerelease tooling.
A source-preview scan, translate, and run path emits evidence for recognized operations and manual review.
Guided reimplementation and adapters are documented; no automated .NET or MAUI source rewriter exists today.
A matching protocol name is not proof that every client behavior or extension will transfer.
Server MCP discovery and query are source-evaluation paths. The separate geospatial-mcp specification remains a source preview with partial coverage. The single-environment operator loop is private beta.
Discover covered services, read metadata, query features, and invoke supported analysis through server APIs. Policy checks apply to the agent identity just as they do to any other client.
Read health and telemetry, inspect deterministic findings, and prepare policy-scoped proposals. Risky and irreversible work remains approval-gated.
Health/readiness endpoints, Prometheus metrics, and OpenTelemetry signals expose the deployment state.
Operators and agents can read the available signals and supporting evidence before proposing a change.
The single-environment loop can produce structured proposals under configured release and policy controls.
Deterministic low-risk actions require explicit policy. Risky and irreversible work remains approval-gated; the system does not claim unattended fleet self-healing.
Post-action verification, signed fleet promotion, and broader autonomous remediation remain planned.
Agents use scoped credentials and the same authorization boundaries as interactive or service clients.
Operators can inspect the condition, proposed action, and configured policy before execution.
Automation does not turn unknown, risky, or irreversible work into an implicit background action.
Use the public Helm chart to evaluate a stateless Honua server tier on AKS with managed PostgreSQL/PostGIS, shared object storage, Redis for multi-node mode, and your observability backend.
Available for Kubernetes evaluation. Immutable live upgrade and rollback evidence is not yet published.
Modules are private and must be pinned to an exact commit. No stable public SemVer bundle exists.
Validate cold starts, migrations, storage, job durability, failure handling, and rollback behavior.
There is no Azure Marketplace listing or one-click production deployment available today.
Replica counts, service tiers, regions, availability targets, and recovery objectives remain workload decisions.
Use the public Helm chart to evaluate Honua on EKS, or inspect the ECS/Fargate path available in source. Keep the server tier stateless and place operational state in PostgreSQL/PostGIS, shared object storage, and Redis where multi-node behavior requires it.
Evaluate through the public Helm chart. This is not a certified, sized production architecture.
Evidence differs from the Kubernetes path; validate deployment, health, scaling, and rollback behavior.
Validate cold starts, storage, migrations, queue semantics, job durability, and failure recovery.
There is no AWS Marketplace listing or one-click production deployment available today.
Infrastructure modules are private, with no stable public bundle; Lambda and Batch remain evaluation paths.
Use the architecture to orient the evaluation, then verify compatibility, availability, and deployment boundaries before choosing a production path.