> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-pt/productos/object-storage/details/compatible-clients.md).

# Clientes compatíveis

O software de cópia de segurança, os NAS e os clientes S3 que ligam ao repositório.

Ao falar S3 padrão, o repositório liga-se a uma grande variedade de software sem desenvolvimentos à medida. Esta é uma referência de categorias e ferramentas habituais; qualquer Cliente compatível com S3 funciona.

| Categoria                      | Ferramentas habituais                  | Utilização típica                                |
| ------------------------------ | -------------------------------------- | ------------------------------------------------ |
| Software de cópia de segurança | Veeam, Acronis, Bacula, Veritas, Ahsay | Destino de cópias de segurança                   |
| NAS                            | QNAP                                   | Cópia ou sincronização do NAS para o repositório |
| Clientes de desktop            | Cyberduck, S3 Browser                  | Explorar e mover objetos manualmente             |
| Linha de comandos              | AWS CLI, s3cmd, rclone                 | Automação e scripts                              |

> #### 📘 O padrão S3 é a vantagem
>
> Não dependes de um Cliente concreto: se o software fala S3, conecta. Isso permite-te escolher a ferramenta que já usas com os teus Clientes em vez de te adaptares a uma proprietária.

### Onde continuar

* Os dados e comandos para conectar: [Credenciais e acesso S3.](https://docs.plenit.com/docs-pt/productos/object-storage/details/credentials-and-s3-access.md)
* Os passos concretos por ferramenta estão no [Como fazer](https://docs.plenit.com/docs-pt/productos/object-storage/how-to.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.plenit.com/docs-pt/productos/object-storage/details/compatible-clients.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.
