HERE connects its live-map promise to production automotive scale, quantified tour-planning outcomes and controlled deployment, while TomTom makes its Orbis architecture, traffic portfolio and developer buying path more explicit; HERE therefore has the stronger product-marketing case for high-stakes automotive, fleet and privacy-sensitive enterprise decisions, with TomTom leading in evaluation transparency for open map data, traffic and self-service APIs.

Companies

HERE Technologies traces its mapping business to 1985 and operates as a privately held location-technology company backed by automotive, technology and telecommunications shareholders. It reports more than 8,000 employees across 52 countries. Its current corporate story centers on a unified live map, location services and software used in automotive, logistics and enterprise applications. Because HERE is private, it does not publish a revenue split comparable with TomTom’s segment reporting.

TomTom was founded in the Netherlands in 1991 and is listed on Euronext Amsterdam. It reports roughly 3,300 employees in more than 30 offices. The business has evolved from consumer navigation devices toward location technology for automotive and enterprise customers while retaining a smaller Consumer segment. For 2025, TomTom reported €554.7 million in revenue: €481.8 million from Location Technology and €72.9 million from Consumer. Within Location Technology, Automotive generated €322.9 million and Enterprise €158.9 million.

Market context and key disruptors

Commercial map providers now compete across several layers: base-map data, continuously updated road attributes, traffic observations, search and places, routing logic, navigation software, automotive-grade content and workflow-specific applications. OpenStreetMap and the Overture Maps Foundation reduce the scarcity of global base data. Overture’s transportation release alone describes tens of millions of road kilometers in an open schema. Commercial differentiation therefore depends increasingly on validation, refresh speed, licensing clarity, proprietary observations, production reliability and the ability to convert map data into decisions.

Google remains a demanding benchmark for consumer place discovery because its Places data model includes reviews, photos and opening hours. Mapbox exerts pressure from the design and developer side through Studio, custom styles and composable map experiences. Vehicle software adds another test: software-defined vehicles, EV routing, ADAS and automated-driving programs require long production cycles, regulated update processes and stable map standards. UNECE cybersecurity and software-update rules and standards such as NDS raise the value of auditable, production-ready delivery. Logistics buyers meanwhile judge location technology through delivery cost, service levels, truck constraints, replanning and integration with transport systems. These forces reward proof tied to a specific operational result, not broad coverage claims alone.

Buyer personas and decision criteria

Automotive product or program leader. The trigger is a new vehicle platform, navigation stack, ADAS function, EV experience or regulatory milestone. Vehicle-program and procurement budgets fund the decision. Coverage, NDS compatibility, update reliability, security, cockpit integration and production references dominate evaluation. Credible proof includes deployed vehicles, OEM references, certification and release performance.

Digital product and engineering leader. A new app, geographic expansion or provider migration creates demand. Product and engineering teams sponsor the purchase, while developers influence selection. They test API consistency, documentation, pricing, styling, latency, quotas and SDK quality. A working trial, transparent unit economics and migration guidance carry more weight than category language.

Fleet or logistics operations leader. Cost pressure, missed service windows, electrification or route complexity initiates the project. Operations and IT share ownership. The buying test covers vehicle constraints, time windows, ETA quality, dynamic replanning, driver execution and integration. A pilot against historical routes and measured on-time or cost improvement is the preferred proof.

Data, security and procurement approver. This group enters when location data is sensitive, usage is large or licensing is complex. It examines provenance, permitted use, residency, self-hosting, anonymization, service commitments and exit risk. Architecture documents, contractual terms, audits and a controlled proof of concept are decisive.

Positioning and messaging hierarchy

HERE Technologies

HERE’s homepage leads with a live map designed to power real-world AI, then routes buyers toward driver experience, automated driving, fleet routing and enterprise uses. The platform pages translate that promise into maps, data, APIs, SDKs, analytics and a data marketplace. The strongest evidence sits below the corporate language: HERE reports map content in 238 million vehicles across more than 90 OEM brands; it documents self-hosted location services and a dedicated Anonymizer; and its METRO digital tour-planning case reports 97–98% on-time delivery, about 20% cost savings and a 37% increase in automated planning. Those proof points make automotive scale, operational optimization and controlled deployment believable.

The hierarchy becomes less precise when the company moves between a universal live map, AI, automotive, fleet and general enterprise location intelligence. A buyer can identify many capable modules, yet must assemble the path from the top-level promise to a defined workflow. Product marketing would benefit from more role-based evaluation paths and clearer public packaging for advanced services.

TomTom

