Neoserver is an open-source geospatial server written in Go that publishes maps, vector features, raster coverages, and tiles from PostGIS, DuckDB, and common file formats (GeoParquet, GeoJSON, GeoPackage, GeoTIFF/COG). It implements a broad set of OGC protocols - WMS 1.3.0, WFS 2.0 (2.0.0 and 2.0.2), WCS 2.1/2.0.1, WMTS 1.0, OGC API Features and OGC API Tiles - plus Mapbox Vector Tiles and TileJSON. Feature writes require PostGIS; optional capabilities depend on service settings and published test evidence is explicitly not an OGC product certification. Data stays in its configured sources while Neoserver layers, styles, credentials and service settings are isolated per workspace, and a browser console provides guided publishing, live previews and discovery.
Deployment and operations are designed for production use: a Docker image (tobilg/neoserver:0.2.0) bundles the console and native geospatial libraries, and the server supports API-first automation, scoped API keys, OIDC, workspace roles, layer-level access control, resource limits, seeding of persistent tile caches and telemetry export. Documentation and step-by-step guides cover common workflows - WMS/WFS from PostGIS or DuckDB, raster subsetting with WCS, vector tiles and caching, GeoParquet/DuckDB workflows without a DB server, and comparisons with other servers. The project is MIT-licensed and intended for teams that want an OGC-compliant, workspace-isolated publishing platform they can run in their own infrastructure.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.