Honua Server
Publish, query, edit, and process geospatial data through shared services and standard interfaces.
The runtime behind maps, applications, and analytical jobs.
Server, SDKs, Console, and AI tools for geospatial applications and operations—with experimental mobile and field collection.
Build with SDKs, work in Console, connect an agent, or explore the field tools. Each component has its own role and release maturity. See what each component replaces →
Publish, query, edit, and process geospatial data through shared services and standard interfaces.
The runtime behind maps, applications, and analytical jobs.
Manage data, services, jobs, and sharing in Console. Use Studio’s realtime editor alongside the shared AI conversation.
Studio is part of Console, not a separate application to launch.
JavaScript / TypeScript for web applications; .NET and Python for backend services, analysis, and data pipelines.
Typed feature access, administration, and supported processing workflows.
Connect AI through MCP and use command-line tools to inspect services, prepare workflows, and propose operational changes.
Explicit permissions and separate approval for consequential changes.
.NET MAUI libraries for mobile field apps, GeoPackage storage, and connectivity-aware synchronization.
Pre-1.0 alpha. Client and server support determine the available field workflows.
The field collection app built on the Mobile SDK: forms, offline capture, and synchronization with geospatial services.
Early development, not a GA field app. Android has verified workflows; other device targets remain unverified.
Start with the work: publish data, build maps, analyze, automate, and operate.
Create layers from existing database tables without copying data, or import files and services.
Find features, filter results, update records, and work with versioned edits.
Compose maps with AI, style layers, collaborate, and prepare print layouts.
Run spatial jobs, joins, buffers, clustering, density, and terrain analysis.
Locate addresses, reverse-geocode coordinates, and solve network routes.
Work with cloud rasters, imagery services, mosaics, and multidimensional coverages.
Query elevations, discover scenes, and publish 3D tiles and specialist scene data.
Filter by time, follow feature changes, and send event notifications.
Collect data with online forms and synchronize disconnected field work.
Discover data, ground requests, prepare plans, and execute reviewed actions.
Manage services, monitor requests, and coordinate runtime and cache resources.
Connect identity providers, manage organizational access, and extend the server.
Preview and experimental functionality is labeled where stated in the referenced scope. Release notes ↗
Work with spatial data from desktop GIS, web applications, backend services, and AI agents.
Feature, map, imagery, geometry, processing, geocoding, routing, and scene services through familiar REST interfaces.
Feature access, maps, tiles, processing, and catalog discovery.
Familiar service interfaces for desktop GIS and existing integrations.
Typed spatial access, agent tools, business intelligence, and asset catalogs.
Publish existing database tables as live layers without copying their data. PostGIS supports full read/write workflows; other providers have read-only or experimental scope, as shown below.
Spatial data, edits, query statistics, analytics, and native spatial output.
Serve geometry and geography tables from an existing database.
Embedded analytical and reference data without another database service.
Serve existing spatial tables through the provider’s query interface.
SDO_GEOMETRY support; use a non-Native-AOT build.
Native GEOMETRY and GEOGRAPHY through the warehouse provider.
Read spatial warehouse tables; use a non-Native-AOT build.
Read from a SQL Warehouse through the Statement Execution API.
Experimental providers are separate from the supported read/query paths. Provider reference ↗
See which formats you can import, register in place, produce, or request as query output.
Compact formats for analytical datasets and query results.
Publish imagery and tiles from files or object storage.
Register datacubes or convert scientific sources for coverage access.
NetCDF4, HDF5, and GRIB use the documented GDAL-to-Zarr path and require a reader-enabled build. Coverage release scope remains separate.
Bring in familiar datasets and export through the documented file or query paths.
Import tracks, interchange files, geometry text, and packaged databases.
Choose the response format that fits your client or downstream workflow.
Complete import and output matrix ↗ · Cloud-native workflows ↗
Search individual operations, review evidence, or build a shareable checklist for your evaluation.