> 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/about-crosswatch.md).

# About CrossWatch

Self-hosted watchlist, history, ratings, and resume progress sync plus real-time scrobbling

CW is a self-hosted **all-in-one tool** for sync, scrobbling, captures, and recovery.

It keeps **watchlists**, **history**, **ratings**, and **progress** aligned across your media servers and trackers.

Run it in Docker. Keep control of your data. Manage everything from one web UI.

{% hint style="success" %}
CW is easy to start and flexible enough to grow with your setup.
{% endhint %}

### What makes it flexible

* Use **profiles**, **pairs**, and **Watcher routes** for multi-account setups.
* Improve matching with **TMDb** and **Anime ID Mapping**.
* Recover more safely with local state and **captures**.

### Flexible real-time scrobbling

**Watcher** uses **routes mode**.

Each route maps one media server profile to one tracker profile.

That means you can:

* send playback from one server to multiple tracker targets
* split users or servers into separate routes
* run multiple media servers and trackers in one setup

### How it works

* **Providers** connect media servers and trackers.
* **Profiles** group multiple accounts or servers under one provider.
* **Pairs**, **runs**, and local **state** drive sync planning and scheduling.

### Start here

* [Installation](/getting-started/installation.md)
* [First-time setup](/getting-started/first-time-setup.md)
* [Configure Pairs](/crosswatch/settings/configure-pairs.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://wiki.crosswatch.app/about-crosswatch.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.