Why Stadia Maps Instead of OpenStreetMap Tiles

For the photo world map I wanted OpenStreetMap data from an EU server without running a tile server myself. Stadia Maps met every criterion.

When I added the photo world map, the first question was where the map tiles come from. "Just use OpenStreetMap" sounds like the answer, but it isn't that simple.

Why not the OSM tile servers

OpenStreetMap runs its own tile server at tile.openstreetmap.org. It works, but the Tile Usage Policy rules it out for production sites with real traffic. The data is free for everyone; the servers are not. In detail:

  • No systematic use for commercial or busy sites.
  • A Referer and a User-Agent are required, so abuse can be traced.
  • Requests can be throttled or blocked at any time when resources run short.

The OSM Foundation lives on donations. If you want to embed maps seriously, you either host tiles yourself or use a provider that does it and gives something back to OSM.

My criteria

I held the tile service to the same bar as the rest of the site:

  1. Served from Europe. The endpoint processes requests in the EU, without a detour through the US.
  2. GDPR-friendly. A data processing agreement (DPA), and no cookies, trackers or fingerprinting through the tiles.
  3. OSM base data. The same cartography as OSM, because I like it and the licence (ODbL) is clear.
  4. A free tier. A personal site should cost nothing at hobby scale.
  5. No infrastructure of my own. Self-hosting tiles (tileserver-gl with OpenMapTiles data) would turn a small photo section into an infrastructure project.

Why Stadia Maps

Stadia Maps is a small US provider focused on privacy and OSM data. What decided it:

  • EU endpoint tiles-eu.stadiamaps.com. The browser connects only to servers in the EU. Stadia says it strips personal data at the edge before a request reaches services in other regions.1
  • Documented GDPR compliance. There is a DPA, and requests are counted by the Referer header, not by cookies or fingerprints. The privacy policy says there are no third-party scripts, only tile images.
  • OpenMapTiles and OSM. The styles (I use alidade_smooth) are drawn from OSM geometry, and both OSM and OpenMapTiles appear in the map's attribution.
  • 200,000 tile requests a month for free. An embedded map on my scale lands somewhere in the four or five figures. The free plan is for non-commercial use only (as of November 2026).2
  • Authentication by domain. There is no API key in the browser code; Stadia checks the Referer instead. That is also why the map needed two CSP fixes.

The alternatives

  • Mapbox: US-based without an EU endpoint. Legally workable (SCCs, the EU-US Data Privacy Framework), but more paperwork than I want for a hobby site.
  • Google Maps: tracking and cookies as soon as its script loads. That breaks my rule of no third-party requests.
  • MapTiler: Swiss, hosted in the EU, and my second choice. The free tier is lower (as of November 2026: 100,000 API requests and 5,000 map sessions a month, non-commercial) and the style a bit too colourful for me.3
  • Self-hosting with tileserver-gl and an OpenMapTiles dump was the most honest option. It failed on disk space (the planet dump is about 90 GB) and on the work of keeping it up to date.

Takeaways

  • The OSM tile servers are community infrastructure, not a general API. Embedding them on a production site hurts the project or gets you throttled.
  • For the GDPR the server location matters more than the company's seat. An EU endpoint plus a DPA makes a US provider manageable.
  • Stadia Maps says it passes part of its revenue on to OpenStreetMap. If I ever outgrow the free tier, the fee goes partly back to the data I use.

More on this

Topic
  • OpenStreetMap Freely usable world map, mapped by volunteers since 2004. The data is licensed under the Open Database License.
Mentioned in
Mentioned
  • Stadia Maps Map tile service built on OpenStreetMap data, with an EU endpoint and authentication by domain instead of an API key.

Show in the graph view →