Pricing overview

HERE Technologies employs a multi-tiered pricing structure designed to accommodate various usage levels, from individual developers to large enterprises. The model is primarily based on transactions, where a "transaction" typically refers to a single API call or data request. This approach is common among location-based service providers, including alternatives like Google Maps Platform pricing, which also uses a pay-as-you-go model for most services.

The core of HERE's pricing strategy involves a generous free tier, followed by tiered paid plans that offer increasing transaction volumes at a set monthly fee. Beyond these included transactions, an overage rate applies, allowing costs to scale with demand. This structure aims to provide predictability for common use cases while ensuring flexibility for unexpected spikes in usage. Enterprise customers can negotiate custom agreements, which often include dedicated support, specialized services, and tailored pricing for high-volume or unique requirements, as detailed on the HERE pricing page.

The transaction types that count towards usage vary by specific API or SDK used. For example, a request to the Geocoding API to convert an address to coordinates would count as one transaction, as would a route calculation request or a map tile load. Developers are encouraged to review the API reference documentation for precise definitions of transaction counting for each service.

Plans and tiers

HERE Technologies offers several plans, each designed to meet different operational scales and provide clear cost structures. These plans include a Freemium tier, a Pro plan, and custom Enterprise solutions. The primary differentiator between plans is the monthly allowance of transactions and the associated cost per transaction beyond the included limits.

Plan comparison

Plan Monthly Price Included Transactions/Month Overage Rate (per 1,000 transactions) Key Features & Best For
Freemium $0 250,000 $1.00 Prototyping, development, low-volume applications, personal projects.
Pro $49 500,000 $0.70 Small to medium-sized businesses, production applications with moderate usage, startups needing more capacity.
Enterprise Custom Custom Custom Large-scale deployments, high-volume commercial applications, specific SLA requirements, dedicated support, specialized services.

The Pro plan includes a base number of transactions and then charges for additional usage. For instance, if a Pro plan user exceeds 500,000 transactions in a month, each additional 1,000 transactions would cost $0.70. This tiered structure aims to offer a predictable base cost while allowing for scalable growth without requiring an immediate jump to a higher fixed plan if usage fluctuates. For detailed pricing specifics and any potential regional variations, consulting the official HERE pricing page is recommended.

Free tier and limits

The HERE Technologies Freemium plan provides a substantial free tier, allowing developers to utilize up to 250,000 transactions per month without any charge. This tier is designed to enable extensive prototyping, development, and even deployment of low-volume applications. The 250,000 transactions per month limit is generally sufficient for many personal projects, small-scale internal tools, or the initial stages of a startup's product development, as outlined in the HERE pricing details.

Beyond the included 250,000 transactions, the Freemium plan charges an overage rate of $1.00 per 1,000 transactions. This means that if a user on the Freemium plan performs 251,000 transactions in a month, they would incur a charge of $1.00 for the extra 1,000 transactions. This pay-as-you-go approach helps manage costs if usage occasionally exceeds the free limit without committing to a paid plan immediately.

The free tier applies across most of HERE's core Location Services, including geocoding, routing, mapping, and search APIs. However, certain specialized services, such as highly granular traffic data or specific advanced analytics features, may have different pricing models or may not be fully available within the free tier. Developers should always verify the specific service's transaction counting and free tier eligibility in the HERE API reference documentation.

Real-world cost examples

To illustrate the HERE Technologies pricing model, consider several hypothetical scenarios:

  1. Scenario 1: Small Development Project
    • Usage: 150,000 geocoding requests per month.
    • Plan: Freemium.
    • Cost: $0.00. This usage falls well within the 250,000 free transactions, resulting in no charge.
  2. Scenario 2: Growing Startup Application
    • Usage: 350,000 routing requests per month.
    • Plan: Freemium.
    • Cost Calculation: 250,000 free transactions + 100,000 overage transactions. Overage cost: (100,000 / 1,000) * $1.00 = $100.00.
    • Recommendation: At this usage level, upgrading to the Pro plan ($49/month for 500,000 transactions) would be more cost-effective as it covers the usage for less than the Freemium overage.
  3. Scenario 3: Medium-Sized Logistics Application
    • Usage: 750,000 map tile loads and 200,000 routing requests per month (total 950,000 transactions).
    • Plan: Pro.
    • Cost Calculation: Base Pro plan cost: $49.00 (includes 500,000 transactions). Overage transactions: 950,000 - 500,000 = 450,000. Overage cost: (450,000 / 1,000) * $0.70 = $315.00.
    • Total Monthly Cost: $49.00 + $315.00 = $364.00.
  4. Scenario 4: High-Volume Automotive Solution
    • Usage: 10 million transactions per month across various services.
    • Plan: Enterprise.
    • Cost: Custom pricing, negotiated directly with HERE Technologies. This would involve a tailored agreement, potentially with a lower per-transaction cost than standard Pro plan overages and specialized support.

These examples highlight how the transaction-based model scales. It is crucial for developers to monitor their API usage, often through the developer portal's analytics tools, to optimize costs and select the most appropriate plan.

How the pricing compares

HERE Technologies's pricing model is comparable to other major geospatial API providers, typically featuring a free tier and subsequent usage-based billing. Key competitors like Google Maps Platform and Mapbox also offer freemium models, but the specific transaction definitions, included volumes, and overage rates can differ significantly.

  • Google Maps Platform: Google Maps Platform provides a free tier that includes $200 of monthly credit, which translates to varying numbers of free requests depending on the specific API (e.g., 40,000 free map loads for Dynamic Maps, 20,000 free geocoding requests). After the free credit, costs are calculated per 1,000 requests, with rates that vary widely by service. For example, Geocoding API calls might cost $5.00 per 1,000 requests after the free tier, as detailed on the Google Maps Platform pricing page.
  • Mapbox: Mapbox also employs a freemium model with a set number of free units for various services (e.g., 50,000 map loads, 5,000 geocoding requests, 100,000 tiles per month). Beyond the free limits, Mapbox charges per unit, with pricing tiers that reduce the per-unit cost as volume increases. For instance, after the free tier, map loads might start at $5.00 per 1,000, and geocoding requests at $10.00 per 1,000. Their pricing page provides detailed breakdowns.
  • TomTom Developer: Similar to HERE, TomTom offers a free tier, typically around 2,500 free transactions per day (approximately 75,000 per month). After the free tier, pricing is usage-based, with rates that vary by API and volume. For example, their Geocoding API might cost around $0.75 per 1,000 requests for standard volumes, as described on the TomTom Developer pricing page.

While HERE's free tier of 250,000 transactions per month is competitive, especially for early-stage development, direct cost comparisons require careful consideration of the specific services used, the definition of a "transaction" for each provider, and the actual volume of usage. For instance, a single "map load" might be counted differently by HERE versus Google Maps Platform. Developers should perform a detailed analysis based on their projected usage patterns across specific APIs to determine the most cost-effective solution for their particular application.