MapsForDevs — Commercial License Terms (Developer Reference)
This file is a developer-facing summary. The legally binding terms live in your account dashboard and supersede this summary if they conflict.
What you get
| Plan | Tile API | Embed widget | Geocoding |
|---|---|---|---|
| Free | 20k tile reqs / mo | Unlimited views (rate-limited per IP) | 2.5k reqs / mo |
| Pay-as-you-go | $0.05/1K above free, lower at higher volume | Unlimited | 25k / mo included, then PAYG |
| Scale | Negotiated | Negotiated | Negotiated |
Quotas reset on calendar month boundaries (UTC+2 / SAST).
What you can do
- Build commercial products on top of our tile API.
- Cache tiles you fetched on your own CDN, for up to 90 days from each fetch.
- Display our maps in unlimited end-user browsers / devices, subject to plan quota.
- Modify our public style.json (colours, layer order, fonts) and serve the modified style from your own origin.
What you can't do
- Re-distribute the raw tile bytes /
.pbffiles to third parties as a generic tile service. (Caching tiles for your own users = fine. Reselling tiles as their own product = not fine.) - Strip or hide attribution. Both
© OpenStreetMapand© MapsForDevsmust remain visible on every map view. - Use a single API key across more than one publicly-accessible product / domain. Issue separate keys per product.
- Bulk-download our entire tile corpus. (We have a script that detects this. We will rate-limit and contact you.)
Attribution requirement
© OpenStreetMap contributors · © MapsForDevsBoth clauses, both clickable links, on every map view. See recipes/attribution.md for placement guidance.
For ODbL data (OpenStreetMap), the open database license requires attribution and share-alike for derivative databases. Producing rendered tiles from the database is not a derivative database — your tiles are not subject to share-alike.
API key handling
mfd_pub_*keys belong in browsers / public bundles. They must be domain-restricted.mfd_srv_*keys belong in server-side code only. If exposed in browser code, rotate immediately.- Keys are shown once at creation. Storage is your responsibility.
- Lost a key? Rotate via the dashboard. Old key works for 24 h grace period.
Data freshness
- Tile API: rebuilt monthly from current OpenStreetMap data.
- Geocoding: live against our Nominatim instance; reflects OSM updates within ~24 h.
Service level (SLO)
| Plan | Uptime target | Notes |
|---|---|---|
| Free | 99.0% | Best effort |
| Pay-as-you-go | 99.9% | |
| Scale | 99.95% with custom SLA | Contracted |
Status page: https://status.mapsfordevs.com
Termination
You can cancel any time. On cancellation:
- Tile API and geocoding stop on the next quota cycle boundary.
- Embed widgets keep working.
Privacy & data
- We log tile requests for billing + abuse detection. Logs retained 90 days.
- We don't track end-user identity, geolocation, or session data.
- We don't sell or share request logs with third parties.
- See full privacy policy: https://mapsfordevs.com/privacy
Refunds
- Pay-as-you-go: prior usage is non-refundable. Cancel any time to stop further billing.
Contact
- support@mapsfordevs.com — technical issues, billing
- legal@mapsfordevs.com — license clarifications, custom terms
- abuse@mapsfordevs.com — report misuse of keys / quota theft