> 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/overview/who-its-for.md).

# Who It's For

MetaMarket suits a studio that would rather configure its engagement and economy backend than build and maintain one. You can start with a single title and adopt only the parts you need. When you ship a second game, it runs on the same foundation, and a shared player identity and loyalty standing connect the two.

## A studio launching one game

You do not need a portfolio for this to pay off. Instead of building identity, quests, rewards, an inventory, energy timers, and a wallet, you configure them and spend the time on the game itself.

## An existing game adding engagement or economy systems

If your live game needs daily loops, a progression system, a shop, or a server-authoritative economy, you can add each as configuration rather than as a new backend project. Your existing client keeps shipping unchanged.

## A publisher operating several titles

A catalogue benefits most. One backend serves every title, and a player who links their installs is recognised across all of them and carries one loyalty standing through the portfolio.

## A platform connecting several game experiences

If you are building a connected set of games under one player, the shared identity and loyalty layer is what you are buying. Each game still runs its own economy and content underneath it.

## Where to start

* New to the product: [What you can build](/overview/capabilities.md), then [When MetaMarket is a good fit](/overview/when-good-fit.md).
* Weighing the architecture: [Architecture overview](/architecture-and-trust/product-overview.md) and [Studio and platform responsibilities](/architecture-and-trust/responsibilities-and-boundaries.md).
* Ready to build: [Evaluate MetaMarket](/evaluate-and-integrate/evaluate.md).