> 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/checklist-for-native-team-workspaces/select-a-native-team-workspace.md).

# Select a Native Team workspace

This article is intended for teams planning to use Devolutions Server or Devolutions Cloud as their workspace.

To assist with selecting the appropriate workspace, here is a set of concerns and the list of workspaces that can serve in such a context.

{% hint style="danger" %}
When choosing a non-on-premises workspace, it is important to account for the security of data both at rest and in transit. It is strongly recommended to further encrypt data using a master key for file-based solutions or a [security provider](https://docs.devolutions.net/rdm/commands/administration/security-providers/) for [advanced workspaces](https://docs.devolutions.net/rdm/workspaces/workspace-types/native-workspaces/), ensuring that only authorized parties can access the data.
{% endhint %}

<table><thead><tr><th width="449">CONCERN</th><th align="center">Devolutions Server</th><th align="center">Devolutions Cloud</th></tr></thead><tbody><tr><td>Self-hosted data</td><td align="center">X</td><td align="center"></td></tr><tr><td>Cloud-hosted data</td><td align="center"></td><td align="center">X</td></tr><tr><td>Unaccessible database to end users</td><td align="center">X</td><td align="center">X</td></tr><tr><td>Encryption at rest and in transit</td><td align="center">X</td><td align="center">X</td></tr><tr><td><a href="https://blog.devolutions.net/2023/05/unraveling-zero-knowledge-and-zero-trust-concepts/">Zero-knowledge</a> on sensitive data</td><td align="center"></td><td align="center">X</td></tr><tr><td>Privileged Access Management (PAM) module</td><td align="center">X</td><td align="center">X</td></tr><tr><td>AD accounts used for authentication</td><td align="center">X</td><td align="center"></td></tr><tr><td>AD group membership used to assign permissions</td><td align="center">X</td><td align="center">X</td></tr><tr><td>Activity logs</td><td align="center">X</td><td align="center">X</td></tr><tr><td>Data accessible globally</td><td align="center">Note</td><td align="center">X</td></tr><tr><td>Just-in-time (JIT) connections via Devolutions Gateway</td><td align="center">X</td><td align="center">X</td></tr></tbody></table>

#### Note

Exposing a Devolutions Server instance to the Internet without protection from DDoS attacks is not recommended. It is essential to use strong passwords and obscure account names that cannot be easily deduced through social data mining techniques.


---

# 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:

```
GET https://docs.devolutions.net/rdm/getting-started/checklist-for-native-team-workspaces/select-a-native-team-workspace.md?ask=<question>
```

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.
