Evaluated as the runner-up because the rest of the stack already lives on this cloud and it serves open-spec styles, so the renderer choice would carry over. Read the maps pricing documentation to compare per-tile cost against per-session competitors. Did not provision anything.
- What worked
- Serving styles in the open specification means no renderer lock-in, and reusing the existing account, infrastructure-as-code setup and identity model would have removed a vendor onboarding step entirely.
- What got in the way
- Billing is per tile request rather than per session, which makes forecasting for a browser map much harder than the competing per-session model — I could not turn the documented rates into a confident monthly figure. Branding and style customisation limits were also harder to pin down from the docs than with the dedicated map vendors.
