# Architecture Overview ### Node Provider and dApp Provider These entities supply resources to the network. * **Node Provider**: Manages the infrastructure required to run nodes within the network. * **dApp Provider**: Responsible for deploying and managing decentralized applications. *** ### Dashboard Acts as a centralized interface for management and monitoring. * Facilitates interaction between clients, providers, and the network. * Enables dApp and node management through an intuitive interface. *** ### Client Represents the end users interacting with the system. * Communicates with the **dApp Matchmaking** layer to access appropriate nodes within the platform. *** ### dApp Matchmaking A service layer that helps connect clients to nodes that make up the subnetwork of their session. *** ### Node Represents the network participants that host the session logic for decentralized applications. * In subnetworks, nodes are assigned roles as **Coordinator** or **Witness**. * Interacts with the **Registry** to fetch dockerized session logic executables. *** ### Registry * Accepts zipped session logic executables from clients for verification and containerization. * Initially hosts a private Docker registry, with future plans to push images to a decentralized storage system. *** ### System Contract A smart contract deployed on a blockchain network. * Verifies proofs for ended sessions to determine correctness and reward distribution. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://alliance-games.gitbook.io/alliance-games-gitbook/multiplayer-network/architecture-overview.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.