> 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/enterprise-guide/keeperpam-privileged-access-manager/keeper-connection-manager.md).
# Keeper Connection Manager
Instantly access your infrastructure with zero-trust security
Keeper Connection Manager (KCM) is a self-hosted, agentless remote desktop gateway that provides secure access to desktops, servers, databases and web applications, from a web browser.
KCM is a fully self-hosted connection manager that can be deployed to any on-prem, public cloud, or private cloud environment.
### Features
* RDP, SSH, Kubernetes (K8s), databases, and VNC protocols
* Remote Browser Isolation
* Session Recording
* Privileged Session Management
* Cloud Instance Discovery
* Multi-User Session Sharing
* Role-Based Access Controls
* Two-Factor Authentication
* SSO, Active Directory, and LDAP Integration
* Custom Branding
Keeper Connection Manager can be installed through Docker or native Linux binaries.
### Protocols Supported
* RDP
* SSH
* MySQL
* PostgreSQL
* SQL Server
* VNC
* Kubernetes
* Remote Browser Isolation (HTTP/HTTPS)
### Installation
Keeper Connection Manager is installed as a gateway in your cloud, virtual, or on-prem environment. There are several methods of deployment, depending on your requirements and desired feature set.
### Resources
* [Keeper Connection Manager](https://www.keepersecurity.com/connection-manager.html) homepage
* [Full Documentation](https://docs.keeper.io/keeper-connection-manager/)
---
# 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/enterprise-guide/keeperpam-privileged-access-manager/keeper-connection-manager.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.
