> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/concepts/intermediate-concepts/topology.md). # Topology Devolutions Server topology describes how the web server, database, and gateways connect, covering all in one, split, and DMZ deployment patterns. Topology in a Devolutions Server deployment describes how the web server, database, gateways, and clients are arranged and connected. Common patterns include all in one installations, split web and database servers, and designs that place Devolutions Gateway components in a demilitarized zone for secure remote access. Understanding your topology helps with capacity planning, troubleshooting, and security reviews. Documenting it alongside vaults and using consistent naming for hosts and services makes it easier for new administrators to understand how traffic flows through the environment. #### Related topics * [Topologies](/server/overview-of-devolutions-server/topologies.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.devolutions.net/server/concepts/intermediate-concepts/topology.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.