> 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/keeper-bridge/keeper-bridge-server-installation.md).

# Keeper Bridge Server Installation

Installation of the Keeper Bridge service

Use the link below to install the latest Keeper Bridge:\
[Download Keeper Bridge](https://keepersecurity.com/bridge/KeeperBridge.zip)

1. &#x20;On the server, extract the zip file and then double click the KeeperEnterpriseBridge.msi file.
2. &#x20;If applicable, Process the User Account Control window.
3. &#x20;Select **Next** on the Welcome screen.
4. &#x20;Choose **I accept the agreement** and select **Next** on the End-User License Agreement screen.
5. &#x20;Accept the default installation location or browse for a new one and then select **Next**.&#x20;
6. &#x20;Click **Install** on the Ready to Install screen .
7. &#x20;Select **Finish** to complete the installation.

{% hint style="info" %}
The Keeper Bridge Client can be installed on multiple computers but the Keeper Bridge Service should only be installed on one server per instance.
{% endhint %}


---

# 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/keeper-bridge/keeper-bridge-server-installation.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.
