neoserver connects your data sources to standards-based maps, features, coverages, and tiles. Start in the browser, automate through the management API, and run the server on your own infrastructure.
Publish your first dataset
Follow the illustrated console tutorial, from an empty catalog to a working client connection.
Start with the console →Automate with the API
Initialize the server, create a workspace, and publish data using HTTP requests.
Start with the API →Connect your data
PostGIS, DuckDB Spatial, GeoParquet, vector files, rasters, and mosaics.
Explore data sources →Deploy and operate
Persistence, reverse proxies, encryption keys, health checks, backups, and upgrades.
Read the deployment guide →OGC services
Find endpoints, operations, query examples, and supported capabilities for your clients.
Explore service documentation →Management API reference
Browse every endpoint and schema without starting a server.
Open the API reference →How it fits together
A workspace contains your data connections, publications, styles, access rules, and service settings. A store connects to a source. A layer or coverage publishes selected data through the enabled OGC services.
The console calls the same management API available to your scripts. Configuration and security state live in an encrypted catalog; feature data stays in its configured source systems.
Choose your next step
- Sign in to the administration console
- Create a workspace and configure its services
- Understand credentials and access control
- Troubleshoot a connection or publication
- Contribute to neoserver
These guides and screenshots describe the pinned project revision. Check the release notes before upgrading an existing deployment.