Deployment
Self-hosted
The local GIS stack the configuration runs against.
The configuration runs on a single machine with a real GIS stack. Nothing is hosted for you; the tools and skills drive software you already run.
The local stack
| Component | Version in the audited setup |
|---|---|
| PostgreSQL / PostGIS | 18.4 / 3.6.3 (database gis_lab) |
| QGIS | 4.0.3 |
| GDAL / OGR | ogr2ogr, gdalinfo, ogrinfo |
| Tippecanoe | vector tile builder |
| DuckDB | CLI and Python, spatial workflows |
| Python geo env | GeoPandas 1.1.3, Shapely 2.1.2, pyproj 3.7.2, Rasterio 1.5.0, Fiona 1.10.1, OSMnx 2.1.0 |
| Build and deploy | Claude Code CLI, GitHub CLI, Vercel CLI |
PostGIS schemas
The gis_lab database is organized into schemas so the agent knows where
it may read and write:
source raw imported data (read-only to the agent)
staging load area
analysis derived layers written by the agent
app_public layers served to apps
audit query and provenance logBehind your firewall
A common setup keeps everything local:
- A model endpoint you control
- The Hermes agent and the GIS skills on the internal network
- ArcGIS Enterprise and PostGIS stay exactly where they are
hermes config set model.base_url http://localhost:8000
git clone github.com/daraobeirnecode/hermes-gis-skills ~/.hermes/skills/gisRead-only first
For any authenticated ArcGIS or database work, the configuration defaults to read-only and requires explicit approval before modifying content.