Esri-compatible + open standards
Publish client-consumable FeatureServer, MapServer, VectorTileServer, StreamServer, SceneServer and ImageServer surfaces alongside OGC APIs, STAC, CSW, WMTS, WCS, MVT and TileJSON.
See exact operations →
The Field Sentinel Web/Server engine
One data plane. Every map client.
3DGeoServEngine turns databases, files, live feeds, cloud data lakes, imagery and 3D assets into interoperable geospatial services—without locking the data model to a single vendor runtime.
FeatureServer
OGC API
ImageServer
SceneServer
StreamServer
MVT · STAC
3Dservice engine
600+REST endpoints in the shared server backend
60+geospatial, raster, 3D, database and style formats
176optional Python sidecar routes for advanced processing
2browser map engines: GeoLibre and ArcGIS Maps SDK
Designed as infrastructure
Not another map viewer. A programmable geospatial service fabric.
Each feature page documents the protocols, storage engines, processing paths and integration boundaries behind the product.
Dynamic vector tiles and cloud-native data
Generate view-dependent MVT from live DuckDB spatial queries. Query S3, GCS, Azure Blob, OneLake and HTTPS sources with predicate pushdown, then expose governed results as reusable map services.
Inspect the data paths →Real-time, video, mission and 3D
Normalize TAK, IoT, GNSS, MQTT, Redis, Kafka REST and WebSocket feeds; apply geofence and threshold rules; serve I3S, 3D Tiles, LiDAR, splats and full-motion video workflows.
Explore operational services →Spatial analytics, AI and notebooks
Run pure-Go, DuckDB, browser-Pyodide or Python-sidecar processing, plus document RAG and entity link graphs. GeoLibre already embeds JupyterLite on the web and launches real JupyterLab on desktop.
See the notebook architecture →Plugins, APIs and sidecars
Extend the browser with GeoLibre plugins, add Go service packages, call the REST and WebSocket surface, or attach isolated Python and external microservices without forking the core.
Choose an extension seam →Migration and application services
Inventory services, preserve endpoint contracts, move data and databases, reconstruct web maps and forms, modernize applications and operate staged cutovers with measurable acceptance criteria.
Review delivery packages →
A different publishing model
Keep data authoritative. Materialize the service view on demand.
Traditional GIS publishing frequently produces platform-specific service definitions and prebuilt caches. 3DGeoServEngine can keep the source in an open database, object store or portable file and create the client-facing representation at request time.
Authoritative data
PostGIS · Oracle · SQL Server
S3 · Azure Blob · GCS · OneLake
GeoPackage · GeoParquet · COG
Live feeds · files · APIs
3DGeoServEngine
DuckDB spatial + httpfs
CQL2 filtering + reprojection
Dynamic MVT + raster windows
Catalog, auth, events and processing
Consumer contracts
ArcGIS Pro and web SDKs
QGIS and OGC clients
MapLibre · deck.gl · Leaflet
BI, notebooks and custom apps
Where the innovation shows
Capabilities that change the operating model.
The advantage is not merely having more endpoint names. It is keeping multiple interfaces synchronized over the same source, minimizing duplication and letting teams choose clients independently.
LIVE
Dynamic MVT from queryable feature tables
DuckDB ST_AsMVT() creates tiles for the requested view. Edits and database updates can appear without rebuilding a static pyramid.
RANGE
Remote COG imagery as ImageServer
Register an HTTPS COG—including a public or signed object-storage URL—and read only the required byte ranges for exportImage, identify, samples, statistics and tiles.
1:N
One collection, several service contracts
A virtual collection can be accessed as OGC API Features, Esri-compatible FeatureServer and dynamic MVT instead of maintaining three copies.
DDIL
Cloud, on-premises or disconnected edge
The same Go backend runs as a native binary or container and can operate against local staged data when cloud access is unavailable.
OPEN
Frontend and compute are replaceable layers
Use GeoLibre/MapLibre, the ArcGIS Maps SDK, custom clients, browser Python, server Python or other sidecars without changing the service contract.
Compatibility is a migration strategy, not a claim of vendor affiliation.
3DGeoServEngine implements and consumes documented service patterns so existing GIS clients and applications can transition incrementally. Compatibility should be validated against each organization’s actual layers, editing workflows, renderers, security rules and extensions.