Nominatim Pricing: Self-Hosted and Commercial Options (2026)

Pricing overview

Nominatim is an open-source geocoding software distributed under the GNU Lesser General Public License v3 (LGPLv3), meaning the software itself is available without charge for both commercial and non-commercial use. The primary costs associated with Nominatim arise from its deployment and operation, rather than licensing fees. Users have two main approaches to utilizing Nominatim: self-hosting or using a service provided by a third party.

• Self-hosting: This involves setting up and maintaining a Nominatim instance on private or cloud infrastructure. Costs are determined by server hardware, data storage, bandwidth, and the labor required for installation, configuration, updates, and maintenance. This approach offers complete control and customization but demands significant technical expertise and operational investment. The official Nominatim documentation provides detailed installation guides.
• Third-party commercial services: Several providers offer managed Nominatim instances or geocoding APIs built on Nominatim. These services typically charge based on query volume, feature sets, or subscription models, abstracting away the infrastructure and maintenance complexities. This option is suitable for users who prefer a managed solution without the overhead of self-hosting.

Plans and tiers

As Nominatim is open-source software, it does not come with predefined commercial plans or tiers from its developers. Instead, the 'tiers' are effectively determined by the user's chosen deployment method and operational scale. For self-hosted instances, users scale their infrastructure (CPU, RAM, storage) to meet their query volume and performance requirements. For third-party services, specific plans and tiers will vary by provider.

Self-hosted considerations

When self-hosting, the 'tiers' are analogous to the infrastructure choices made. A small-scale deployment for occasional queries might run on a modest virtual private server (VPS), while a high-volume, production-grade service could require dedicated servers with substantial resources. The Nominatim project recommends specific hardware recommendations based on data size, such as 150 GB of disk space and 32 GB RAM for a full Planet OSM database.

Third-party provider examples (illustrative)

Commercial providers offering Nominatim-based services generally structure their pricing with tiers based on query volume, often measured in requests per second (RPS) or total monthly requests. While specific pricing details are proprietary to each vendor, common models include:

• Free/Developer tiers: Limited queries per day/month, often with rate limits.
• Standard tiers: Increased query limits, potentially with higher RPS and basic support.
• Premium/Enterprise tiers: High query volumes, dedicated infrastructure, advanced features, and priority support.

For example, some geocoding API providers (not strictly Nominatim, but illustrative of the market) offer plans starting from a few thousand free requests per day, scaling up to millions of requests for hundreds or thousands of dollars per month, sometimes with price breaks at higher volumes, as seen with Google Maps Platform.

Free tier and limits

Nominatim itself, being open-source, constitutes a 'free tier' in terms of software cost. However, its practical usage involves either self-hosting or relying on public instances, each with its own interpretation of 'free' and 'limits'.

Self-hosted free tier

If you self-host Nominatim, you have effectively unlimited usage, bounded only by your infrastructure's capacity and your budget for it. There are no software-imposed rate limits or query caps. All costs are operational (hardware, electricity, bandwidth, maintenance) rather than per-query licensing.

Public Nominatim instances

Several public Nominatim instances exist, often run by OpenStreetMap community members or organizations. These instances typically provide a free service but impose strict usage policies and rate limits to prevent abuse and manage server load. For example, the official OpenStreetMap Nominatim instance (nominatim.openstreetmap.org) has a strict usage policy:

• No heavy usage (e.g., bulk geocoding).
• Maximum of 1 request per second.
• A specific User-Agent header is required.
• Commercial use is generally discouraged; users are advised to set up their own instance or use a commercial provider for production applications.

These limits are in place to ensure fair use and maintain service availability for casual users and OpenStreetMap contributors. Relying on public instances for production applications is not recommended due to these restrictions and the lack of service level agreements (SLAs).

Real-world cost examples

The cost of using Nominatim varies significantly based on the chosen deployment model and usage volume. Here are illustrative scenarios:

Scenario 1: Small-scale self-hosted (e.g., hobby project, internal tool)

• Description: Geocoding a few hundred to a few thousand addresses per day, non-critical application.
• Infrastructure: Small cloud VPS (e.g., 2-4 vCPU, 8-16 GB RAM, 200 GB SSD for OSM regional data).
• Estimated monthly cost: $20 - $80 (for VPS rental from providers like DigitalOcean, AWS Lightsail, or similar). This excludes setup time and maintenance labor.
• Considerations: Requires basic Linux administration skills. Initial setup can take several hours to a few days. Data updates (e.g., weekly) consume bandwidth and CPU.

Scenario 2: Medium-scale self-hosted (e.g., medium-sized business, research project)

• Description: Geocoding tens of thousands to hundreds of thousands of addresses per day, requiring higher reliability.
• Infrastructure: Dedicated cloud instance or larger VPS (e.g., 8-16 vCPU, 32-64 GB RAM, 500 GB - 1 TB SSD for full Planet OSM data).
• Estimated monthly cost: $150 - $500+ (for cloud instance). This also excludes dedicated IT staff time for setup, monitoring, and maintenance.
• Considerations: Requires experienced system administrators. Performance tuning, database backups, and regular updates are critical. Downtime can impact operations.

Scenario 3: Large-scale self-hosted (e.g., enterprise application, high-volume service)

• Description: Geocoding millions of addresses daily, requiring high availability and performance.
• Infrastructure: Multiple dedicated servers or highly provisioned cloud instances, potentially with load balancing and distributed databases. (e.g., 16+ vCPU, 128+ GB RAM, TBs of NVMe SSDs).
• Estimated monthly cost: $1,000 - $5,000+ (for infrastructure alone). Significant ongoing costs for dedicated DevOps/SysAdmin teams.
• Considerations: Complex setup and maintenance. Requires specialized expertise in database optimization, distributed systems, and potentially custom development for scaling.

Scenario 4: Third-party commercial service (illustrative, not Nominatim-specific)

• Description: Geocoding tens of thousands to millions of addresses per month, preferring managed service.
• Provider Model: API calls, often tiered pricing. For example, a commercial geocoding API might charge $0.50 - $4.00 per 1,000 requests, with volume discounts.
• Estimated monthly cost: $50 - $2,000+, depending on call volume and provider.
• Considerations: No infrastructure management overhead. Includes support and SLAs. Less control over underlying software stack. Price per query might be higher than self-hosting at very high volumes, but total cost of ownership (TCO) might be lower due to reduced labor costs.

How the pricing compares

Nominatim's pricing model, centered on open-source software and self-hosting, stands in contrast to most commercial geocoding APIs. The comparison highlights a trade-off between direct monetary cost and required technical investment.

While the upfront software cost of Nominatim is zero, the total cost of ownership (TCO) for a self-hosted instance can be substantial, especially for high-volume or high-availability requirements. Commercial alternatives like Google Maps Platform or Mapbox Geocoding API offer managed services that abstract away infrastructure complexities, charging primarily for usage. This often translates to a higher per-query cost but a lower labor cost for development and operations teams. The choice between Nominatim and commercial alternatives often comes down to budget for infrastructure vs. budget for per-request API calls, desired level of control, and available technical expertise.