> 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/it/concepts/intermediate-concepts/topology.md).

# Topologia

La topologia di Devolutions Server descrive come si collegano il server web, il database e i gateway, coprendo i modelli di distribuzione all-in-one, suddivisi e DMZ.

La topologia in una distribuzione di Devolutions Server descrive come sono organizzati e collegati il server web, il database, i gateway e i client. I modelli comuni includono le installazioni tutto in uno, i server web e database separati e le architetture che collocano i componenti di Devolutions Gateway in una zona demilitarizzata per un accesso remoto sicuro.

Comprendere la propria topologia aiuta nella pianificazione della capacità, nella risoluzione dei problemi e nelle revisioni di sicurezza. Documentarla insieme alle casseforti e utilizzare una denominazione coerente per host e servizi rende più semplice per i nuovi amministratori capire come il traffico attraversa l'ambiente.

#### Argomenti correlati

* [Topologie](/server/it/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/it/concepts/intermediate-concepts/topology.md?ask=<question>&goal=<user_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.