> 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/privileged-access-manager/on-prem-connection-manager.md).

# Self-Hosted Options

Deploy and operate Keeper in a self-hosted environment

## Overview

Keeper Security provides both Cloud and Self-Hosted options for customer deployments.

**Self-Managed Keeper ("SMK")** provides a fully self-hosted Keeper deployment. It is designed for organizations that require complete operational control, including air-gapped environments.

Your organization manages the infrastructure and services that support the deployment. Self-Managed Keeper is licensed separately from KeeperPAM.

### Self-Managed Keeper

Use Self-Managed Keeper when your deployment requires:

* A self-hosted or air-gapped environment
* Customer-managed infrastructure and operations
* Control over deployment services and data storage

Learn more about [Self-Managed Keeper](/keeperpam/self-managed-keeper/self-managed-keeper-overview.md)

***

### Keeper Connection Manager

Keeper Connection Manager (KCM) is a standalone remote access gateway. It is typically deployed as a bastion host for controlled access to remote infrastructure.

KCM provides session recording and privileged session management. It can also retrieve credentials from the Keeper Vault through its Keeper Secrets Manager integration.

KCM is available with a KeeperPAM license. It is distinct from Self-Managed Keeper, which requires separate licensing.

Learn more about [Keeper Connection Manager](/keeper-connection-manager/readme.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://docs.keeper.io/keeperpam/privileged-access-manager/on-prem-connection-manager.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.