Mapbox pricing teardown
https://www.mapbox.com/pricingMapbox's pricing page is a massive, highly granular usage-based catalog covering dozens of APIs and SDKs across Navigation, Maps, Search, Data, and Support, each with interactive sliders showing cost per usage tier. It's excellent for transparency and self-serve exploration by technical buyers, but the sheer volume of line items, tiered per-unit rates, and 'Contact sales for discount' cutoffs make it hard to get a quick sense of what anything actually costs at scale.
Tier structure
Navigation SDK v3.x (Metered)
Free / $0.30 per user + per-trip fees
Navigation SDK v3.x (Unlimited trips)
Free / per-MAU fee
Directions API
Free up to 100k requests, then $2.00/$1.60/$1.20 per 1,000
Map Matching, Optimization, Matrix, Isochrone APIs
same tiered structure as Directions
Mapbox GL JS (Map Loads)
Free up to 50k loads, then $5.00/$4.00/$3.00/$2.50 per 1,000
Mapbox GL JS (Map Seats)
Free up to 3 seats, then $4.00/$3.20/$2.40 per seat
Search Box API (Sessions/Requests)
Free tier then tiered per-1,000 pricing
Geocoding & Address Autofill APIs
Free tier then tiered per-1,000/session pricing
Support: Individual
$50/month
Support: Business
10% of monthly spend, $500/mo minimum or $6,000/year
Value metric
usage-based per API/SDK (per request, per MAU, per tile load, per seat, or per session), metered with volume-discount price breaks
How limits scale
Escalation logic
Each of ~30 products has its own free tier followed by 3-4 declining per-unit price bands as usage grows, with an implicit enterprise tier reached via 'Contact sales for discount' at the highest volumes; there's no unified good-better-best plan ladder, just per-product usage escalation.
Psychological anchors
- Free tier as universal entry anchor — Every single API/SDK starts with a generous 'Free' tier (e.g., 100k requests, 50k map loads, 3 seats) before metered pricing kicks in, lowering the barrier to first use.
- Declining per-unit price bands (volume discount) — Nearly every product shows a step-down cost curve (e.g., Directions API $2.00 → $1.60 → $1.20 per 1,000) that rewards higher usage, encouraging growth without a hard plan upgrade decision.
- High-end anchor via 'Contact sales for discount' — At the top of every usage curve, pricing disappears into a sales conversation, implicitly anchoring the visible self-serve rates as the 'retail' price versus a presumed better enterprise rate.
- Interactive sliders to visualize cost — Each product includes a draggable usage slider that recalculates 'Monthly cost,' letting prospects self-anchor around their own expected usage rather than a generic plan price.
- Annual commitment discount messaging — The page promotes 'Save when you commit' as a top-level value prop, though specific discount percentages are not shown publicly.
What this page is optimizing for
The page is optimized for self-serve technical evaluation and usage-based expansion revenue: pervasive free tiers and instant sliders let developers start building and see costs grow with them, while 'Contact sales for discount' at high volumes funnels larger accounts into enterprise negotiation.
Red flags
- Extremely high number of distinct priced products (30+) makes the page overwhelming and hard to compare or benchmark against competitors.
- No unified plan names (Starter/Pro/Enterprise) — pricing is fragmented per API, so a buyer using multiple products must sum many separate calculators to estimate total spend.
- 'Contact sales for discount' appears on almost every product at high volume, obscuring true enterprise pricing and adding friction for larger prospective customers.
- Search Box API shows both 'introductory preview pricing' and 'standard pricing' simultaneously, which is confusing about what a new signup will actually be charged.
- No visible annual discount percentage despite promoting 'Save when you commit,' leaving the actual savings opaque.
- Support plans bury pricing logic (10% of spend with a $500/mo minimum) in a way that's hard to project without already knowing total usage costs.
Best-practices scorecard
What works · 1
- Value metric matches usage — Pricing is granularly tied to actual usage (requests, loads, seats, sessions) per product, which fits developer-consumption models well.
Half measures · 4
- Visible prices — Per-unit rates and free thresholds are shown for every API, but total cost requires manual calculation across many products and disappears into 'contact sales' at scale.
- Annual discount offered — Annual commitment savings are mentioned as a value prop but no specific percentage or terms are shown on the page.
- FAQ or objection handling — Tooltips define technical terms (e.g., what counts as a 'trip' or 'session') but there's no consolidated FAQ section addressing common pricing objections.
- Clear CTAs per tier — Each product has a 'Detailed pricing' expander and 'Contact us for discount' link, plus top-level Sign up/Contact sales buttons, but CTAs are repetitive and generic rather than tailored to buyer intent.
What's missing · 3
- Clear recommended tier — No highlighted/recommended plan exists since this is a per-product usage catalog rather than a tiered plan structure.
- Tier differences are scannable — With 30+ separately priced products each having their own multi-band pricing table, the page is dense and hard to scan for overall cost comparison.
- Trust signals present — No customer logos, testimonials, or case studies are visible on the pricing page itself.