Documentation
One platform, many game surfaces
MDL is designed to host multiple public game runtimes from the same deployed platform. The platform host owns management and docs surfaces, while game domains present each title as its own independent experience.
Platform host
The platform host is where builders and operators work. It is the home for game setup, runtime configuration, documentation, monitoring, billing surfaces, and account tooling.
Game domains
A public game domain should feel like the game's own product surface. Players should experience the game's title, assets, and world rather than the platform underneath it.
Tenant routing
MDL resolves the incoming host and decides whether the request belongs to the platform or to a specific game tenant. This keeps deployment centralized while still allowing each game to have its own identity and domain.
The platform should be shared. The player-facing game should not feel shared.
Current transition state
The routing layer already exists, but MDL is still in transition. Today the runtime is still heavily backed by one selected game package, while the long-term direction is request-scoped game resolution and platform-managed hosted data.