A useful foundation.
Start with the registered Community spatial capabilities. Explore, build, and self-host without a named-user fee.
Explore Community capabilities ↗Capabilities for your needs.
Pricing for your scale.
Community, Pro, and Enterprise define the capabilities. Usage or deployed capacity will define the commercial scale—not named-user fees.
Final metering units, capacity bands, and rates are being developed. Commercial evaluation terms are agreed up front.
More demanding work.
Add the registered Pro capabilities for advanced spatial workflows, integrations, performance, and agent operations.
Explore Pro capabilities ↗Organizational control.
Add the registered Enterprise capabilities for governance, sophisticated identity integration, approval policies, and enterprise workflows.
Explore Enterprise capabilities ↗These are edition summaries, not a second entitlement matrix. Essential authorization, isolation, audit integrity, and recoverability are baseline obligations. Advanced governance and automation are distinct capabilities.
Current release conditions are separate from the long-term model.
The documented 2026.1 deployment posture disables license enforcement and capacity metering, with catalog entitlements active. It does not remove runtime dependencies, approval controls, or Preview / Experimental boundaries. Read the current licensing contract ↗
ONE REGISTRY. NO GUESSWORK.
Find the capabilities you need.
The comparison below reads the same committed capability data used by the site’s evidence catalog. Minimum edition is not release maturity. Evidence labels are shown as evidence—not as production-readiness claims.
Loading the committed capability snapshot…
| Capability | Minimum edition | Evidence & release details |
|---|
Source snapshots are dated and commit-pinned, not a promise that trunk and your installed release have identical capabilities. Confirm support against the release documentation. Open the full capability and evidence catalog ↗
CLEAR LICENSE BOUNDARIESSource licenses.
Source licenses.
Explicitly stated.
- Honua Server · Honua Collect
- Source-available under Elastic License 2.0 (ELv2).
- Other platform components
- Apache License 2.0, including the SDKs and open protocol projects.
- Mobile SDK · Collect app
- Experimental Their licenses do not imply production readiness.
Repository licenses govern source use. Edition entitlements govern server capabilities. Release maturity and support terms are separate. Third-party dependencies retain their own licenses.
Inspect the repositories ↗THE COMMERCIAL DIRECTIONScale with the work.
Scale with the work.
Not the headcount.
We are developing usage-based metering, capacity bands, or a combination. The pricing should support elastic workloads—not penalize distributing the same work across smaller instances.
For customer-hosted deployments, the Honua software fee is separate from infrastructure, model-provider charges, and optional support or services.
No speculative rate card. Bring a representative workload and we’ll agree evaluation scope and commercial terms before work begins.
Discuss commercial terms