Skip to content

Pricing

You pay for what you publish and build.

Your price follows the itineraries and zones you keep published, and the products you build on.

Create an account

Your scope

What does your team need?

Online Map Studio

Our online app, nothing to install

Outdoor Platform

Outdoor infrastructure for your products

Premium options

Your selection

No product selected yet.

Create an account

Included

What one agreement gives your whole team

Every agreement includes the Itinerary Editor, Map Publishing, the SDKs & Elements and keys for the Tile API. It covers your whole team, up to any seat limit it sets. Drafts are open, and publishing runs up to the limits your agreement names. Your quote adds Embedded Studio, white label, a support tier and named limits.

Itinerary Editor

  • Activity-aware routing
  • Drafts, segments and zones
  • Real-time collaboration
  • Elevation profiles
  • AI agent, on your own AI provider
  • GPX and KML import

Map Publishing

  • One line of code, on any site
  • Share links and public pages
  • Downloads in GPX, FIT, KML and more
  • Flythrough video
  • Printable PDF roadbook

Terrain and conditions

  • Activities from trail running to ski touring
  • Slope, aspect, weather and snow overlays
  • SAC hiking grades on each segment

SDKs & Elements

  • Typed API client that never renders
  • Map elements, renderer included
  • Turn-by-turn navigation
  • Source-available license

Tile API

  • Vector and raster tiles
  • Basemaps, terrain, weather, snow, POIs
  • Mountaya, Mapbox GL, MapLibre and deck.gl

Your agreement

  • Your whole team, up to any seat limit
  • Named rate limits, on contract
  • Availability commitment, on contract
  • White label and support, as options
  • Hosted in the European Union

In production

See what you use. Hear what changes.

Self-serve or on an agreement, every organization gets the same console. It tracks your usage by the day, sends signed webhooks and emails the members who need to know.

Usage, day by day

See each day's requests by product, operation, source and API key. Your limits sit beside them, with the day your pace reaches them.

app.mountaya.com
Your organizationUsageWhat your organization used this period, against its plan.Data APITile APIAI agentQuotasShowthis monthforall keysFilters1resourcebysuccessesSource: SDK & APIClear allRequestsBilled per requestThis month196,800 requests12 client errors · 0 server errorsMonthly quota66% of 300,000Resets Dec 1Pace328,000 by Nov 30Runs out of quota by Nov 28Rate limit60 requests a minuteOver it, requests are refused with 429Served requests per day, by resource5k10k15kNov 1Nov 8Nov 15Back to Map StudioYOYour organizationORGANIZATIONProfileMembersNotificationsPLANBillingUsageMAPSMap PublishingSecurityAI agentDEVELOPERSAPI keysWebhooksACCOUNTPreferencesSecurityProfileSign outManage cookies

Every quota on one page

Seats, published itineraries, API volume, rate limits and webhook endpoints, each beside what you use. A signed agreement raises them.

app.mountaya.com
Your organizationUsageWhat your organization used this period, against its plan.Data APITile APIAI agentQuotasQuotas come from your agreementEach one is a term of your agreement: to raise one, contact our team to change it.View agreementMap StudioHow many people your organization holds,members and pending invitations alike,counted now.Seats7 of 10Members and pending invitationsMap PublishingHow many itineraries and zones yourorganization keeps published, countednow.Published itineraries18 of 25Published nowPublished zones4 of 10Published nowData APIHow many requests your integrations maymake to the Data API, each usage periodand each minute.Monthly quota66% of 300,000Resets Dec 1Rate limit60 requests a minuteOver it, requests are refused with 429Tile APIHow many requests your keys and embeddedmaps may make to the Tile API, each usageperiod and each minute.Monthly quota63% of 2,000,000Resets Dec 1Rate limit600 requests a minuteOver it, requests are refused with 429DevelopersHow many webhook endpoints may receiveyour events, and how many domains may useyour keys.Webhook endpoints1 of 2Enabled and disabledAllowed domains2 of 3On the Security page's listBack to Map StudioYOYour organizationORGANIZATIONProfileMembersNotificationsPLANBillingUsageMAPSMap PublishingSecurityAI agentDEVELOPERSAPI keysWebhooksACCOUNTPreferencesSecurityProfileSign outManage cookies

Webhooks that keep trying

Your systems hear when an itinerary is published or an invoice is paid. Every delivery is signed and retried for up to three days.

app.mountaya.com
Your organization / WebhooksProduction eventsAn endpoint of the organization: Mountaya sends it the events it subscribes to as signed HTTPS requests.Showlast 24 hoursNov 16, 10 AM – Nov 17, 10 AMFiltersHealthThis endpoint aloneLast 24 hours12 attempts8 delivered · 0 pending · 0 failedFirst-attempt success75.0%100.0% in the endResponse time, p95420 msmedian 85 msLast success9:50 AMIn the 13 months deliveries are kept.ConfigurationWhere Mountaya delivers, which events,and how it signs them.EditStatusEnabledURLhttps://api.yourwebsite.com/mountayaEvent typesEvery itinerary eventSigning secretwhsk_••••••••••••DeliveriesEvery delivery made to this endpoint overthe period, the newest first.TODAYzone.published9:44 AMitinerary.published9:43 AMorganization.billing.invoice.paid8:12 AMBack to Map StudioYOYour organizationORGANIZATIONProfileMembersNotificationsPLANBillingUsageMAPSMap PublishingSecurityAI agentDEVELOPERSAPI keysWebhooksACCOUNTPreferencesSecurityProfileSign outManage cookieszone.publishedSucceededProduction events · 9:44 AMStarted byThe eventStartedNov 17, 9:44 AMATTEMPTSResendSucceeded9:50 AMAttempt 4 · HTTP 200 · 85 msFailed9:45 AMAttempt 3 · Timed outReceiverFailed9:44 AMAttempt 2 · HTTP 503 · 940 msReceiverFailed9:44 AMAttempt 1 · HTTP 503 · 1.1 sReceiverRESPONSEHTTP 200 · Attempt 4REQUESTMountaya-Signature: t=…,v1=…Mountaya-Event-Type: zone.publishedMountaya-Delivery-Attempt: 4

