1. Market context and key disruptors
The location-technology market is no longer shaped only by competition between traditional digital-map providers. Several forces are changing the economics of the sector. Google Maps remains the benchmark for consumer place discovery, local search, reviews, photos, opening hours and everyday POI richness, making it difficult for HERE or TomTom to compete on consumer depth alone. Mapbox pressures both companies from the developer-experience and design side, especially where customers want custom visual maps, branded interfaces, flexible styling and product-led map experiences. Overture Maps Foundation and OpenStreetMap are changing the cost and availability of base-map data, which pushes commercial players to prove the value of their proprietary layers, validation pipelines, road attributes, routing logic, traffic data and automotive-grade reliability. Automotive demand is another pressure point: map providers tied to OEM contracts are exposed to car-production cycles, delayed model launches and the shift toward software-defined vehicles. At the same time, AI-assisted mapmaking, sensor-derived observations, cloud marketplaces, EV routing, ADAS, fleet electrification and privacy-sensitive deployment models are opening new areas of differentiation. HERE and TomTom are therefore not only competing with each other; they are competing with open data, hyperscalers, developer-first platforms, consumer-map ecosystems and vertical workflow software.
2. Core positioning
HERE Technologies and TomTom are direct competitors in location technology. Both operate across maps, search, routing, traffic, automotive, EV, mobility, fleet/logistics and developer APIs. The practical distinction is that HERE is more naturally positioned as enterprise location infrastructure, while TomTom is more naturally positioned around maps, traffic, automotive navigation and driver-facing mobility experience.
HERE presents a platform for building, deploying and scaling location solutions, with solution areas around EV routing and charging, asset tracking, location analytics, fleet routing and professional navigation. TomTom presents a portfolio covering Orbis Maps, Places APIs, Routing APIs, Traffic APIs, Automotive Navigation, Navigation SDK, ADAS, EV Service, EV Routing, Tracking and Logistics APIs, hazard warnings and driver-navigation products.
The difference matters because customers rarely buy maps in isolation. A logistics team buys better routing and ETA quality. An OEM buys navigation, cockpit, safety and EV functionality. A developer buys APIs that are easy to integrate. A public-sector or enterprise customer may care more about privacy, deployment model, data control and long-term platform reliability.
3. Main comparison
| Dimension | HERE Technologies | TomTom | What it means |
| Core logic | Location services, map data, routing, fleet operations, self-hosting, anonymization and location analytics. | Maps, navigation, routing, traffic, automotive mobility, EV, places/search and driver-facing services. | HERE is more infrastructure and data-layer oriented; TomTom is more mobility and navigation-experience oriented. |
| Routing and fleet | Stronger enterprise story around fleet routing, professional navigation, EV-aware route planning and operational workflows. | Strong routing, Navigation SDK, EV routing, traffic-aware mobility and Tracking/Logistics APIs. | HERE fits operational routing better; TomTom fits navigation and traffic-aware mobility better. |
| Traffic intelligence | Traffic supports routing, fleet and dynamic location workflows. | Traffic APIs, Traffic Analytics, traffic data and mobility-intelligence products are highly visible. | TomTom has the clearer public traffic story. |
| Automotive and cockpit | Credible in automotive-grade maps, ADAS, EV, automated-driving and software-defined-vehicle contexts. | Automotive Navigation, Orbis Maps for Automated Driving, ADAS SDK and RoadCheck are productized. | Both are strong; TomTom’s cockpit and navigation story is easier to identify publicly. |
| Privacy and deployment | Stronger public evidence around self-hosting and anonymization-oriented infrastructure. | No direct equivalent was visible in the reviewed public product structure. | HERE is stronger where data control and deployment architecture matter. |
| Places and local search | Geocoding, search and POI capabilities exist, but the story is less consumer-discovery oriented. | Places APIs and search are more visibly named and packaged. | Neither equals Google Maps’ consumer place ecosystem of reviews, photos and mass local feedback. |
4. Core strengths and product logic
HERE is strongest when location technology is treated as infrastructure: APIs, routing engines, location data layers, analytics, enterprise integration, deployment control and operational decision support. Its fleet-route-planning story is important because it links routing, traffic, driver hours, EV range and charging constraints. That points to logistics, field operations and professional-navigation buyers rather than only consumer map users.
TomTom is strongest where the buyer problem is navigation, traffic intelligence, automotive mobility or driver experience. Its public offer is easier to read as a mobility stack: maps, Places APIs, Routing APIs, Traffic APIs, Automotive APIs, Automotive Navigation, ADAS, EV services, speed restrictions, hazard warnings, sat navs and in-dash navigation. This does not make TomTom less enterprise-grade; its public identity is closer to vehicles, movement, traffic and navigation experience.
5. Data and map-building logic
Both companies rely on mixed data ecosystems and compete on map coverage, freshness, POI quality, road attributes, traffic modelling, routing logic, automotive-grade reliability, API performance and licensing.
TomTom links Orbis Maps to TomTom data layers plus open data from Overture Maps Foundation and OpenStreetMap. This is strategically important because open map data reduces the defensibility of raw base-map coverage. TomTom’s challenge is therefore to show that its proprietary enrichment, traffic data, validation, routing logic and automotive layers create value beyond open-data aggregation.
HERE emphasizes platform-scale location data, digital mapping, navigation technologies, vehicle probe and sensor datasets, and AI-assisted mapmaking. Its map story is less about consumer discovery and more about operational reliability, enterprise integration and location intelligence.
The useful distinction is communication: HERE frames map capability as enterprise infrastructure; TomTom frames it through maps, traffic, navigation, automotive and driver-facing use cases.
6. Business and channel logic
TomTom’s commercial structure is clearer because it reports Location Technology and Consumer. Location Technology sells through Automotive, mainly OEMs and Tier 1 suppliers, and Enterprise, covering public and private-sector customers. Consumer covers portable navigation devices and mobile applications.
HERE does not disclose the same channel segmentation, but its routes to market are visible through direct enterprise sales, the HERE Developer channel, AWS Marketplace / HERE on AWS, the partner ecosystem, automotive and SDV partnerships, and integrations such as SAP.
For a market reader, the distinction is useful. TomTom’s channel language is more explicitly segmented by business line and customer type. HERE appears more ecosystem and platform-driven, with routes into enterprise, developers, cloud marketplaces, partners and automotive software environments.
7. Best fit by use case
| Buyer need | Better fit | Reason |
| Enterprise location-services infrastructure | HERE | Stronger when buyers need APIs, data layers, routing logic, analytics, deployment control and enterprise integration. |
| Fleet routing and professional navigation | HERE | Better fit for operational routing, mixed fleets, EV-aware constraints and professional navigation. |
| Traffic and mobility intelligence | TomTom | Clearer public story around traffic data, traffic analytics, routing and mobility intelligence. |
| Automotive navigation, cockpit and safety | Balanced; TomTom clearer publicly | Both are credible; TomTom is more visibly packaged around navigation, driver-facing services and safety alerts. |
| EV routing and charging | Balanced, split by context | HERE fits EV-aware fleet and platform routing; TomTom fits EV navigation, charging discovery and automotive EV experience. |
| Location analytics and spatial enrichment | HERE | HERE has the clearer enterprise story around location analytics and operational location data. |
| Privacy-sensitive location workflows | HERE | Stronger public evidence around self-hosting, anonymization and data-governance-sensitive use cases. |
| Full vertical workflow software | Depends on vertical specialist | Both provide location layers; site selection, dispatch, TMS or retail analytics often need specialist software on top. |
8. Public-review and brand perception context
Public reviews are limited evidence, but they are useful for identifying recurring frustrations around routing, traffic accuracy, app experience, map errors, POI quality and update delays.
TomTom has more public consumer-navigation visibility because of navigation apps, sat navs, maps and service updates, and driver products. HERE’s public perception is less consumer-led and more platform and enterprise-led. Its reputation is more likely to be judged through documentation quality, developer experience, marketplace presence, partner integrations, API reliability and enterprise referenceability.
The difference is therefore not only technical. TomTom is easier for ordinary drivers and app users to judge. HERE is easier for enterprise buyers, developers and integration partners to judge.
9. Potential improvements
• Map freshness and correction transparency: both companies could communicate more clearly how reported road changes, restrictions, POIs, speed limits and access rules are validated and reflected in live products.
• Local place richness: both offer search, geocoding and place capabilities, but neither has the consumer visibility of Google Maps for reviews, photos, opening hours and everyday discovery. This matters even in enterprise applications.
• Design-led map-building: HERE and TomTom are strong location-technology platforms, but customers building branded interactive map products may still look to Mapbox-style environments for styling control, custom layers, icons, fonts and product experience.
Final takeaway
HERE and TomTom are close competitors, but their strongest public stories differ.
HERE is stronger where the buyer needs enterprise location infrastructure: fleet routing, location analytics, asset tracking, EV-aware operations, platform services, professional navigation and data-governance-sensitive workflows.
TomTom is stronger where the buyer needs maps, traffic intelligence, automotive navigation, EV navigation, driver-facing services, safety alerts and mobility experience.
The market pressure comes from several directions at once: Google on consumer place richness, Mapbox on design and developer experience, Overture and OpenStreetMap on open-data economics, cloud platforms on distribution, and automotive volatility on OEM-linked revenue. That is why the comparison should not be reduced to who has better maps. The stronger question is: which company is better embedded in the workflow where location data becomes a business decision?
Methodology and source basis
This report is based on company websites, product pages, documentation, financial reporting and selected external market signals. It is a strategic positioning and product-comparison analysis, not a technical audit, pricing benchmark or verified customer-satisfaction study.