TomTom starts with maps and location technology for businesses, developers and drivers. Its product navigation is comparatively explicit: Maps, Navigation, Traffic and Services lead to Orbis Maps, APIs, SDKs, automotive products, ADAS and traffic analytics. Orbis supplies a coherent architectural story by naming TomTom proprietary content, Overture data, selected OpenStreetMap sources, partner observations and customer data, then exposing the result through APIs, SDKs and map formats. Public pricing for core developer services shortens evaluation.

This clarity is qualified by a product transition. The Orbis APIs reached general availability in July 2026 with six initial APIs, while the company states that truck and other transport modes and some batch capabilities do not yet match the legacy portfolio. TomTom also warns developers not to mix Orbis and legacy products in one application. Its Waypoint Optimization API is scheduled for withdrawal on 31 May 2027 with no recommended migration path. The public taxonomy is strong; migration and capability-parity messages now need equal prominence.

Product portfolio and architecture

HERE groups its portfolio around map content and the HERE Platform, supported by routing, geocoding and search, map rendering, traffic, positioning, tour planning, analytics, SDKs, automotive map products, professional navigation, self-hosted location services and anonymization. HERE WeGo gives the company a consumer-facing navigation product, though the commercial case is primarily enterprise and automotive.

TomTom’s portfolio spans Orbis Maps, search, routing, traffic, map display, tracking and logistics APIs, Maps and Navigation SDKs, automotive navigation, ADAS software, RoadCheck, EV services, Traffic Analytics, Map Maker and consumer navigation products. The portfolio exposes distinct developer, enterprise and automotive access routes; advanced automotive products generally use request-access or enterprise sales rather than public pay-as-you-go purchase.

Feature and capability comparison

Buyer workflows and jobs to be done

The same feature can matter differently by workflow. The assessment below assigns a leader only where current public evidence supports one; technical accuracy and contract fitness still require a buyer-specific test.

HERE visibly owns constrained multi-vehicle planning and privacy-controlled deployment; TomTom visibly owns traffic evaluation and open-data composition. Both strongly claim automotive, navigation and EV workflows, where public marketing alone cannot rank technical performance. The full transport-management job remains outside either company’s core ownership. Public evidence is also thin for a complete location-data migration program covering dual running, historical data, contract exit and operational change management.

Data, integrations and ecosystem implications

HERE’s platform combines its map, traffic and location content with customer and partner data, APIs, SDKs, analytics and marketplace access. AWS distribution, SAP integration and automotive standards extend enterprise reach. Self-hosting can reduce exposure for controlled workloads, although deployment responsibility and support requirements increase implementation work. The platform’s proprietary center may also raise migration and contract-review effort for deeply embedded applications; that is a procurement inference, not a published switching-cost measure.

TomTom Orbis documents a mixed-source system: TomTom content, Overture, selected OpenStreetMap sources, partners, sensors and customer data. Overture-aligned schemas, standard map formats and bring-your-own-data support can improve interoperability and reduce dependence on a single raw-data source. Buyers still need to separate Orbis from legacy APIs, check feature parity and manage license conditions such as ODbL obligations. Openness improves inspectability; it does not remove governance or migration work.

Competitive narrative, sales enablement and win-loss signals

The competitive set changes by job. Google is strongest as a reference point for consumer places and discovery. Mapbox is prominent when product teams prioritize visual design and custom interaction. OpenStreetMap and Overture are viable inputs for organizations able to assemble validation, routing, traffic and operations themselves. Transport-management systems, last-mile platforms and traffic specialists can win when the buyer wants a finished vertical workflow rather than location components. Internal build remains an option for differentiated algorithms or data control, with substantial maintenance cost.

A useful discovery process asks which map attributes drive the decision; how quickly corrections must appear; which vehicle, traffic, EV or privacy constraints matter; whether open-source licensing is acceptable; where data may be processed; and how pricing behaves at expected volume. HERE should demonstrate Tour Planning against real constraints, self-hosted architecture, Anonymizer and automotive production evidence. Its sales team should be ready for objections about public pricing, portfolio breadth and proprietary integration. TomTom should demonstrate Orbis source layers, Map Maker, traffic analytics and the navigation or ADAS experience. It should address Orbis-versus-legacy selection, capability parity and the Waypoint Optimization retirement before a buyer discovers them during implementation.

Public commercial announcements show selections, renewals and partnerships for both companies, but disclose few controlled head-to-head outcomes. HERE’s METRO case is unusually useful because it reports operational metrics. TomTom’s annual reporting supplies segment revenue and automotive backlog, while commercial news supplies named relationships. Neither source set supports a defensible claim about overall win rate, technical accuracy or displacement of the other vendor.

