Pricing overview
HelloSalut provides a tiered pricing structure primarily based on the number of API requests made per month. This model is common among geospatial API providers, allowing users to select a plan that aligns with their anticipated usage volume. The service includes access to a suite of APIs, such as Geocoding, Reverse Geocoding, Timezone, and IP Geolocation, under a single subscription plan. Users are typically charged based on their monthly request count, with higher tiers offering a lower cost per request. All plans are billed in Euros, and the service adheres to GDPR compliance standards.
The pricing structure is designed to be transparent, with clear documentation detailing what constitutes a single request across its various API endpoints. For instance, a single call to the Geocoding API to convert an address to coordinates counts as one request, as does a call to the IP Geolocation API to determine a user's location based on their IP address. This clarity assists developers and technical buyers in estimating their operational costs effectively before integration. The official HelloSalut pricing page provides the most current details regarding specific plan inclusions and any potential overage charges.
Plans and tiers
HelloSalut offers several distinct plans, each tailored to different usage volumes, ranging from a free tier for initial development and low-volume applications to higher-volume plans for more intensive commercial use. The core differentiator between plans is the monthly request allowance and the price point. Each plan grants access to all of HelloSalut's core products, including the Geocoding API, Reverse Geocoding API, Timezone API, and IP Geolocation API, without additional per-product charges.
The following table outlines the primary plans available, their monthly costs, key limits, and the types of users or applications they are best suited for, based on information from the official HelloSalut pricing documentation:
| Plan Name | Monthly Price (EUR) | Monthly Requests | Key Limits / Features | Best For |
|---|---|---|---|---|
| Free | 0 | 5,000 | Standard API access, no credit card required | Testing, personal projects, very low-volume applications |
| Starter | 9 | 50,000 | Includes all APIs, email support | Small websites, early-stage startups, basic geocoding needs |
| Basic | 29 | 250,000 | Increased request allowance, priority email support | Growing applications, small to medium businesses |
| Pro | 79 | 1,000,000 | High-volume usage, dedicated support options | Medium to large applications, enterprise prototypes |
| Enterprise | Custom | Custom | SLA, dedicated infrastructure, advanced features | Large-scale deployments, high-performance requirements |
Overage charges apply if a user exceeds the monthly request limit of their chosen paid plan. These charges are typically calculated on a per-request basis, often at a slightly higher rate than the average cost per request within the plan's allowance. Details on overage rates are specified on the HelloSalut pricing page.
Free tier and limits
HelloSalut provides a robust free tier designed to allow developers to experiment with the API and integrate it into small-scale applications without immediate financial commitment. This free tier includes 5,000 API requests per month. It grants full access to all of HelloSalut's core APIs, including Geocoding, Reverse Geocoding, Timezone, and IP Geolocation, making it suitable for proof-of-concept development, personal projects, and applications with very low traffic volumes.
The primary limitation of the free tier is the monthly request count. Once the 5,000-request limit is reached within a billing cycle, API calls will typically return an error until the next cycle begins or the user upgrades to a paid plan. There are no functional differences in API capabilities between the free tier and paid plans; the difference lies solely in the volume of requests permitted. The free tier does not require a credit card for sign-up, which streamlines the onboarding process for new users. For developers requiring a higher volume of requests or looking for dedicated support, upgrading to a paid plan becomes necessary. The HelloSalut documentation provides further specifics on free tier usage policies.
Real-world cost examples
To illustrate HelloSalut's pricing in practical scenarios, consider the following examples:
-
Small Blog with Location Tagging: A personal blog that tags posts with a location, performing an average of 100 geocoding requests per day to convert addresses to coordinates for a map display. This amounts to approximately 3,000 requests per month. This usage falls comfortably within the HelloSalut Free plan (5,000 requests/month), incurring no cost.
-
Local Business Directory: An online directory listing 1,000 local businesses that requires daily updates to their address data, performing 50 reverse geocoding requests per day to ensure accuracy. Additionally, it uses 200 IP geolocation requests daily to personalize content for visitors. This totals approximately (50 + 200) * 30 = 7,500 requests per month. This usage exceeds the free tier but fits within the Starter plan (50,000 requests/month) for 9 EUR per month.
-
Ride-Sharing Application (Early Stage): An early-stage ride-sharing application performing 5,000 geocoding requests for origin-destination searches and 3,000 reverse geocoding requests for driver location updates daily. This totals approximately (5,000 + 3,000) * 30 = 240,000 requests per month. This volume would require the Basic plan (250,000 requests/month) at 29 EUR per month. If usage occasionally peaks above 250,000, overage charges would apply beyond the 250,000 limit, as detailed on the HelloSalut pricing page.
-
E-commerce Platform with Delivery Zones: An e-commerce platform that validates customer addresses against a database of delivery zones, requiring 20,000 geocoding requests per day. This equates to 600,000 requests per month. This usage would require the Pro plan (1,000,000 requests/month) at 79 EUR per month.
How the pricing compares
HelloSalut's pricing model is competitive within the geospatial API market, particularly for basic geocoding and location data needs. Its tiered, request-based system is a common approach shared by many providers, including Google Maps Platform and Mapbox Geocoding API. However, specific pricing points and free tier allowances can vary.
-
Free Tier Comparison: HelloSalut's free tier of 5,000 requests per month is comparable to or more generous than some alternatives. For example, OpenCage Geocoder offers a daily limit on its free tier, while LocationIQ provides a similar free tier of 5,000 requests per day, which translates to a significantly higher monthly allowance than HelloSalut's. Mapbox offers 100,000 free requests per month for its Geocoding API, which is a higher volume than HelloSalut.
-
Paid Tier Value: At 9 EUR for 50,000 requests per month, HelloSalut's Starter plan positions it as a cost-effective option for small to medium applications. This price point is generally lower than what some major cloud providers charge for similar volumes, especially when considering the bundled access to multiple API types (geocoding, reverse geocoding, IP geolocation, timezone). For instance, Google Maps Platform uses a pay-as-you-go model with a monthly free credit, but costs can escalate quickly for higher volumes without specific plan commitments. Similarly, AWS Location Service charges per request across different API categories, which can make direct comparisons complex but often results in higher costs for comparable aggregated services.
-
Feature Set and Specialization: HelloSalut focuses on core geocoding and location data services. While larger platforms like Google Maps or Mapbox offer a broader ecosystem of mapping, routing, and visualization tools, HelloSalut's pricing reflects its specialization, making it a viable choice for developers whose primary need is accurate and cost-effective location data APIs without the overhead of extensive mapping features. For applications requiring advanced mapping functionalities, the more comprehensive, albeit often pricier, offerings from providers like Mapbox might be necessary.
Developers should evaluate their specific needs, including anticipated request volume, required feature set, and budget, when comparing HelloSalut with its alternatives. The most economical choice often depends on the scale and complexity of the application being developed.