// the find
go-spatial/tegola
Tegola is a Mapbox Vector Tile server written in Go
Tegola is a vector tile server that reads from PostGIS, GeoPackage, or SAP HANA and serves Mapbox Vector Tiles (MVT spec v2). It handles geometry processing (clipping, simplification, make-valid) natively in Go, or can offload that to PostGIS via ST_AsMVT. Target audience is GIS developers who need a self-hosted tile server without paying for a managed service.
- ST_AsMVT support via the mvt_postgis provider is a smart performance win — letting the database do the geometry encoding avoids double-serialization and is notably faster at scale than the native Go pipeline.
- Cache backend selection is genuinely useful: file, S3, Redis, Azure Blob, and GCS are all there, and build tags let you strip out the ones you don't need so the binary stays lean.
- The native Go geometry pipeline (Douglas-Peucker simplification, Sutherland-Hodgman clipping, makevalid) is non-trivial work and means you can run it without PostGIS at all using GeoPackage files.
- AWS Lambda support and configurable build tags (noGpkgProvider, noS3Cache, etc.) make it practical to deploy in constrained environments where CGO or specific cloud SDKs are unwanted.
- The native geometry pipeline (maths/makevalid, maths/clip) is visibly complex and has known edge cases — the testdata directory full of UUID-named failing polygon fixtures suggests this code has historically been fragile and is not easy to reason about.
- No support for dynamic vector tile sources beyond SQL queries: there's no way to serve GeoJSON files, FlatGeobuf, or call an external WFS. If your data isn't in PostGIS or a GeoPackage, you're writing a new provider from scratch.
- The README says Go 1.26.2 is required but that version doesn't exist yet (latest stable is 1.22.x), which is a documentation error that will confuse anyone trying to build from source.
- Activity has slowed — 1,489 stars but the contributor base is small, issues referencing edge-case geometry bugs go unanswered for months, and there's no roadmap. Projects depending on it should be prepared to maintain forks.