> For the complete documentation index, see [llms.txt](https://docs.couchdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.couchdrop.io/storage/local-storage/server-requirements.md).

# Server Requirements

Learn about requirements for connecting Couchdrop to file servers

## Overview

The Couchdrop Windows / macOS Agent connects on-premises file servers to Couchdrop.

The agent runs as an executable on a Microsoft Windows or macOS host and can also run as a service.

### Server requirements

The resources required by the agent can vary depending on the types and volume of transfers involved.

For most deployments, we recommend:

| Component           | Recommendation |
| ------------------- | -------------- |
| **CPU**             | 4–8 vCPU cores |
| **Memory**          | 16 GB          |
| **Free disk space** | 32 GB          |

{% hint style="info" %}
Higher-volume transfers may require additional CPU, memory, disk space, or network capacity.
{% endhint %}

### Supported Windows versions

The following Microsoft Windows versions have been tested for use with the Couchdrop Agent.

| Operating system       | Supported |
| ---------------------- | --------- |
| Windows XP             | No        |
| Windows 10             | Yes       |
| Windows Server 2012 R2 | No        |
| Windows Server 2016    | Yes       |
| Windows Server 2019    | Yes       |
| Windows Server 2022    | Yes       |

{% hint style="info" %}
For help configuring the agent on an operating system that is not listed above, contact [**support@couchdrop.io**](mailto:support@couchdrop.io).
{% endhint %}

### Software requirements

The Windows Agent requires **Microsoft .NET Framework 4.7.2**.

Make sure this version of the .NET Framework is installed before opening or running the agent.

### Network requirements

Transfer performance depends on both your internal network and your external internet connection.

For environments transferring high volumes of files or data, we recommend using the highest available uplink speed, with a **1 Gbps fiber connection** where possible.

If you experience performance issues with the agent:

* Run a speed test from the agent host.
* Check the available upload and download bandwidth.
* Check the internal connection between the agent and your file server or network storage.
* When applicable, select a Couchdrop data region that is geographically close to the agent.

### Firewall requirements

The Couchdrop Agent communicates with the Couchdrop control plane and APIs exclusively over **HTTPS**. No additional inbound ports need to be opened.

If your organization uses a proxy server, firewall, or web filter that restricts outbound traffic, allow access to:

* `fileio.couchdrop.io`
* `api.couchdrop.io`
* `*.couchdrop.io`
* `8.8.8.8`
* `8.8.4.4`

{% hint style="info" %}
If you continue to experience connectivity issues after allowing these destinations, contact [**support@couchdrop.io**](mailto:support@couchdrop.io).
{% endhint %}


---

# 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.couchdrop.io/storage/local-storage/server-requirements.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.