This is the entire price list.
Billed per API token. No map-load SKUs, no seats, no enterprise tier, no sales call to find out what it costs.
Tiles are tiles — raster or vector, interactive or static, the same two numbers apply.
What would your workload cost?
Drag the sliders. The math is the pitch.
Assumes 60 tile requests per map view at ~150 KB per tile. Competitor costs use their published graduated volume tiers, free allowances included; sources and as-of date are under the comparison tables below.
Three real workloads, priced three ways.
| Scenario | MoogleGaps | Google Maps | Mapbox |
|---|---|---|---|
| Store locator 20,000 map views, 5,000 geocodes / month | $5.72/mo $3.72 tiles + 180 GB, $2.00 geocoding | $70.00/mo map loads over the 10k free cap at $7/1k | $0.00/mo inside the 50k-load and 100k-geocode free tiers |
| Consumer app 500,000 map views, 100,000 geocodes / month | $95.00/mo $93.00 tiles + 4,500 GB, $2.00 geocoding | $3,320.00/mo map loads plus geocoding over both free caps | $1,550.00/mo map loads; geocoding still within free tier |
| Logistics backend 50,000 map views, 2,000,000 geocodes / month | $371.30/mo $9.30 tiles + 450 GB, $362.00 geocoding | $5,330.00/mo geocoding dominates at $5.00 down to $1.50 per 1k | $1,050.00/mo temporary geocoding only — results may not be stored |
Estimated monthly cost after each provider's free allowances, using published list prices as of October 2026. MoogleGaps costs assume 60 tile requests per map view at ~150 KB per tile, and are computed with the same rates the estimator above uses. Their pricing pages are longer than our codebase; we may have simplified, so check the sources below before betting the quarter on it.
What you can and cannot do.
The sticker price is only half the cost. The other half is what the license won't let you build.
| Capability | MoogleGaps | Google Maps | Mapbox |
|---|---|---|---|
| Cache map tiles indefinitely | Yes Cache on your CDN, your servers, or user devices — no expiry. | No No caching of Google Maps Content; the tile SKUs have no caching allowance. Google ToS §3.2.3(b) ↗ | No Device-only cache, capped at 30 days. Mapbox Product Terms §2.8.1 ↗ |
| Bundle offline map packs in your shipped app | Yes Fixed-area tile packs are a product — embed them in the app binary. | No No pre-fetching, bulk download, or rehosting; no offline allowance exists. Google ToS §3.2.3(a) ↗ | Restricted Offline caches must be downloaded by the SDK at runtime within its device caps — no pre-bundled packs (§2.8.1). Mapbox Product Terms §2.8.1 ↗ |
| Self-host tiles on your own storage or CDN | Yes Host part or all of the world on your own cloud storage and read it with MoogleGaps. | No No resharing or rehosting Google Maps Content outside the services. Google ToS §3.2.3(a) ↗ | No Content must come directly from Mapbox APIs (§1.9, §2.8.1); self-hosting requires the separately licensed Atlas product. Mapbox Product Terms §1.9, §2.8.1 ↗ |
| Store geocoding results permanently | Yes Store them in any database for as long as you like; ODbL share-alike applies only if you redistribute enhanced data. ODbL ↗ | Restricted Generally 30 days; indefinite storage only per end user, for that user's own sessions. Google SST §6.3 ↗ | Restricted Temporary geocodes may never be stored (§2.7.2); the pricier Permanent mode allows internal-use storage only (§2.7.3). Mapbox Product Terms §2.7 ↗ |
| Display results on a non-provider map | Yes Use our tiles and geocodes with any map — MapLibre, Leaflet, or a competitor's. | No No use with or near a non-Google map; sole exception is the Places UI Kit (SST §15.1). Google ToS §3.2.3(e) ↗ | Restricted Address geocodes may position results on any map, but POI results require a Mapbox map and raw lat/lngs may not be shown (§2.7). Mapbox Product Terms §2.7 ↗ |
| Redistribute raster map tiles satellite imagery | Yes Freely distributable; attribution is required and we send it automatically in API responses. | No No resharing or rehosting Google Maps Content outside the services. Google ToS §3.2.3(a) ↗ | No No distribution from a cache, by proxying, or by screenshot (§2.8.1). Mapbox Product Terms §2.8.1 ↗ |
| Build derived datasets from vector and geocoding data OpenStreetMap / Nominatim | Yes Derive and redistribute freely — it's ODbL: if you enhance the data, publish those enhancements under ODbL too. ODbL ↗ | No No creating content from Google Maps Content — tracing, digitizing, terrain models. Google ToS §3.2.3(c) ↗ | No No tracing, deriving, or extracting; narrow exception for tracing satellite imagery non-commercially or for OSM. Mapbox Product Terms §1.6 ↗ |
Our reading of each provider's public terms as of October 2026 — a summary, not legal advice; read the actual terms before relying on them. The MoogleGaps column is our product policy, and it follows the licenses of the underlying open data rather than adding a license of our own: raster tiles from public satellite imagery are freely distributable with attribution, while vector tiles and geocoding come from OpenStreetMap and Nominatim under the ODbL — you keep full redistribution rights, and share-alike applies if you redistribute enhanced data. Sources: Google Maps Platform pricing · Mapbox pricing · Google Maps Platform ToS · Google Service Specific Terms · Mapbox ToS · Mapbox Product Terms
Spend your maps budget on your product instead.
One API token, one page of pricing, zero sales calls.