> 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/when-good-fit.md).

# When MetaMarket Is a Good Fit

MetaMarket suits a game that needs several server-held systems to agree with each other: identity, actions, quests, rewards, resources, inventory, and an economy. The platform holds state, evaluates quests, and delivers rewards on the server, so a client cannot grant itself a reward or edit its own balance.

Building those systems separately means a service each, a data model each, and continuing work to keep them consistent. If that describes the backend you are about to build or already maintain, MetaMarket replaces most of it.

## A strong fit

* Engagement and economy systems have to work together, and state, progression, and rewards must be computed and held server-side rather than in the client.
* You would otherwise stand up separate quest, reward, inventory, identity, and currency services and keep them in sync.
* You expect to reuse the same systems across more than one title, or want one player identity and one loyalty standing across a portfolio.
* You are comfortable with assisted onboarding at the platform's current stage, where registration and configuration are set up with the team.

The value grows with each title you add. The first game saves the cost of building the backend. Later games reuse it, and once a player links their installs through a device handoff, they carry one identity across all of them. MetaMarket maintains the platform currency and loyalty standing on top of that identity and displays them on its own surfaces; your game neither reads nor sets them.

## Not the right tool

Some needs are better met elsewhere, at least today:

* A single leaderboard or a small amount of local state, where a full engagement backend is more than the game needs.
* A requirement that every piece of state stay on your own infrastructure, with nothing server-side on the platform.
* A need to self-host the whole product now; a dedicated deployment is a roadmap direction, not a current option.
* Real-money custody or settlement today. MetaMarket works on game-native value; a real-money exchange is a roadmap direction, not a current component.
* A need for immediate public self-service signup, before assisted onboarding.

If the fit is close but not certain, [Evaluate MetaMarket](/evaluate-and-integrate/evaluate.md) is the low-commitment way to find out, and [Product availability](/overview/current-scope.md) is the exact state of everything you would build on.