I built GeoLens: a self-hosted geospatial catalog and map builder (PostGIS, vector tiles, one docker compose)

GeoLens is an internal catalog and map builder for spatial data. Drop in a vector or raster file, or connect a WFS, OGC API Features, or ArcGIS service, and the data lands in PostGIS, tiled and searchable. Build a map from those layers in the browser and share it by link or embed.

I built this because the small GIS teams I worked with were paying ArcGIS Online or Mapbox to host data that never needed to leave their own server. Vendor lock-in is what GeoLens avoids.

Live demo, no signup to browse: https://demo.getgeolens.com

Stack: FastAPI, PostgreSQL 18 with PostGIS as the single source of truth. The job queue lives inside Postgres, so there is no broker to run. React with MapLibre on the front, Titiler for raster tiles, MinIO or S3 for files, Valkey for the tile cache. It serves OGC API Features and Records, STAC, and DCAT, so QGIS can read the catalog directly.

Install and run with docker-compose:

curl -fsSL https://getgeolens.com/install.sh | sh

Docs: https://docs.getgeolens.com

Footprint: the public demo ran on a 2 vCPU / 8 GB VM for the past month. A small VPS is the target, not a Pi.

AI involvement: Claude Code and Codex wrote a lot of the implementation and did review passes. The architecture and product calls are mine, and I read what ships.

License: Apache 2.0

Repo: https://github.com/geolens-io/geolens

Happy to answer anything about the stack or the choices