tilegroxy Docs
GitHub Issues Get tilegroxy

Your Maptile gateway

One tile API in front of every map source you use.

Tilegroxy shines when your application consumes geospatial data from multiple sources. Instead of being tied to a specific backend, it can pull data from any protocol, whether the standard initialisms or a proprietary, authenticated API. Tilegroxy allows you to provide access to all your maps through a single entry point with uniform authentication, caching, CORS rules, logging, and tracking, all while protecting your keys and upstream providers.

tilegroxy.yml

  • YAML

  • JSON

server:
  production: false
layers:
  - id: osm
    provider:
      name: proxy
      url: https://tile.openstreetmap.org/{z}/{x}/{y}.png
{
  "server": { "production": false },
  "layers": [
    {
      "id": "osm",
      "provider": {
        "name": "proxy",
        "url": "https://tile.openstreetmap.org/{z}/{x}/{y}.png"
      }
    }
  ]
}

  • Binary

  • Container

tilegroxy config check
tilegroxy serve
docker run --rm -p 8080:8080 -e SERVER_BINDHOST=0.0.0.0 -v ./tilegroxy.yml:/tilegroxy/tilegroxy.yml:Z ghcr.io/michad/tilegroxy serve

  • Start Quickstart Proxy tiles from OpenStreetMap with a single-layer config.

  • Reference Configuration Layers, providers, caches, authentication, server and telemetry.

  • Learn by example Examples Complete configurations, from a vector basemap to multi-tenant imagery.

  • CLI Commands serve, seed, test, and config create / check / diff.

Features

Sources

  • Proxy to ZXY, WMS, TMS, WMTS, or other protocol map layers

  • Raster tiles plus Mapbox Vector Tile (MVT) and MapLibre Tile (MLT) vector formats

  • Act as an HTTP server for MapServer and other CGI tile generators

  • Custom providers for non-standard and proprietary imagery sources

Transform
Cache
Secure
Operate