Honua
// pricing & licensing

Priced like infrastructure.
Because it is infrastructure.

Self-host Community at no charge under the Elastic License 2.0 (ELv2) ↗. Pro starts at $6,000 per year and Enterprise at $15,000, with unlimited users. Commercial capacity is measured in serving units: each production node counts as one or more units under a published vCPU and memory ceiling. Every client SDK is Apache 2.0.

// two decisions

Pick a capacity band. Pick an edition.

The capacity band covers your everyday production fleet, measured in serving units. The edition determines the available capabilities: Pro is the working GIS; Enterprise adds governance features. Together they set one annual software-license price.

Community · no charge · ELv2
Serve, query, and map on the documented Community surfaces with no license key. Evaluate the public source and validate required workflows against the proof matrix before production use.
Pro
Starter $6,000 · Team $15,000 · Scale $30,000 /yr
The Pro catalog includes Esri FeatureServer editing, geocoding, spatial analytics, cloud rasters, and multi-node caching. Alerts and real-time streaming are Preview; single-provider OIDC is available in public source under the Pro entitlement. Bands cover up to 3, 10, or 25 serving units.
Enterprise
Starter $15,000 · Team $24,000 · Scale $39,000 /yr
Adds migration imports, branch versioning, multi-provider SSO with custom claim-to-role mapping, and the extension SDK to a Pro pack. These are inspectable in public source under Enterprise entitlements; no immutable public server artifact is published. Standard support is included; Priority and Premium are priced separately.
Annual prices by capacity band and edition
Capacity bandServing unitsProEnterprise
Starter Up to 3 $6,000 / yr $15,000 / yr
Team Up to 10 $15,000 / yr $24,000 / yr
Scale Up to 25 $30,000 / yr $39,000 / yr
Beyond 25 units Private offer — roughly $800–$1,000 per additional unit / year. Request a quote →

// Enterprise is a flat governance add-on over any Pro pack — same bands, same serving units, one annual number.

// the unit

What a serving unit is.

The ceiling rule. One serving unit is one production serving node up to 8 vCPU and 32 GiB RAM. Proportional larger nodes count as multiples — 16 vCPU / 64 GiB = 2 units, 32 / 128 = 4. Mixed shapes such as 12 vCPU / 32 GiB must be confirmed in the order until an exact rounding rule is published. This is capacity-band pricing, not a per-core license rate.

Non-production is excluded. Dev, test, staging, and cold-standby DR capacity does not count toward your paid band.

Users are unlimited. Units count servers, never people.

// worked examples

Annual software-license examples.

Three production deployment shapes using the published capacity bands. Cloud infrastructure and optional support or services are separate.

A small city replacing one aging GIS server
$6,000 / yr
One 8 vCPU node = 1 serving unit → Pro Starter at $6,000/yr, unlimited users. Add the governance pack → Enterprise Starter at $15,000/yr.
A utility with sixty users
$15,000 / yr
Two production nodes that may autoscale to four fit the Pro Team band at $15,000/yr. Sixty operators and analysts add no seat charge because users are unlimited.
A state agency platform
$39,000 / yr
A production fleet of 25 serving units fits Enterprise Scale at $39,000/yr. Capacity beyond 25 units uses a private offer at roughly $800–$1,000 per additional unit / year.
// the model

What the model keeps visible.

You buy a capacity band that covers your everyday fleet; your variable cost is your own cloud infrastructure, which you already know how to price.

Cost scales with workload, not adoption
Adding a user creates no Honua seat fee. Added workload may require a larger capacity band; billing is not based on named users, request credits, or data volume.
One flat annual number
Your invoice does not vary within the term when autoscaling stays inside the committed band. Contract-defined short-burst grace above the band is described separately.
Growth is prospective
Short bursts do not create automatic overages. If higher capacity becomes sustained or recurrent, move to the next band under the terms in your order.
Size down at renewal
If your committed production footprint shrinks, you can select a smaller capacity band at renewal.
Operational burst room
Standard terms include short-burst grace above the committed band. Higher emergency capacity and response commitments are available through the Surge Pack.
A visible capacity measure
Capacity consumption is visible to the operator. Commercial terms define sustained excess without request, byte, or user metering.
Non-production is free
Dev, test, staging, and cold-standby DR capacity don't count toward your band.
Topology-flexible
VMs and Kubernetes use the serving-unit model. Serverless remains an evaluation path; confirm that and any unusual deployment shape in the order form.
No usage-based billing
Paid capabilities use fast in-memory entitlement checks, but billing is not based on requests, bytes processed, or users. Workload-safety limits remain separate from licensing.
// what's in each edition

Community, Pro, Enterprise — the split, laid out.

This table maps current public source and maturity-labeled work to the commercial editions. Each tier includes capabilities from the tier to its left. Unless a badge says otherwise, an entry is Source evaluation: runnable from public server trunk without an immutable release artifact. Preview is implemented but pre-GA and may require explicit opt-in; private beta is limited to selected evaluators; planned means unavailable today. See the status vocabulary and evidence.

