> 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/overview/topologies.md).

# Topologies

You can install Devolutions Server instances using different topologies. The following examples illustrate several potential configurations, depending on your needs.

### Single server topology

For a small team of up to 20 users, install a Devolutions Server instance and a corresponding Microsoft SQL Server (MSSQL) instance on the same machine. Depending on use, you may find resources become constrained with greater than 20 active users.

### Dual server topology (recommended)

A recommended Devolutions Server configuration is one server for the instance and another for the Microsoft SQL Server instance. In this configuration, Devolutions Server instance performance is less affected by database resource contention.

### High-availability database topology

Database availability groups allow for active-passive failover configurations to ensure high database availability. When the active database server becomes unavailable, the passive database failover server switches seamlessly in the background, providing uninterrupted Devolutions Server instance access.

### High-availability load-balancing topology

Devolutions Server can combine the previously mentioned high-availability database topology with a [load-balanced Devolutions Server instance for maximum availability](https://docs.devolutions.net/server/kb/how-to-articles/deploy-high-availability-load-balanced-env/). Using physical or software-based load balancing, you can direct users across multiple Devolutions Server instances that connect to database instances in an availability group.

### Manual failover topology

For customers who seek a simplified topology for their system, but need redundancy, you can use two duplicated Devolutions Server instances and direct each to the same Microsoft SQL Server database. Users can manually toggle between servers if one becomes unresponsive by registering both instances as separate workspaces in their Devolutions applications, such as Remote Desktop Manager or Devolutions Password Manager.

#### See also

* [Devolutions Academy – Choosing your topology](https://academy.devolutions.net/student/path/2942210/activity/4493545)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.devolutions.net/server/overview/topologies.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.