Tiles with a style you control
Day and night styles ship ready and the style document is open, so the head-unit look is a design decision rather than a vendor default.
Automotive
Connected-car maps, priced like an API.
For aftermarket units, connected services and fleet OEM programmes, the map is a tile request and the traffic is a feed. Where this does not fit — offline embedded stacks and lane-level HD — the honest answer is that HERE still owns that ground.
How it is usually put together
Traffic on the same graph
Flow and incidents reference the same links the router uses, so the arrival estimate and the highlighted jam agree.
One key across the fleet
Scoped keys per programme with per-service quotas, rotated without a firmware release.
A modelled month
$291,799.44 you keep
Illustrative volumes for a business of this shape, priced with the same calculator as the pricing page. Both columns apply the free allowances first.
| Service | Monthly volume | On HERE's list price | On ApiNavi |
|---|---|---|---|
| Places & autosuggest | 2M | $3,940.00 | $1,970.00 |
| Routing | 7.5M | $11,242.50 | $5,621.25 |
| Vector tiles | 120M | $10,957.00 | $5,478.50 |
| Traffic | 9M | $22,493.75 | $11,246.88 |
| per month | $48,633.25 | $24,316.63 |
These volumes are modelled, not measured from a customer. They exist so the arithmetic is visible — put your own numbers into the calculator.
What to watch
- No offline embedded stack: this is a connected pattern, not a head-unit SDK
- No lane-level HD content for automated driving
- Tile caching policy on the device changes the bill by an order of magnitude — model it early
Run your own numbers
The calculator takes your call volumes and prints both columns.