Emails each member chooses

Each member picks the emails they get, in English or French. A change to their role always reaches them.

app.mountaya.com
Your organizationNotificationsWhich notifications Mountaya sends you about this organization, and how.Required notificationsThe notifications about your own accessto this organization. They are alwayssent, so you never miss a change to it.NotificationEmailYour role changesWhen somebody changes your role in the organization.You are removed from the organizationWhen somebody removes you from the organization.Optional notificationsThe other notifications Mountaya sendsyou about this organization. Each one ison until you turn it off.NotificationEmailA collection is deletedWhen a member deletes a collection of the organization.A webhook endpoint is failingWhen a webhook endpoint's deliveries have failed for 24 hours.A webhook endpoint is disabledWhen a webhook endpoint is disabled, by a member or after 72 hours of faileddeliveries.Save changesBack to Map StudioYOYour organizationORGANIZATIONProfileMembersNotificationsPLANBillingUsageMAPSMap PublishingSecurityAI agentDEVELOPERSAPI keysWebhooksACCOUNTPreferencesSecurityProfileSign outManage cookies

99.9% availability, in your agreement

A signed agreement can commit us to 99.9% monthly availability of the Data API and the Tile API. Planned maintenance is announced on the status page five business days ahead.

mountaya.instatus.com
MountayaSubscribe to updatesAll systems operationalSCHEDULED MAINTENANCEPlatform maintenanceMon, Nov 23, 22:00 – 23:00 CETOnline Map StudioOperationalMap Studio APIOperationalData APIOperationalMCP ServerOperationalTile APIOperationalWebsiteOperationalDocumentationOperational90 days agoToday

Use case

600,000 runners, one source of geospatial data: Mountaya.

Jonathan Levy
Jonathan LevyCo-Founder & Managing Director @ Campus Coach

Instead of juggling Google Maps, Mapbox, Strava, and other providers, we made Mountaya our single source of truth for all our geospatial data. Having one centralized, end-to-end platform radically simplifies how we manage our stack and build new products.

Jonathan Levy

What will you publish and build first?

Bring a course or a product idea to a tailored onboarding session. Your quote follows within 2 business days.

Create an account

Frequently asked questions

An itinerary is published the moment anyone outside your organization can see it. That means a map embedded on a site, an exported video, a public page, or a share link sent to one person. A race with three courses on its event site is three published itineraries. The twenty variants you rejected on the way are drafts. Republishing an updated version is the same itinerary. Zones are counted apart, against a limit of their own. A zone is published once you publish it, for a collection's embed or share link to show.

Three things. The itineraries and zones you keep published at the same time, each with its own limit in your agreement. The Outdoor Platform products you build on: Embedded Studio and your monthly Tile API volume. And the options you add: white label and a support tier.

Tell us what you plan to publish and build, in the form on this page. We answer within 2 business days, with a quote in euros, excluding VAT. If you would rather see it on your own ground first, ask for a scoped pilot. We load one of your real courses and walk your team through it.

Not for the Data API and the MCP Server. Create an account, add a card or a SEPA direct debit mandate and pay for the requests you make. The Itinerary Editor, Map Publishing, Embedded Studio, the Tile API, white label and support start on a signed agreement, with the scope written down first.

Yes. The agreement covers the organization you already run, with the same keys. It adds the products it names, and can add named rate limits and an availability commitment.

A signed agreement runs for the term it states, twelve months unless agreed otherwise. Neither side ends it for convenience during that term. It names what it covers: your published itineraries and zones, the Outdoor Platform products you use, your rate limits and your support tier. The self-serve Data API runs month by month, each month counted from the day it opened. A failed renewal payment is retried for up to seven days, then the Data API closes. A first invoice that fails closes it at once. To open it again, add a payment method or reopen it in the billing settings. Every unpaid invoice is charged first, and nothing opens while one stays unpaid.

The Data API counts one request per operation it answers without an error. A call that batches several operations counts each one, and an MCP Server tool call counts as one Data API request. Each month's requests are billed at the rates on this page, counted from the day the Data API opened, the month's last day included. The Tile API counts one unit per overlay or content tile served, never a basemap tile. Your agreement names its monthly volume and rate limits. Your own integration counts, Map Publishing included: the requests your servers, pages and apps make with your keys, and the MCP Server's. You see the volume of the tiles Map Publishing draws on your sites apart. Map Studio, Embedded Studio and share links are recorded apart too, and never count toward your rate limits, your monthly volume or your bill. Throttled and failed responses are never billed and never counted.

No. The SDKs & Elements are source-available and need no agreement of their own. Their Data API requests are billed like any other, and their Tile API requests count toward your agreement.