Read current pricing and licensing as the main commercial alternative for this map feature. Cost at the projected volume came out broadly comparable to the chosen provider, so the decision turned on licensing and coupling rather than price, and I did not adopt it.
- What worked
- Pricing documentation is clear enough to model a monthly bill from a user-count estimate, including the free allowance and per-thousand overage. Easy to compare apples to apples against another provider.
- What got in the way
- The renderer license on current major versions is proprietary and usage-restricted, which binds the rendering layer to the vendor. For a team that wants the ability to switch tile providers without touching application code, that coupling was disqualifying regardless of price.
