> For the complete documentation index, see [llms.txt](https://docs.kodesage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kodesage.ai/deploy-kodesage/self-hosted-embedder-installation.md).

# Self-hosted Embedder installation&#x20;

Self-hosted Embedder installation guide

**Prerequisites**&#x20;

* A system with Ubuntu with docker and docker-compose installed and with the latest Nvidia driver for the GPU-s in the system.&#x20;
* Install the [Nvidia Container Toolkit.](https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/install-guide.html)&#x20;
* Install git-lfs with the command: sudo apt-get install git-lfs&#x20;
* The embedder service can also be runned with multiple instances if necessary.&#x20;
* Copy the provided tar file and the embedder-wrapper folder into the server, where the embedder service will be hosted. After that, run this command:&#x20;
* docker load --input embedder-service.tar&#x20;

For running multiple instances modify the docker-compose file, copy the part after the ‘services’ as many times as many instances you would like to run. Modify the service and the container name for each copy. Also modify the ports so the instances could run separately.&#x20;

The model will be downloaded at the first start of the container.&#x20;

**Start the instances**&#x20;

Go back to the root folder and execute this command:&#x20;

* docker compose up –d&#x20;

The embedder service should start without errors.&#x20;

**Load balancers**&#x20;

If you are running multiple instances of LLMs and/or embedders, you will need separate load balancers which will handle the concurrent loads. We will provide you with further instructions for installing load balanacers during the onboarding period.


---

# 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.kodesage.ai/deploy-kodesage/self-hosted-embedder-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.
