> For the complete documentation index, see [llms.txt](https://sdk.metamarket.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sdk.metamarket.tech/architecture-and-trust/responsibilities-and-boundaries.md).

# Studio and Platform Responsibilities

On MetaMarket the platform runs shared infrastructure while your game keeps its gameplay, content, and player experience. The split follows from your game's trust level and the gateway door its client uses.

## Who owns what

| Your game or studio                               | MetaMarket                                                             |
| ------------------------------------------------- | ---------------------------------------------------------------------- |
| Sends player activity as actions                  | Interprets each action against your config and stores the result       |
| Displays player-facing state, quests, and rewards | Holds authoritative player state, quest progress, and reward inventory |
| Implements game rules, content, and UX            | Runs the shared quest, reward, and economy engine your config drives   |
| Owns its local economy and progression            | Owns the shared player identity and the platform currency (GG)         |
| Keeps the device key on the device                | Holds every server-side secret and signing key                         |

## What MetaMarket operates

* **Player identity.** One durable player across a studio's games, with device keypairs, token rotation, and device handoff, so a studio does not run its own login system. A connected game reads the shared identity (id and display name); it does not build or hold the credential. Today this is the guest credential; see [Product availability](/overview/current-scope.md).
* **The platform currency and loyalty standing.** GG, loyalty points, tiers, and badges are platform-owned; a game cannot mint, credit, or configure them. They reach a player through platform-owned workflows that react to reported milestones. The mechanic and the exact read and write boundary are in [Local and Shared Economies](/core-concepts/shared-economy.md).
* **Tenant isolation.** Every game is confined to its own app id, and shared platform data sits behind platform-owned workflows, so one game cannot reach another's data or the shared balance directly. [Security and tenant isolation](/architecture-and-trust/security-and-tenant-isolation.md) has the mechanism.

## What your game keeps

* **Gameplay and content.** The engine interprets your configuration; it does not ship your rules, your content pipeline, or your art.
* **Local economy and quests.** Local currency, local progression, and gameplay-local quests are your data. You decide what a quest rewards and when a resource regenerates.
* **Everything the player sees.** The platform returns authoritative state; every screen, asset, and interaction on top of it is yours. The reference desktop clients are MetaMarket's own, not a template to reuse as-is.

## What we set up together

Assisted integration is where the shared decisions get made: your game's trust level, the gateway door its client uses, the set of actions it is allowed to send, and the configuration that drives the engine for it. The team works these through with you during onboarding rather than leaving them to a self-serve form.

MetaMarket handles game-native currencies, rewards, and items; fiat settlement and cash-out stay out of scope, and a real-money exchange is a direction on the [Roadmap](/releases-and-reference/roadmap.md) rather than a current component.

To see which of these run today, check [Product availability](/overview/current-scope.md).