For outdoor ecosystems

# A course editor in your colors, for everyone you serve.

Put Embedded Studio inside your product, and the organizations you serve plan their courses in your colors. The same platform powers the maps in your own app.

[Talk to us](/en/contact/)

[See pricing](/en/pricing/)

Embedded Studio

## Your customers map inside your product

The editor opens inside your app, in your colors and under the rules you set. The organizations you serve never leave your product.

Embedded Studio · Running brand

![Outdoor map of the course, drawn by the Mountaya map elements.](/images/map-studio/terrain-winter.webp)

Fills the window and loads the map renderer

Running brandA course library for the races it sponsors

Race seriesOne course, open in its entrant portal

Outdoor appA trip planner with a full-width map

Works with the tools you already use

Apple Health

For the organizations you serve

## A course editor for each of your customers

Editing, keys and exports, for organizations outside your own team.

### Your users, your call

Every edit is made as the Mountaya member your backend names: one per person, or one shared account. You decide how your users map to Mountaya.

### The map, or the whole editor

Map Publishing puts the finished course on any page, read-only, with one line of code. Embedded Studio puts a themed editor inside your product.

### Your theme, your rules

The editor takes your colors, fonts and corners, and our servers apply the rules you set on every request.

### Keys stay on your side

The organizations you serve work through your credentials. Publishable keys run in the browser, secret keys stay on your server, and session tokens scope each visitor.

### Live editing, together

Each organization's team edits one course together, live, inside your product.

### Courses reach your apps

The editor, the published map and your own components read the same itinerary. A change published once shows up in each.

### Courses in and out as files

Your customers import GPX or KML, and export GPX, FIT or TCX for Garmin, Suunto and Strava.

### White label, as an option

With the white-label option, the Mountaya mark comes off the editor and the published maps.

Map, profile and table

## One course on the map, in a profile and in a table

The map, the Elevation Profile Element and the Segment Table Element read the same course, so pointing at one shows the same place in the other two. This one is the Patrouille des Glaciers, from Zermatt to Verbier.

![Winter map of the Patrouille des Glaciers course, from Zermatt to Verbier.](/images/elements/itinerary-map-light.webp)

Segment table of the Patrouille des Glaciers course, one row per segment from Zermatt to Verbier, each with its distance, climb, descent and altitude range.

### The map follows the profile

Move along the profile and a card gives the distance, the altitude and the climb so far at that point. A marker follows on the map.

### Waypoints on the profile

The course's waypoints are pinned on the profile at their own distance, and each segment is summed up underneath.

### Each row lights its segment

Pointing at a row of the table lights that segment on the map. Pointing at the course on the map lights its row.

### One set of figures

Each segment's distance and climb are computed once, on our servers, from the full track. The table, the profile and the map state the same numbers.

AI agents and API

## The questions your product asks every day

Ask in plain language through the MCP Server, or call the typed client. The Data API answers.

[Explore MCP Server](/en/platform/mcp/)

AI agent

Generate a 22 km trail loop from Chamonix for one of our organizers, with around 1,200 m of climbing.

suggestions

200

{ activity: 'HIKING_AND_TRAIL', candidates: 3, distance: 22000, ascent: 1200, start: [6.8712, 45.9231] }

3 candidates · closest 21.6 km / +1,183 m

3 candidates come back. The closest runs 21.6 km with 1,183 m of climbing, ready to open in the organizer's editor.

Break down the surface and gradient of the course this organizer just published.

analyzeGeometry

200

{ activity: 'HIKING_AND_TRAIL', coordinates: [[6.87126, 45.92307], [6.8713, 45.9231], …] }

+984 m · 19.9° max · asphalt → ground → compacted gravel

The course climbs 984 m and reaches 19.9° at its steepest. It runs on asphalt, then ground, then compacted gravel.

Show how far someone gets on foot from its start in 30, 60 and 120 minutes.

isochrones

200

{ activity: 'HIKING_AND_TRAIL', locations: [[6.8712, 45.9231]], range: [1800, 3600, 7200], rangeType: 'TIME' }

3 polygons · 3.6 / 9.0 / 24.2 km²

3 zones come back: 3.6 km² within 30 minutes, 9.0 km² within 60 and 24.2 km² within 120.

## Why outdoor ecosystems build on Mountaya

Slope and surface come with the map, in the editor and in every API, and weather sits on top. Your team stops assembling them by hand.

Generic map tools

- A mapping product your roadmap never asked for

- One map vendor for your app, another for your customers

- Your customers export a file and finish the job elsewhere

- Every organization you onboard needs a mapping specialist

- A generic map API that sends your users onto the nearest road

Mountaya

- Embedded Studio is that product, hosted and themed to your product

- One organization and the same maps behind both

- They finish it inside your product, in your theme

- Each one opens the editor in your product and starts drawing

- The Data API routes on the trail and reads slope and surface

Use case

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

![Jonathan Levy](/images/avatars/jonathan-levy.webp)

Jonathan Levy

Co-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

![Campus Coach](/images/quote-campus.webp)

## Which organizations do you serve?

Tell us who you serve. We show you Embedded Studio in your theme.

[Talk to us](/en/contact/)

[See pricing](/en/pricing/)

Frequently asked questions

Do our customers see our brand or yours?

Yours, with the white-label option. Embedded Studio takes your colors, your typefaces and your authentication, so the editor reads as part of your product. Without that option, the Mountaya mark stays visible.

Do we have to build the editor ourselves?

No. Embedded Studio is the hosted editor, themed for you and bounded by the rules you set. If you would rather build your own, the SDKs & Elements ship the parts ours is assembled from.

Who decides what each organization is allowed to do?

You do. Theme, starting configuration and safety rules are set per organization and enforced on our servers. No organization gets past what you allow.

How do we get started?

Tell us who you serve, and we plan Embedded Studio around them. We set up your organization and your keys with you, and mount the editor in your product together.
