Pricing overview

OnWater provides an API service designed to determine if a given geographic coordinate is located on water or land. The pricing structure is primarily usage-based, meaning costs are incurred according to the number of API requests made. This model is common among geospatial APIs, where operations often involve discrete queries against a dataset. OnWater's pricing includes a free tier, allowing developers to test the service or support low-volume applications without immediate cost, and then scales through various paid plans as request volumes increase. The service focuses on a single, specific functionality: a boolean check for water presence, which simplifies its pricing model compared to more complex geospatial platforms offering multiple service types and data layers. The official OnWater documentation details the current pricing structure and provides examples of how usage is calculated for billing purposes.

The core value proposition of OnWater is its specialized focus. While broader mapping platforms like Google Maps Platform or Mapbox offer extensive geospatial capabilities, OnWater specifically addresses the need for water body identification. This specialization influences its pricing, which is structured around the singular metric of API calls to its /api/v1/results/{lat},{lon} endpoint. The pay-as-you-go methodology allows users to scale their usage and associated costs directly with their application's needs, from small-scale projects using the free tier to large enterprise applications requiring millions of requests. For developers integrating location-based services, understanding the per-request cost and volume tiers is crucial for effective budget planning. The concept of usage-based pricing models is a standard practice across cloud services, including those for data and GIS APIs, allowing providers to align costs with resource consumption.

Plans and tiers

OnWater's pricing structure is divided into several tiers, each offering a distinct volume of API requests at a set monthly price. These tiers are designed to accommodate a range of usage patterns, from individual developers and small projects to larger applications and enterprises. As the request volume increases across tiers, the effective cost per API call generally decreases, incentivizing higher usage on more comprehensive plans. All paid plans include support and access to the core OnWater API functionality. There are no distinctions in API features between paid tiers; the differences are solely based on the allocated request volume.

The following table outlines the primary paid plans offered by OnWater, detailing their monthly cost, included requests, and typical use cases based on information from the OnWater homepage and documentation:

Plan Name Monthly Price Included Requests Best For
Free Tier $0 5,000 Development, testing, very low-volume personal projects, proof-of-concept
Small $19 50,000 Small-scale applications, startups, moderate personal projects
Medium $49 250,000 Growing applications, mid-sized projects, small businesses
Large $99 750,000 Larger applications, data analysis requiring significant queries, enterprise prototypes
Enterprise Custom Millions+ High-volume enterprise applications, large-scale data processing, custom requirements

For usage exceeding the bundled requests in a paid plan, OnWater typically charges an overage fee per additional request. The specific overage rates are detailed on the OnWater pricing page, ensuring transparency for users whose consumption fluctuates. Enterprise plans are tailored to specific client needs, often involving custom request volumes, dedicated support, and specialized service level agreements, which are negotiated directly with OnWater.

Free tier and limits

OnWater provides a free tier designed to allow developers to explore the API's functionality, integrate it into proofs-of-concept, and support low-volume applications without incurring initial costs. This free tier includes 5,000 API requests per month. This allocation is sufficient for initial development, testing, and even for small-scale personal projects that do not generate high transaction volumes. The free tier offers full access to the core OnWater API, meaning there are no feature limitations compared to paid plans, only volume restrictions. This approach aligns with common practices in the API economy, where free tiers serve as an essential entry point for adoption. Similar free access models are utilized by providers like Cloudflare Workers, offering a baseline of free usage before paid tiers commence.

Key aspects of the OnWater free tier include:

  • Monthly Request Limit: Users can make up to 5,000 API calls within a calendar month.
  • Full API Functionality: All features of the OnWater API are available, allowing developers to fully integrate and test the service.
  • No Credit Card Required: Typically, access to the free tier does not require providing credit card details upfront, simplifying the signup process.
  • Automatic Reset: The request count resets at the beginning of each billing cycle (usually the first day of the month).
  • Transition to Paid Plans: If an application exceeds the 5,000 monthly requests, an upgrade to a paid plan is required to continue service without interruption. OnWater's system monitors usage and provides notifications as users approach their free tier limits.

The free tier is particularly beneficial for students, hobbyists, or developers evaluating OnWater for potential enterprise integration. It mitigates the risk associated with committing to a paid service before understanding its performance and suitability for specific use cases. For applications requiring consistent, higher volumes of requests, upgrading to one of the paid plans becomes necessary to ensure uninterrupted service and benefit from more cost-effective per-request rates.

Real-world cost examples

To illustrate OnWater's pricing in practical scenarios, consider several common use cases and their associated costs based on the outlined plans. These examples demonstrate how different application scales translate into monthly expenditures, providing a clearer understanding of potential budgeting for developers and businesses. The examples assume typical usage patterns and are based on the pricing information provided on the OnWater website.

