> 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/rdm/getting-started/workspaces/workspace-types.md).

# Workspace types

Compare Remote Desktop Manager workspace types, Devolutions Server, Devolutions Cloud, Microsoft Azure SQL, SQL Server, CyberArk, SQLite, and XML, to pick the right fit.

Remote Desktop Manager supports multiple types of workspaces. First decide which workspace you are going to use. For guidance on selecting the right workspace, check out our Devolutions Academy course: [Choosing the right workspace](https://academy.devolutions.net/student/path/1916054/activity/2667043).

Upon initial installation, Remote Desktop Manager uses a local workspace which is an SQLite database.

| NAME                     | DESCRIPTION                                                                                                                                                                                                                                                                                              |
| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Devolutions Server**   | Remote Desktop Manager uses Devolutions Server to store session information. For more information, consult [Devolutions Server](/rdm/getting-started/workspaces/workspace-types/native-workspaces/devolutions-server.md).                                                                                |
| **Devolutions Cloud**    | Remote Desktop Manager connects to the Devolutions Cloud vault. For more information, see the [products features and highlights](https://devolutions.net/hub/) and consult [Devolutions Cloud](/rdm/getting-started/workspaces/workspace-types/native-workspaces/devolutions-cloud.md).                  |
| **Microsoft Azure SQL**  | Remote Desktop Manager uses the Microsoft cloud platform to save and manage all sessions. For more information, consult [Azure SQL](/rdm/getting-started/workspaces/workspace-types/alternative-workspaces/microsoft-azure-sql.md).                                                                      |
| **Microsoft SQL Server** | Remote Desktop Manager uses SQLServer to save and manage all sessions. This is one of the available workspaces for a multi-user environment. For more information, consult [SQL Server (MSSQL)](/rdm/getting-started/workspaces/workspace-types/alternative-workspaces/microsoft-sql-server.md).         |
| **CyberArk**             | The CyberArk workspace makes it possible to connect directly to your CyberArk and launch your sessions with ease, without the added complexity of an SQL Server workspace. For more information, consult [CyberArk](/rdm/getting-started/workspaces/workspace-types/alternative-workspaces/cyberark.md). |
| **SQLite**               | Remote Desktop Manager uses an SQLite database to store session information. For more information, consult [SQLite](/rdm/getting-started/workspaces/workspace-types/local-workspaces/sqlite.md).                                                                                                         |
| **XML**                  | Remote Desktop Manager saves the settings directly in a file in the XML format. For more information, consult [XML](/rdm/getting-started/workspaces/workspace-types/local-workspaces/xml.md).                                                                                                            |

#### See also

* [Devolutions Academy – Understanding vaults](https://academy.devolutions.net/student/activity/3266630)


---

# 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/rdm/getting-started/workspaces/workspace-types.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.