Capabilities in Community, Pro, and Enterprise
CapabilityCommunityPro addsEnterprise adds
Protocols & servingDocumented surfaces include GeoServices REST, OGC APIs, WMS/WFS/WCS/WMTS, OData, STAC, vector tiles, terrain, 3D Tiles, gRPC, and MCP. Coverage and write support vary by protocol; see Proof.
Esri client interopPortal token issuance + read-only Portal sharing facade
EditingFeature editing via open protocols — OGC API Features, WFS-T, OData, gRPCEsri FeatureServer editing — applyEdits / add / update / deleteSource evaluation Branch versioning — named versions, reconcile/post, VersionManagementServerImplemented in public source under the Enterprise entitlement; no immutable public server artifact is published.
Data importOne-shot file import — GeoJSON, Shapefile, GeoPackageQueryable ArcGIS FeatureServer/MapServer layer import; bounded GeoServer catalog apply for existing target PostGIS tables. The GeoServer path does not copy feature data.
AlertsPreview Geofence enter/exit triggers + evaluation engine, webhook deliveryExperimental, disabled by default, and available only through customer opt-in.Preview Dwell + attribute-threshold triggers; email, Slack, Teams, AWS SNS, Azure Event Grid, digest channels
GeocodingForward + reverse with provider failoverBatch geocoding
Spatial analyticsClustering, spatial join, buffer aggregate, density binning, sun/shadow, slice, line-of-sight, viewshed
Rasters & imageryRaster file import + servingCOG serving direct from S3/Azure, cloud storage config, temporal raster mosaic
TemporalTime filtering + extent discovery (timeInfo, OGC TIME)Date-bin histograms, time-series tiles, animation APIPlanned Temporal data versioning — as-of, diff, timeline, rollback — is not available today. Time filtering and analytics are available in public source.
StylingSmart geometry-aware defaultsAuto-cartographic styling suggestions
Static maps & printStandard static mapsHigh-DPI + large dimensions + rich overlays; PDF output + layout templates
Real-timePreview WebSocket / SSE feature streams with filters and replay cursorsExperimental, disabled by default, and available only through customer opt-in.
Caching & scaleIn-memory cachingOutput caching + Redis distributed cache for multi-node
Identity & SSOAdmin + scoped API keys, portal tokensSource evaluation Single-provider OIDC SSO — Azure AD, Google, Okta, Auth0, or genericImplemented in public source under the Pro entitlement and off until configured; validate the exact identity path before production.Source evaluation Multi-provider SSO + custom claim-to-role mappingImplemented in public source under Enterprise entitlements; no immutable public server artifact is published.
Field & mobile collectionPrivate beta Online field collection — form packages and connected submissionsAvailable only to selected evaluators; see current evidence and gaps.Planned Disconnected operation — offline policy, offline sync, and advanced collection featuresOffline sync and device workflows are not available today.
Operations & GitOpsEnv-var config, health probes, Prometheus + OpenTelemetry — available in source.Private beta Single-environment deploy preflight, plan, and rollback control plane.
AI & agentsSource evaluation Server MCP discovery & query — agents can read, search, and analyze. The separate geospatial-mcp specification remains a Source preview.Private beta Operator tools: spec plan/apply with dry runs, structured action records, and policy-gated deterministic low-risk actions. Risky and irreversible work remains approval-gated; post-action verification and coordinated fleet promotion remain planned.Source evaluation Formal human-in-the-loop approval routing and policy-scoped agent permissions. Durable compliance-grade audit storage remains deployment-dependent.
ExtensibilityPlugin / extension SDK — custom validators and edit hooks

Health probes and telemetry are available platform capabilities. The single-environment operator loop is private beta: plan/PR defaults and structured action records exist, while deterministic execution requires an explicitly configured policy. Post-action verification, signed fleet promotion, and a tamper-evident compliance audit store remain planned. Honua does not claim unattended fleet self-healing.

// license stack

How the layers are licensed.

License and commercial model by layer
AxisLegacy GISHonua
Engine licenseProduct-dependent server, core, or user licensing.Elastic License 2.0 (ELv2) ↗ source-available · Community self-hosting at no charge · paid editions priced by capacity.
SDKsLicense and distribution terms vary by product.Permissive Apache-2.0 licensing.
Open standardsStandards coverage and client licensing vary by product.Documented OGC, gRPC, and MCP surfaces without per-client Honua licensing.
ComputeScaling behavior depends on the product and deployment model.Runs in your cloud; autoscaling depends on the deployment shape and workload.
Commercial tierBundled SKUs with overlap and gating.Pro and Enterprise capacity bands · the split is laid out above.
SupportPackaging varies by vendor or service provider.Standard is included; Priority and Premium are priced separately.
MigrationApproach varies by product and client stack.ArcGIS and GeoServer imports in server source evaluation; a public-prerelease JavaScript codemod; Python source-preview tooling; guided .NET and MAUI source-preview paths.
// add-ons & services

Support, surge, and assisted services.

Support
Standard — included in all commercial tiers.

Priority — +$6,000/year; email support with a 48-hour response SLA.

Premium — starting at +$15,000/year; dedicated Slack, a 4-hour response SLA, architecture reviews, and migration assistance. Contract terms control.
Surge Pack
+15–25% of subscription. Adds a contracted high-surge allowance and response-time terms for emergency-mission organizations. Exact capacity and response commitments belong in the order form.
Assisted services
Migration assessment — $3,000–$7,500.

Fixed-scope pilots — $10,000 (simple) · $17,500 (standard) · $25,000 (complex).

Up to 50% of pilot fees credit toward year-one software within 30 days of pilot readout.
// procurement

Purchase direct today. Marketplaces are planned.

Direct annual agreements are available now; request a written quote for your edition, capacity band, and support needs. AWS and Azure Marketplace listings are planned but are not available today. If marketplace procurement is required, tell us so we can share status without treating the listing as a commitment.

// Honua Cloud — planned
Want Honua without operating the server? Honua Cloud is a planned managed service built on the same server and documented protocol surfaces. Packaging and service commitments will be published before availability. Join the early-access list →
// self-hosted today
Evaluate one container beside PostGIS using the local quickstart. All pricing above is for self-hosted deployments. Quickstart →
// next

Price your deployment.
Know the annual software cost.