Example 1: Small Personal Project / Development Testing

  • Scenario: A developer is building a prototype for a marine navigation app or conducting initial data analysis on a small dataset of GPS coordinates. This involves occasional checks, perhaps 100-200 requests per day during active development.
  • Monthly Requests: 150 requests/day * 30 days = 4,500 requests.
  • Cost: $0.00
  • Explanation: This usage falls within the free tier's 5,000 monthly request limit, resulting in no cost.

Example 2: Moderate Web Application

  • Scenario: A small web application that provides location-based services for recreational boaters, checking if user-submitted coordinates are within navigable waters. The application experiences moderate traffic, generating approximately 1,500 requests per day.
  • Monthly Requests: 1,500 requests/day * 30 days = 45,000 requests.
  • Cost: $19.00
  • Explanation: This volume exceeds the free tier but fits comfortably within the Small plan, which offers 50,000 requests for $19 per month.

Example 3: Geospatial Data Processing Job

  • Scenario: A data scientist needs to process a dataset of 150,000 geographical points to filter out land-based coordinates for an environmental study. This is a one-time or infrequent batch job.
  • Monthly Requests: 150,000 requests.
  • Cost: $49.00
  • Explanation: This usage would require the Medium plan, which includes 250,000 requests for $49. The project remains well within this tier's allocation.

Example 4: High-Volume Maritime Logistics Platform

  • Scenario: An enterprise application used by a shipping company to track vessels, optimize routes, and manage port operations, requiring real-time checks for millions of coordinates monthly. For instance, 1.5 million requests per month.
  • Monthly Requests: 1,500,000 requests.
  • Cost: Custom (Enterprise Plan)
  • Explanation: This volume significantly exceeds the largest standard plan (Large, 750,000 requests). The company would engage OnWater for a custom Enterprise plan, which typically offers more favorable per-request rates and dedicated support tailored to high-volume needs. If this were to fall into the regular plan structure, it would either combine the Large plan with significant overage charges or necessitate multiple Large plans, making a custom plan more cost-effective.

How the pricing compares

When evaluating OnWater's pricing, it is useful to compare it against alternative geospatial APIs. While OnWater's core functionality is highly specialized (determining water presence), other platforms offer broader mapping and geocoding services that may encompass similar capabilities, often as part of a larger suite of tools. The comparison highlights OnWater's niche positioning and its value proposition for specific use cases.

OnWater vs. OpenCage Geocoding API

  • OnWater: Priced per request, with 5,000 free requests and plans starting at $19 for 50,000 requests. Focused solely on water/land detection.
  • OpenCage Geocoding API: Offers forward and reverse geocoding. Its free tier provides 2,500 requests/day (approx. 75,000/month). Paid plans start at $50/month for 100,000 requests. While OpenCage can return detailed location data, including administrative boundaries that might indicate water bodies, it does not offer a direct boolean water detection endpoint. Developers would need to parse returned data to infer water presence, potentially adding complexity. OnWater is more cost-effective and direct for its specific task at lower volumes, as detailed on the OpenCage pricing page.

OnWater vs. Google Maps Platform

  • OnWater: Specialized, lower entry cost for its specific task.
  • Google Maps Platform: Offers a wide range of APIs including Geocoding, Places, and Maps Static. Pricing is complex, often based on specific API calls (e.g., Geocoding, Places API calls) and data units (e.g., map loads), with a monthly free credit of $200. While Google Maps can display water bodies and provide geographical context, directly querying if a point is on water requires more advanced analysis of feature types or custom polygon overlays, making OnWater a simpler and potentially more affordable solution for that singular query. For broader mapping needs, Google Maps Platform offers unparalleled breadth.

OnWater vs. Mapbox

  • OnWater: Simple, direct pricing for a specific geospatial query.
  • Mapbox: Provides a suite of mapping tools, including custom maps, geocoding, and routing. Pricing is typically based on map loads, geocode requests (with a free tier of 100,000 requests/month), and other service units. Detecting water presence with Mapbox might involve querying vector tiles or using custom data layers, which requires more development effort and carries different cost implications compared to OnWater's direct API call. Mapbox is designed for comprehensive mapping application development, where OnWater serves a focused utility. Mapbox's pricing information can be found on their official pricing page.

In summary, OnWater's pricing model is highly competitive for its specific niche: accurately and efficiently determining if a geographic point is on water. Its direct API and straightforward usage-based billing make it an attractive option for applications where this specific query is a primary requirement. While alternatives offer broader geospatial capabilities, they often come with more complex pricing structures and may require additional development to achieve the same water detection functionality, potentially at a higher effective cost for that specific task.