// operations

Run GIS like
the rest of your stack.

Honua uses familiar platform primitives: containers, health and readiness checks, OpenTelemetry, and version-controlled change proposals. Container, probe, and telemetry paths are available in public source. The honua-devops GitOps loop manages one environment in private beta; identity capabilities have separate source-evaluation boundaries below, and signed cross-repository releases, fleet promotion, and broader autonomous remediation are planned.

Review your deployment Explore private-beta automation →

GitOps · pull requestsPRIVATE BETA

#284Update Parcels FeatureServer schema · add lot_area_acresMERGED

#283Bump zoning map style · v3 rampMERGED

#282Update scoped API-key policy for field operationsOPEN

#281Rotate object-storage credentialsMERGED

Identity · scoped API keysSOURCE EVALUATION

credentialnamed API key

scopeservices:read

rotationexplicit lifecycle

permissionsinspectable

activitystructured events

Telemetry · OpenTelemetryEXAMPLE WORKLOAD

p50p95p99err raterps // illustrative · real p95s come from your deployment

// available · private beta · planned

Infrastructure as code in. OpenTelemetry out. Governed changes in between.

Available in source: a public Helm chart, health endpoints, and OpenTelemetry signals. Evaluation access: private Terraform modules; no stable SemVer Terraform module bundle is published yet. Private beta: honua-devops can triage findings and route proposed fixes through policy and release controls for one environment. Fleet promotion and wider autonomous recovery remain planned.

terraformEVALUATION ONLY · PIN EXACT COMMITinfra/honua.tf
# Requires honua-iac access; no stable module tag yet.
module "honua" {
  source = "git::https://github.com/honua-io/honua-iac.git//infrastructure/terraform/modules/aws-ecs?ref=6ff579981405e8cda2277d56d0cc3e894539f51d"
  # Evaluation pin shown for reproducibility, not a release.
  # Start single-node; multi-node requires shared storage + Redis.
}

honua-devops · example loop●PRIVATE BETA

03:42

⚠ otel alert · p95 spike

FeatureServer · Parcels · 87ms → 412ms

trace ab18c · span 4f2a

03:43

↪ agent · triage

Likely cause: concurrent-request autoscale lag.

cross-referenced prior incidents

03:43

↪ proposed fix · infra/honua.tf

- autoscaling = { min = 2, max = 24 }

+ autoscaling = { min = 4, max = 32 }

03:44

📝 PR filed · awaiting review

gh.example.gov/infra · "fix: bump featureserver autoscale for traffic spike"

reviewers: @sre-oncall · merge gate: green ci

policy and release controls apply · no tool-path bypass action history recorded · private beta

// runs on what you already run

Built from familiar cloud primitives.

Deploy the server through infrastructure as code, run it in your cloud account, and connect it to your existing storage services. Identity integration has separate current and planned boundaries.

01 · Containers first Deploy an OCI container on infrastructure you operate.

Plain Docker, Helm/Kubernetes, ECS/Fargate, and AKS paths are available in source at different evidence levels. Serverless and batch adapters are evaluation paths; validate cold starts, storage, job durability, and rollback behavior against your workload before adopting them.

02 · PostGIS and object storage The database you trust stays the system of record.

Keep operational features in PostGIS and bounded artifacts in S3, Azure Blob, or MinIO. Supported GeoParquet and COG workflows can read objects in place, avoiding an import step for those workloads.

03 · Identity integration API keys by default; OIDC available for source evaluation.

Scoped API keys and portal tokens are the current default. Public source implements single-provider OIDC under the Pro entitlement and multi-provider OIDC with custom claim-to-role mapping under Enterprise; OIDC remains off until configured. No immutable public server release exists, so validate the exact identity path before production. The private-beta operator uses narrowly scoped credentials while its bearer-identity path is completed.

// performance you can measure

Choose a deployment shape from evidence.

01 · AOT-compiled An alternative deployment path for startup-sensitive workloads.

The engine has a .NET NativeAOT deployment path. Cold-start and scale-to-zero suitability depend on the provider and workload; validate them with the published benchmark harness before choosing a serverless shape.

02 · Benchmarked in the open Public methodology you can run yourself.

The open geobench suite measures latency percentiles, throughput, and cold starts. Run it against your data and traffic shape before sizing production.

03 · CDN-friendly by design Finite tile keys are built for edge caching.

Tiles and other bounded artifacts are the baseline CDN path. Ad hoc feature and spatial queries are not exact-response cached by default; use bounded database admission and measure your own traffic shape.

// what your platform team already knows

Map familiar platform practices to GIS work.

Familiar platform practices mapped to GIS operations
Operation	Legacy GIS	Honua
Roll out a schema change	Apply changes through product-specific administration workflows.	Propose a change in Git, review it, then roll it out. (private beta)
Add a user role	Maintain roles in a product-specific user store.	Create a scoped role and grant per-operation permissions. Custom OIDC claim mapping is an Enterprise source-evaluation path.
Trace a slow request	Correlate product logs and monitoring manually.	Follow an OpenTelemetry trace and the span ID returned with the request.
Rotate a credential	Update product configuration and restart where required.	Resolve configured secret references from your cloud secret manager at startup.
Roll back a release	Restore a prior configuration or backup through product tooling.	Single-environment health-gated rollback is private beta. Signed rollback across multiple environments is planned.
Triage an alert	Inspect logs and metrics, then prepare the remediation.	Ask an MCP-connected agent to inspect telemetry and draft a proposed fix. (private beta)

// the point

Reduce routine GIS operations.
Keep people in control.

Review your deployment Explore private-beta automation

Run GIS likethe rest of your stack.