Choose a deployment shape that matches the evidence.

← Back to claims & evidence

Start with one container beside PostGIS for an evaluation. Add Kubernetes, shared services, or GitOps only where the current evidence supports the deployment you need. These diagrams are reference shapes, not certified designs or sizing recommendations.

Honua Server runs on .NET 10, is packaged as a container image, stores features in PostgreSQL/PostGIS, and emits OpenTelemetry. A public Helm chart is available. Terraform, high-availability, and GitOps paths have the availability boundaries shown below.

Cross-cutting principles

• Familiar interfaces on one server. A single Honua deployment exposes documented GeoServices REST, OGC API Features, WMS, WFS, WMTS, WCS, and STAC surfaces. Coverage varies by protocol and operation; see the Compatibility Matrix.
• Stateless server tier, stateful data tier. Scale the Honua server tier horizontally; keep state in PostGIS and object storage.
• Observability by default. OpenTelemetry traces/metrics from the server tier into the operator's existing backend.
• Shared security boundary. Honua documents TLS termination, authentication options, policy-scoped authorization, and structured security events. The deploying team owns infrastructure controls by default. Durable audit storage and compliance dashboards are not baseline server features; see Security & DPA.

A. Single-node / pilot

The simplest shape — a single Honua container plus PostGIS — matches the public quickstart and the GeoBench test topology.

[ Esri / OGC / STAC clients ]
            |
        (TLS)
            v
   [ Honua Server (container) ]
            |
            v
        [ PostGIS ]

• Use it for: local evaluation, pilots, and single-team deployments.
• Start here: the server quickstart ↗. GeoBench also publishes a compose profile, although its historical headline snapshot has additional reproducibility limits described on the Benchmarks page.

B. Cloud-native HA on Kubernetes / AKS — Preview

The public Helm chart describes a horizontally scaled server tier behind an ingress, with managed PostgreSQL/PostGIS and shared services. Use this path for evaluation and pre-production testing; immutable release and live upgrade/rollback evidence are not yet published.

        [ Ingress / TLS ]
               |
   [ Honua Server pods (N) ]  ---- OTel ----> [ observability backend ]
        |                |
        v                v
 [ managed PostGIS ]  [ object storage (S3 / MinIO) ]

• Use it for: evaluation and pre-production high-availability testing on AKS or Kubernetes. It is not presented as a certified production design.
• Evidence: the public honua-helm chart. Terraform modules are private and do not yet provide a stable public deployment artifact. Multi-node mode requires shared storage and Redis.

C. GitOps-managed operations — Private beta

The private-beta GitOps engine can plan, diff, sync, and roll back one environment. Immutable release binding, verification after each action, and coordinated promotion across environments are not yet complete.

   [ git repo: desired state ]
            |
       (plan / diff)
            v
   [ Honua operator control plane ] --sync/rollback--> [ Honua deployment (A or B) ]

• Use it for: selected private-beta evaluations of plan, review, apply, and rollback for one environment. Coordinated dev → staging → production promotion remains planned.

Deployment evidence status

What these diagrams do not establish

No production sizing recommendation. The diagrams are illustrative. They do not prescribe cloud sizing, replica counts, PostGIS tiers, or object-storage settings.

No general capacity rule. Honua has not published a requests-per-pod rule. The dated GeoBench profile is benchmark evidence, not a production sizing calculator.

No compliance certification. SOC 2 Type II remains planned; no certification or report is currently available.

No marketplace install. AWS and Azure Marketplace listings and one-click deployment URLs are not currently available.