> For the complete documentation index, see [llms.txt](https://doc.commandersact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.commandersact.com/configure/administration/domain-management/on-premise-proxy.md).

# On-Premise Proxy

1st party collection through your own proxy

The On-Premise Proxy is a feature that orchestrates the communication between your website/app and the Commanders Act platform. A proxy is a sort of intermediary, routing information back and forth between two points—in this case, your website or app and Commanders Act.

The On-Premise Proxy is designed to be installed by your IT team on your own servers. This allows for control and flexibility in managing the data flow between your system and Commanders Act.

For the installation and technical details, your DevOps team can refer to the technical documentation available at the following link:

{% embed url="<https://hub.docker.com/r/commandersact/ca-trk-proxy>" %}


---

# 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://doc.commandersact.com/configure/administration/domain-management/on-premise-proxy.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.