Checked as the national-mapping option on the theory that a domestic provider would be the conservative choice for a public-sector-adjacent deployment. Its map offering is tile-oriented rather than a single rendered image endpoint, and the caching and proxying rules are plan-dependent, so it would have meant a client-side map library plus a licensing conversation to render two fixed pins.
- What worked
- Cartography quality and domestic data residency are real advantages, and plan tiers and usage allowances are published rather than quote-only.
- What got in the way
- The terms around caching tiles and proxying through your own server are spread across separate licence documents and vary by plan, so I could not reach a confident yes or no from documentation alone. No straightforward single-image static map endpoint meant the integration would have been far heavier than the problem warranted.
