DGM Server is the backend layer of Dispro Game Manager. It supports the logic used by the game frontend and brings the project's services together within a modular architecture. The game and its website share a foundation organized around the needs of each title.
A shared foundation for different ways to play
DGM Server supports single-player, Steam co-op and multiplayer experiences. The backend provides a foundation for the logic used by the client in each mode, while modules let each game adapt that foundation to the experience it offers.
Single-player: backend support for the logic behind solo experiences.
Steam co-op: a service foundation for cooperative experiences integrated with Steam.
Multiplayer: support for the logic and services required by the game's shared experience.
Frontend logic connected to the backend
Within the DGM ecosystem, the logic used by the frontend relies on DGM Server. This separation organizes the game's presentation and backend services as parts of one project, with modules tailored to how it works.
Modularity lets each title build its foundation from the services it needs while retaining a common structure within the DGM ecosystem.
The game and its website in one ecosystem
DGM Server also powers the game's website. The web presence belongs to the project's architecture and uses its backend alongside the game client.
This approach brings the gameplay experience and its web presence together around the title's services, allowing both to evolve within one structure.
One franchise, multiple games
DGM Server supports the organization and creation of different games within a single franchise. Each title can have its own combination of modules and integration interfaces while retaining a shared technology foundation.
The franchise provides the shared framework; each game defines its needs. This structure allows the universe to expand with new projects and services tailored to each one.
Modular APIs and MCP integrations for each game
Each game has a modular arrangement of APIs and MCP integrations that connects its services to the applications and tools using them. Integrations are organized by title and module according to the project's needs.
Per-game APIs: organized interfaces for accessing each title's services.
Per-game MCP integrations: connections for compatible tools and assistants, tailored to each game's context.
Modular composition: services and integrations adapted to the scope of each project within the franchise.
DGM Server connects the client, services and website through a modular foundation built to accompany a game's development and the expansion of its franchise.
