Territory management
Geomarketing analytics
Store locator for your website
Address to coordinates
Real-time address autocomplete
Embeddable map tiles
Single and multi-stop routing
Maps for transport & logistics
Full Placematic Spatial API overview
HERE Gold Partner — one contract, full support
Your savings vs Google Maps — free
Building fleet software or an ELD platform
Running a delivery network or distribution operation
Managing a multi-location retail or franchise network
Expanding a location network or planning new sites
Territory and route management for field teams
Adding location features to a software product
Assessing whether your fleet is ready to go electric
Pricing deliveries by distance, traffic and vehicle type
Building maps and navigation into your product
API credentials scoped to your use case
Custom volumes, bundles, and support
See HERE in action with our team
Estimate your costs with the API calculator
Full HERE Location Services overview
HERE vs Google Maps, Mapbox & more
Test and explore HERE APIs in the browser
Free tools for converting HERE location data
Create, edit, and validate GeoJSON in the browser
Truck-compliant routes with road restrictions
Multi-stop fleet route optimization
Bulk travel time and distance calculation
Energy-aware routing for electric vehicles
Travel-time service area calculation
Real-time traffic overlays and road incidents
High-resolution satellite and aerial imagery
Fleet-specific map rendering with truck restrictions
Address to coordinates at scale
GPS coordinates to structured address
Bulk address processing at enterprise scale
Search and discover millions of POIs globally
Hybrid GPS, Wi-Fi and indoor positioning
GPS trace matching with speed and compliance data.
Multi-vehicle fleet tour optimization
Build map-powered iOS, Android and web apps
A TCO-honest comparison for engineering teams evaluating HERE and OpenStreetMap with OSRM — infrastructure costs, truck routing depth, data quality, and ops overhead side by side. Including the question most comparisons avoid: when is "free" actually free?
$
0
OSM license cost
30
+
TRUCK CONSTRAINTS
1
DAY
API KEY TURNAROUND
10
YR
HERE GOLD PARTNER
TL;DR · The verdict
A complete comparison covering the factors that matter for production logistics deployments — not just licensing cost.
* ODbL → free to use with attribution and share-alike requirements ** Lua profiles → requires custom developer configuration — not available as API parameters
OSM is free to license. Running it in production for a logistics operation is not. Here is an honest TCO breakdown.
* Lua profiles → requires custom developer configuration — not available as API parameters OSRM infrastructure cost estimates based on typical AWS/GCP deployment for regional coverage with redundancy. Engineering time estimates based on community benchmarks. Actual costs vary significantly by team size, region coverage, and routing profile complexity. HERE pricing via Placematic partner tier as of June 2026.
OSM is the right choice for the right team. These four situations are not it.
Four surfaces where HERE and OpenStreetMap / OSRM diverge most significantly for production logistics deployments.
HERE Routing API includes a dedicated commercial vehicle profile with 30+ constraints — weight, height, width, length, axle configuration, tunnel categories (B–E), HazMat classifications, and emission zones — available as standard API parameters in every request.
OSRM supports flexible routing profiles written in Lua for different modes of transportation and respects turn restrictions including time-based conditional restrictions. However, commercial vehicle constraint parameters are not natively supported — implementing weight limits, height restrictions, and HazMat routing requires custom Lua profile development and ongoing maintenance as OSM data evolves.
OpenStreetMap is one of the most detailed geographic datasets in the world — in well-mapped urban areas, coverage rivals and sometimes exceeds commercial providers. The community of millions of contributors continuously updates road data, points of interest, and address information globally.
HERE map data is collected and maintained by dedicated professional teams with specific focus on commercial road restrictions, weight limits, bridge heights, and hazardous material routes. For logistics operations where an incorrect road restriction causes a compliance violation or accident, the difference between community-maintained and professionally verified data is operationally significant.
HERE via Placematic is a managed API — no infrastructure to provision, no data pipelines to maintain, no servers to monitor. SLA-backed uptime means routing availability is Placematic's responsibility, not yours.
OSRM is a C++-based high-performance routing engine that calculates thousands of routes per second at a fixed infrastructure price — a genuine advantage for teams with DevOps capacity and high routing volumes. The trade-off is taking on the operational work of running a server, applying updates, handling backups, and managing monthly OSM data updates.
HERE Geocoding API is included in the same partner tier as routing — one API key, one integration, one support relationship. Batch geocoding, reverse geocoding, and autocomplete are available as standard features.
OpenStreetMap routing via OSRM does not include geocoding. Nominatim is a separate OSM-based geocoding service that requires its own deployment, server infrastructure, and data pipeline. For teams needing both routing and geocoding, OSM requires two separate self-hosted stacks.
“We cut our routing bill by more than half moving from Google Maps to HERE through Placematic — and finally got truck-legal ETAs our dispatchers trust.“
VP Engineering · US logistics platform
OpenStreetMap data is free under the Open Database License (ODbL). However, running a production routing engine on OSM data — using OSRM, Valhalla, or GraphHopper — requires server infrastructure, DevOps maintenance, monthly data pipeline updates, and engineering time to configure and tune. For high-volume logistics operations, the total cost of ownership of self-hosted OSM routing typically exceeds a managed API like HERE once you account for infrastructure, maintenance, and engineering opportunity cost.
OSRM supports custom routing profiles written in Lua, which can be configured to approximate truck routing by adjusting road weights and access rules. However, OSRM does not natively support commercial vehicle constraint parameters like weight limits, height restrictions, HazMat classifications, or tunnel categories out of the box. Implementing compliant truck routing on OSRM requires significant custom engineering. HERE Routing API includes a dedicated commercial vehicle profile with 30+ constraints as a standard feature.
OpenStreetMap data is community-maintained — coverage is excellent in urban areas and well-mapped regions, but variable for logistics corridors, industrial zones, and commercial vehicle restrictions in less-mapped areas. HERE map data is collected and verified by dedicated professional teams across 200+ countries with specific focus on commercial road restrictions, weight limits, and hazardous material routes. For consumer mapping, OSM is often sufficient. For compliance-critical logistics routing, HERE’s professionally verified data reduces the risk of routing errors.
Self-hosted OSM routing makes most sense when: your team has DevOps capacity to maintain the infrastructure, you have strict data sovereignty requirements that prevent sending location data to third-party APIs, your routing requirements are standard driving profiles without complex truck constraints, and your volume is high enough that managed API costs are significant but your engineering costs are relatively low. For teams without dedicated infrastructure engineering, managed APIs like HERE typically offer better TCO.
A production OSRM deployment for a medium-sized logistics operation typically requires: cloud server infrastructure ($200–$800/month depending on region coverage and redundancy), monthly data pipeline updates from Geofabrik or planet.osm, DevOps engineering time for maintenance and updates (estimated 4–8 hours/month), and initial setup engineering (20–40 hours). For teams without existing infrastructure engineering, the total cost of ownership often exceeds a managed HERE API subscription at equivalent routing volumes.
Yes. Request your API key at placematic.com/start-trial/ — no demo call required, no credit card needed to start. You will receive credentials within 1 business day scoped to your use case. There is no contract required for pilot access — you test in sandbox and discuss commercial terms only when you are ready to go to production.
Placematic is a HERE Gold Partner with 10 years of production integrations. You get faster API access, lower pricing through our partner tier, and a dedicated integration team — none of which are available when purchasing HERE directly at standard rates.
No demo call. No credit card. API key within 1 business day.
HERE Gold Partner since 2016 · Full integration support · Placematic USA LLC