> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/keeperpam/endpoint-privilege-manager/deployment/deployment-reference.md).
# Deployment Reference
**Audience:** IT admins deploying Keeper EPM across Windows, macOS, and Linux endpoints.
This section is your deep technical library for KEPM deployment. It contains detailed specifications, package formats, platform requirements, and behavior notes for the components you'll work with when packaging the agent, rolling it out to endpoints, validating installations, and troubleshooting deployment issues. Use these pages when you need exact installer arguments, supported OS versions, file and certificate locations, system extension and entitlement details, or signing and trust requirements—and when you want to understand how the agent installs, registers, and operates on each platform "under the hood."
Deployment reference content is intentionally precise and comprehensive. It's the right place to start when you're authoring MDM payloads, scripting silent installs, validating an agent registration, diagnosing a failed rollout from installer or system logs, or confirming how the agent interacts with a specific OS subsystem. When the Deployment guides walk you through a rollout at a procedural level, the Deployment Reference provides the authoritative detail behind every step.
---
# 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.keeper.io/keeperpam/endpoint-privilege-manager/deployment/deployment-reference.md?ask=&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.
