Reading HERE's price list line by line
HERE publishes fragments of its pricing across a support page, a sign-up flow and a handful of resellers. Here is what the public numbers actually say, where they disagree, and how we reconciled them into a rate card.
The hardest part of pricing against HERE Technologies is not the arithmetic. It is that their published numbers live in three different places, two of which require an account, and the third of which is a support-plan table that most people never find.
What is actually public
Three things are genuinely public without signing in: the support-plan table with its monthly floors, the free-tier allowances quoted in developer documentation, and a per-transaction geocoding rate that appears consistently across independent trackers. Everything else is either behind the sign-up wall or quoted per deal.
- Support plans: $50, $525 and $2,200 a month, or 9% of licence fees on the middle two, whichever is greater
- Free allowances: 30,000 geocoding and map transactions, 5,000 routing, 2,500 matrix, 500 tour optimisations
- Geocoding: $0.88 per 1,000 up to five million, dropping to $0.70 between five and ten million
Where sources disagree
Independent trackers publish $1.00 per 1,000 for geocoding where HERE's own documentation and two resellers say $0.88. Vector tiles show up as both $0.50 and $0.088 per 1,000. Neither pair is a contradiction once you notice that one number is the entry rate and the other is the volume rate — but you only notice that if you read four sources.
We modelled it as a ladder: $0.50 below a million tiles a month, $0.088 above. That reconciles both figures and matches how every other service on their list behaves.
The April increase
On 1 April 2026 HERE raised Base Plan and pay-per-transaction pricing by roughly 6% for new contracts, renewals and extensions. Existing contracts hold until renewal. Our rate card reflects the post-increase list, which means anyone still on a pre-April HERE contract is comparing against a slightly lower number than the one we halve.
Why we publish the reconciliation
Because a discount claim you cannot check is marketing. The rate card is generated from a table of HERE's published figures multiplied by a single constant, each row carries its source and retrieval date, and a test in our build fails if any row stops being exactly half. If we got a number wrong, it is wrong in public where someone can tell us.