// capability catalog · /capabilities

Every capability. One evidence trail.

Pricing, claims, demos, and samples each show a slice of what Honua does. This page joins them: one row per capability, with its edition, current status, evidence, documented gaps, and links to see it live, try it, and read the full evidence page. Tick the capabilities you use today to build a shareable, filtered view and a rough edition/capacity estimate.

What this table establishes. It is generated from capabilities.v1.json, a draft fixture checked into this repository ahead of the real evidence artifact. It will be replaced by the capability-matrix.v1.json published by honua-server CI (honua-io/honua-server#2892 ↗). Counts shown here are either already published on claims.html / the compatibility matrix, or explicitly marked as not yet published — none are invented.

How to read a row

Source evaluation

Runnable and inspectable from public server trunk today. A numbered variant carries a dated CITE or conformance count.

Partial coverage

Documented, operation-level coverage and gaps exist, but no aggregate test count is published for this exact capability yet.

Preview

Implemented and disclosed, but pre-GA: disabled by default, opt-in only, and may change before general availability.

Proof pending

No public evidence artifact is published for this exact capability yet.

Edition chips

Community (free, self-host, ELv2), Pro, and Enterprise — see pricing for what each adds.

Gaps in-row

Every row states what the capability does not yet cover, in the row itself — not on a separate page you have to find.

The catalog

DRAFT evidence snapshot from capabilities.v1.json — DRAFT-FIXTURE (replace with honua-server capability-matrix.v1.json — see honua-io/honua-server#2892/#2893).

Editing

Editing capabilities: edition, status, evidence, and links
Capability	Edition	Status & evidence	Summary & gaps	Links
Feature editing	Pro	Partial coverage No count published yet	Create, update, and delete features via Esri FeatureServer applyEdits and open protocols (OGC API Features, WFS-T, OData). Branch versioning is Preview (post-first-release)	See it live · Try the sample ↗ · Docs · Evidence →

Serving

Serving capabilities: edition, status, evidence, and links
Capability	Edition	Status & evidence	Summary & gaps	Links
Esri FeatureServer (query & serve)	Community	Partial coverage No count published yet	Serve queryable feature layers through Esri's GeoServices REST FeatureServer surface, side by side with OGC API Features. Query parameters, attachments, relationships, and versioned workflows vary by dataset — validate before cutover.	See it live · Try the sample · Docs · Evidence →
Esri MapServer (dynamic export)	Community	Partial coverage No count published yet	Serve dynamic map exports, identify, legends, and layer definitions through Esri's GeoServices REST MapServer surface. Dynamic export, identify, legends, and renderer parity vary by service — validate before cutover.	See it live · Try the sample · Docs · Evidence →
OGC API Features	Community	Source evaluation — counted evidence 137/137 · OGC API Features	Serve and query vector features through the OGC API Features standard, the open-protocol counterpart to Esri FeatureServer. Write support through this surface is WFS-T/OGC API Features Part 4; Esri FeatureServer applyEdits is tracked separately under Editing.	See it live · Try the sample · Docs · Evidence →
WMS 1.3 map rendering	Community	Source evaluation — counted evidence 199/199 · WMS 1.3	Render map images through the OGC Web Map Service 1.3 standard. No documented gaps.	Docs · Evidence →
WMTS 1.0 tile caching	Community	Source evaluation — counted evidence 60/60 · WMTS 1.0	Serve pre-rendered map tiles through the OGC Web Map Tile Service 1.0 standard. No documented gaps.	Docs · Evidence →
Vector tiles (OGC API Tiles)	Community	Source evaluation — counted evidence 16/16 · OGC API Tiles	Serve vector tile sets through the OGC API Tiles standard for client-side rendering. No documented gaps.	Try the sample · Docs · Evidence →
STAC catalog & search	Community	Partial coverage No count published yet	Publish a SpatioTemporal Asset Catalog (STAC) for imagery and raster collections, queryable via STAC API search. STAC is a supported surface outside the published 952-assertion CITE snapshot; no separate STAC conformance count is published yet.	See it live · Docs · Evidence →

Geocoding

Geocoding capabilities: edition, status, evidence, and links
Capability	Edition	Status & evidence	Summary & gaps	Links
Single-line geocoding	Pro	Partial coverage No count published yet	Forward, reverse, and suggest geocoding with provider failover through Esri GeocodeServer and the SDK geocoding sample. Batch geocoding is an Enterprise capability. No public evidence artifact is published for geocode-operation coverage yet.	Try the sample · Docs · Evidence →

Data ingest

Data ingest capabilities: edition, status, evidence, and links
Capability	Edition	Status & evidence	Summary & gaps	Links
One-shot file import	Community	Proof pending No count published yet	One-shot import of GeoJSON, Shapefile, and GeoPackage files into serving layers. Queryable ArcGIS FeatureServer/MapServer layer import and bounded GeoServer catalog apply are Enterprise capabilities. No public evidence artifact is published for import coverage yet.	Docs · Evidence →

Analytics

Analytics capabilities: edition, status, evidence, and links
Capability	Edition	Status & evidence	Summary & gaps	Links
Spatial joins & analytics	Pro	Proof pending No count published yet	Clustering, spatial join, buffer aggregate, density binning, and related spatial analytics operations. No public evidence artifact is published for spatial-analytics operation coverage yet.	See it live · Docs · Evidence →

Alerts

Alerts capabilities: edition, status, evidence, and links
Capability	Edition	Status & evidence	Summary & gaps	Links
Geofence enter/exit alerts	Pro	Preview No count published yet	Geofence enter/exit triggers with an evaluation engine and webhook delivery. Preview: experimental, disabled by default, and available only through customer opt-in. Dwell and attribute-threshold triggers with email/Slack/Teams/SNS/Event Grid delivery are an Enterprise capability.	See it live · Docs · Evidence →

Imagery & rasters

Imagery & rasters capabilities: edition, status, evidence, and links
Capability	Edition	Status & evidence	Summary & gaps	Links
Cloud-Optimized GeoTIFF serving	Pro	Proof pending No count published yet	Serve Cloud-Optimized GeoTIFFs directly from S3/Azure cloud storage, with temporal raster mosaics. No public evidence artifact is published for COG-serving operation coverage yet.	See it live · Try the sample · Docs · Evidence →

Streaming

Streaming capabilities: edition, status, evidence, and links
Capability	Edition	Status & evidence	Summary & gaps	Links
Real-time feature streaming	Pro	Preview No count published yet	WebSocket / SSE feature streams with filters and replay cursors for live incident and asset feeds. Preview: experimental, disabled by default, and available only through customer opt-in.	See it live · Docs · Evidence →

Identity

Identity capabilities: edition, status, evidence, and links
Capability	Edition	Status & evidence	Summary & gaps	Links
OIDC single sign-on	Pro	Preview No count published yet	Single-provider OIDC SSO (Azure AD, Google, Okta, Auth0, or generic) implemented in public source. Multi-provider SSO and custom claim-to-role mapping are an Enterprise capability. No immutable public server release artifact is published yet.	Docs · Evidence →

Build your capability plan.

Tick the capabilities you use today above, enter your expected serving units, and this page estimates the edition and capacity band you would need — using the published pricing bands. Requires JavaScript for the live estimate and shareable link; the checklist and submission below work either way.

Tick capabilities above and enter your expected serving units below — JavaScript computes an edition and capacity-band estimate here. Without JavaScript, you can still submit your selections using the form below.

Expected serving units

// migration intake

Send us your capability plan.

Submitting includes the capabilities you ticked above and your expected serving units, so we can reply with the right edition, evidence, and next step — no separate re-explaining what you need.

Submitting this form creates no commercial commitment. If a paid pilot fits, we scope and quote it separately.

Name Work Email Company

AI-assisted operations & AI Studio interest Pilot funding status

Anything else we should know?

By submitting, you ask Honua to respond to this inquiry. See Privacy & Cookies for processors, retention, and your choices.

Scanning an existing Esri estate?

The honua-esri-assess ↗ footprint scanner maps a scanned estate through the same capability keys to a ?caps= link like this page produces — nothing about your estate leaves your network. See Migration Evidence for the assessment workflow.