Compare

PickPoint vs the alternatives

Pricing, rate limits, tracking, and onboarding - side by side across five providers.

No per-request billingNo per-minute rate limitsDevice tracking on every plan

Deep diveHow to Choose a Geolocation API for Production: a technical breakdown of all six providers →Architecture, pricing calculations, code examples and migration guide · ~15 min

Side by side

Needs significant engineering before serving a single request: 600 GB planet import, PostgreSQL + PostGIS setup, and an ongoing diff pipeline. The public instance prohibits commercial use and caps at 1 req/s. Right tool for open-source projects with the infrastructure capacity to run it.

Nominatim PickPoint
Planet import ~600 GB, PostgreSQL + PostGIS, ongoing diff pipeline. Significant upfront engineering before serving a single request.
Setup
Sign up, copy an API key, make a request. No database, no ops, no imports. Live in 2 minutes.
Public instance: 1 req/s, commercial use prohibited. Self-hosted: no cap, but full infrastructure ownership.
Rate limits
No per-minute caps on any plan. Burst your full daily quota whenever the workload demands it.
Forward and reverse geocoding only. Routing (OSRM), autocomplete (Pelias), and tracking each require a separate system.
Scope
Geocoding, routing (10+ modes), address autocomplete, and WebSocket device tracking - one key.
Self-managed. Your team owns availability, backups, and incident response. No SLA by definition.
Reliability
99.9% uptime SLA. Incidents published to the API Status page within 30 minutes.
Free (server costs yours). ODbL attribution required in public-facing products.
Cost
From $50/month - all four APIs, SLA, and support included. No per-request billing.

When Nominatim makes more sense: open-source apps, internal tooling, or hobby projects where ops capacity exists, commercial use is not required, and zero licensing cost is the priority.

Built for

Products that ship geo features without managing infrastructure or watching an invoice grow.

Production SaaS

Geocoding, routing, and autocomplete in one integration

  • Forward & reverse geocoding worldwide
  • Address autocomplete for search fields and checkout
  • Turn-by-turn routing with 10+ vehicle modes
  • One API key, one flat monthly bill - costs don't spike with traffic

Fleet & Logistics

Real-time tracking and routing on a single plan

  • WebSocket GPS streaming at up to 50 Hz
  • Device registration, live status, and track history
  • Multi-stop route optimization with time-window support
  • No per-request billing as your fleet grows

E-commerce & Delivery

Address quality from input to last mile

  • Autocomplete reduces checkout address entry errors
  • Forward geocoding to validate and normalize addresses
  • Last-mile routing for dispatch and delivery windows
  • Batch geocoding for catalog enrichment - no rate limits

On-demand & Field Service

Dispatch, routes, and live position in one stack

  • Real-time device location via WebSocket stream
  • Optimized routing for technicians and drivers
  • Geocoding for job-site address lookup and verification
  • One key covers the full location stack end-to-end

Cost at 1M requests / month

Geocoding + routing combined. Illustrative estimates - check each provider's current pricing page.

Google
~$5,000–15,000
HERE
~$750–1,500
Mapbox
~$700–2,500
TomTom
~$500–1,200
Nominatim
~$100–300 (server)
PickPoint
~$50–200/mo flat

Worked example: 500k geocoding + 100k routing calls/month - Google ~$3,500 · HERE ~$720 · Mapbox ~$950 · TomTom ~$600 · PickPoint ~$100

Migrating to PickPoint

For geocoding, the switch is a URL change and one header. Most migrations take under an hour.

From Nominatim
- curl "https://nominatim.openstreetmap.org/search - ?q=Eiffel+Tower&format=json&limit=1"   + curl "https://api.pickpoint.io/v2/geocode/forward + ?q=Eiffel+Tower" + -H "X-Api-Key: YOUR_KEY"
response: [{lat, lon, …}] → GeoJSON FeatureCollection
From Google Geocoding
- curl "https://maps.googleapis.com/maps/api/geocode/json - ?address=Eiffel+Tower&key=GOOGLE_KEY"   + curl "https://api.pickpoint.io/v2/geocode/forward + ?q=Eiffel+Tower" + -H "X-Api-Key: YOUR_KEY"
results[0].geometry.location.lat → features[0].geometry.coordinates[1]
From Mapbox Geocoding
- curl "https://api.mapbox.com/geocoding/v5/mapbox.places - /Eiffel+Tower.json?access_token=MAPBOX_TOKEN"   + curl "https://api.pickpoint.io/v2/geocode/forward + ?q=Eiffel+Tower" + -H "X-Api-Key: YOUR_KEY"
GeoJSON FeatureCollection - features[0].geometry.coordinates compatible
From HERE Geocoding
- curl "https://geocode.search.hereapi.com/v1/geocode - ?q=Eiffel+Tower&apiKey=HERE_KEY"   + curl "https://api.pickpoint.io/v2/geocode/forward + ?q=Eiffel+Tower" + -H "X-Api-Key: YOUR_KEY"
items[0].position.lat → features[0].geometry.coordinates[1]
From TomTom Search
- curl "https://api.tomtom.com/search/2/geocode - /Eiffel+Tower.json?key=TOMTOM_KEY"   + curl "https://api.pickpoint.io/v2/geocode/forward + ?q=Eiffel+Tower" + -H "X-Api-Key: YOUR_KEY"
results[0].position.lat → features[0].geometry.coordinates[1]

Try before you decide

Test the same queries and see for yourself.

Start free trial