> For the complete documentation index, see [llms.txt](https://wiki.crosswatch.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.crosswatch.app/getting-started/installation.md).

# Installation

Choose an installation path for Docker or Unraid.

Choose the install path that fits your environment.

CrossWatch supports standard Docker setups and Unraid Community Apps.

### Install paths

{% columns %}
{% column %}

#### Installation

Use this for standard Docker, Docker Compose, Portainer, or NAS container UIs.

[View Installation](/getting-started/installation/docker-setup.md)
{% endcolumn %}

{% column %}

#### Unraid Apps

Use this if you install CrossWatch from the Unraid Community Apps catalog.

[View Unraid Apps](/getting-started/installation/unraid-apps.md)
{% endcolumn %}
{% endcolumns %}

### Memory usage

| Items  | Minimum |   Average |   Maximum | Idle after sync |
| ------ | ------: | --------: | --------: | --------------: |
| 2,500  |  88 MiB |  \~95 MiB | \~105 MiB |        \~95 MiB |
| 25,000 |  88 MiB | \~230 MiB | \~330 MiB |       \~225 MiB |
| 50,000 |  88 MiB | \~350 MiB | \~570 MiB |       \~370 MiB |

Measured container memory, excluding Docker Desktop overhead. Minimum is a fresh start before any sync. Maximum is reached while syncing with the Analyzer and dashboard pages open. Memory stops growing after the second sync.

Figures assume one pair. Each extra pair adds its own peak, and providers add roughly 30 MiB on the first sync for TLS connections and provider sessions.

All figures are measured container memory, excluding Docker Desktop overhead.\
Number of items can increase rapidly depending on the number of sync pairs and features you use.

### Quick guidance

Pick **Installation** if you want full control over volumes, ports, and runtime settings.

Pick **Unraid Apps** if you want the Unraid template to prefill the container basics.

For scheduled syncs, use [Container Run Once Mode](/crosswatch/command-line-interface-cli/container-run-once-mode.md).

After install, continue with [First-time setup](/getting-started/first-time-setup.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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.crosswatch.app/getting-started/installation.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 `build a script that syncs our docs to a CMS` 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.