Packaging, pricing and adoption friction

HERE’s current entry route is the Base plan with monthly free thresholds followed by pay-as-you-grow charges. Since April 2025, new customers must add a payment method; the earlier Limited plan is no longer the correct default for new accounts. Support tiers, higher-volume arrangements and specialized products introduce enterprise discussion. Self-hosted services add infrastructure, release-management and operational requirements that should be costed alongside license fees.

TomTom publishes free allowances and usage pricing for core developer products and offers custom enterprise arrangements. Automotive Navigation and advanced automotive programs require access requests or commercial engagement. The Orbis launch creates a second decision layer: teams must choose the correct product family, avoid unsupported mixing, confirm geographic and modal parity and plan migration. The announced retirement of Waypoint Optimization without a recommended replacement is the clearest current product-adoption risk in the comparison.

For both vendors, headline request prices are only part of total cost. Buyers should model tiles versus non-tile calls, peaks, storage and derived data rights, support, SLAs, map-display rules, data licenses, SDK maintenance, testing and migration. A production proof should use expected volumes and failure modes, with contract language for product retirement and data portability.

Business model, channels, acquisition and revenue logic

HERE sells through direct automotive and enterprise relationships, developer self-service, cloud channels such as AWS, technology partners and integrations such as SAP. Public materials indicate licensing, platform usage, support and solution delivery as likely revenue mechanisms, although HERE does not publish a comparable segment breakdown. Its shareholder base and long automotive history reinforce access to vehicle programs; its platform and partner routes broaden the enterprise funnel.

TomTom reports Automotive, Enterprise and Consumer revenue within a public-company structure. Automotive sells map and software products into vehicle programs; Enterprise serves private and public organizations; Consumer includes navigation devices and applications. Developer pricing supports product-led evaluation, while large-scale and automotive programs use direct sales and partners. Its reported automotive backlog gives investors visibility into contracted future activity, though backlog is not the same as recognized revenue.

Both use documentation, demos, customer stories, partner announcements, webinars and industry events to acquire and advance buyers. At CES 2026 and Auto China 2026, each company promoted automotive and AI-enabled map capabilities through demonstrations and partner conversations. Events can create executive access and technical evaluation opportunities, but attendance itself is weak evidence of product leadership.

Reviews and public perception

Public reviews are useful for finding hypotheses to test, not for ranking enterprise platforms. HERE WeGo reviewers describe positive offline-map and navigation experiences alongside complaints about routes, traffic, interface changes and individual map errors. TomTom app and Trustpilot reviewers praise aspects of traffic and navigation while also raising app changes, map updates, CarPlay behavior, subscriptions and support. Store, country, device, version and self-selection effects make these samples non-representative.

The asymmetry in public perception is structural. TomTom retains a visible consumer brand through apps and navigation devices, so ordinary drivers generate more product and service commentary. HERE is increasingly assessed through enterprise documentation, developer implementation, OEM deployments and partner references. Neither review surface verifies API reliability, global map accuracy, automotive safety performance or fleet return on investment. Buyers should convert recurring complaints into test cases and validate them in the relevant geography and release.

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 has the stronger overall product-marketing case for buyers whose decision depends on production automotive scale, constrained fleet planning or controlled location-data deployment. Its best claims connect to identifiable products and unusually concrete proof, including installed-vehicle scale, self-hosting, anonymization and METRO’s operating outcomes. The main weakness is evaluation architecture: the broad live-map and AI story needs shorter persona-based paths, clearer advanced-product packaging and more comparable proof across enterprise uses.

TomTom is stronger at making traffic products, developer pricing and Orbis data composition inspectable. Its Maps–Navigation–Traffic–Services structure helps buyers find a product, while Orbis documentation explains provenance and interoperability with useful specificity. The immediate product-marketing priority is to make portfolio transition risk as easy to understand as the new architecture: parity, unsupported combinations, migration timing and replacements should be visible before adoption. For automotive and EV programs, neither vendor wins on public evidence alone; a program-specific technical and commercial evaluation remains necessary.

Methodology

This comparison uses public company pages, current product documentation, financial reporting, customer stories and selected neutral standards and workflow sources reviewed through 26 July 2026. It evaluates product marketing, buyer fit and evidence quality. It does not constitute a technical benchmark, legal interpretation, price quote, representative customer-satisfaction study or verified head-to-head win-rate analysis.

Selected Sources