Honua logo
Honua Pricing and Licensing

Pricing and Licensing

Scales with infrastructure, not headcount.

Community is free. Commercial is per-node. No per-user fees. Protocols, SDKs, mobile access, and agent workflows are never metered or gated.

Editions

Three editions. Clear boundaries.

Community Pro Enterprise
Price Free self-hosted (ELv2) Per-node commercial license (quote-based) Per-node annual contract (quote-based)
Protocols and SDKs All protocols, all SDKs, mobile toolkit included Same, plus stronger runtime depth Same, plus governance and compliance controls
Runtime boundary Single-process with in-memory coordination Distributed cache, gRPC streaming, advanced capabilities SSO/OIDC, RBAC, audit logging, change management, multi-tenancy
Support Community / GitHub Email and issue support Premium support with SLAs
Best fit Evaluation, single-team deployment, smaller production Production workloads needing throughput and scale Organizations with governance, compliance, multi-team needs
Commercial pricing is quote-based today. Three cost components: software subscription, support tier, and optional professional services. Customer cloud infrastructure spend is separate.

What ArcGIS Buyers Compare

The pricing model most teams are trying to leave.

Cost driver Typical legacy model How Honua handles it
Users Per-seat licensing that grows with every analyst, viewer, and field worker Not metered. Add users without a new purchase.
Extensions and protocols Premium extensions and protocol access sold as add-ons All protocols ship in every edition. No add-on gating.
Field / mobile Separate per-user field app subscription ($25-299/user/month) Mobile toolkit included. No separate field license.
SDK access SDK licensing tied to platform subscription tier All SDKs are Apache 2.0. Use them freely.

License Split

Different parts, different licenses.

Component License What it means
Honua Server runtime Elastic License 2.0 Use, self-host, modify, deploy. Do not resell as a managed hosted service.
Official SDKs (JS, .NET, Python) Apache 2.0 Adopt the client libraries without licensing ambiguity.
Mobile toolkit Apache 2.0 Evaluate and build on the mobile SDK without client-side licensing friction.
Site and collateral Apache 2.0 Reuse public materials internally without ambiguity.

Operator Layer

The AI operator tool is separate.

Public

Runtime, protocols, SDKs, mobile, MCP

The open-core product covers the server runtime, all protocol APIs, official SDKs, mobile toolkit, and the base MCP data-access layer.

Private

AI DevOps operator

Operator-grade rollout planning, delegated operations, and implementation-partner workflows are private enterprise tooling built on top of the public admin APIs.

Try It

Run Honua and see the platform first-hand.

The fastest way to evaluate is Docker + one SDK. After that, pricing and licensing questions get much more concrete.