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

# Deploy

**Overview**

This guide provides step-by-step instructions for setting up an environment that integrates multiple services like AIMETA.

**Prerequisites**

* Necessary API keys and environment variables as required by specific services.
* Ensure NVIDIA GPU drivers are installed if utilizing GPU support for the LLM.

**Service Configuration**

1. **LLM-GPU Services**
   * **Purpose:** Hosts a Large Language Model with optional GPU support.
   * **Configuration:**
     * Operates within a Linux environment.
     * Utilizes all available NVIDIA GPUs for the GPU-enabled configuration.
2. **Pull-Model Service**
   * **Purpose:** Manages the model pulling for the LLM service.
   * **Configuration:**
     * Built from Linux environment.
     * Depends on environment variables such as model URLs and API keys.
     * Connected to the `net` network and dependent on `llm-gpu`.
3. **Database Service**
   * **Purpose:** Utilizes Neo4j for graph-based data storage.
   * **Configuration:**
     * Exposes ports for external connectivity.
     * Uses persistent storage volumes.
     * Configured with environment variables for authentication and plugins.
4. **Loader Service**
   * **Purpose:** Loads data into the Neo4j database.
   * **Configuration:**
     * Custom Dockerfile.
     * Interacts with Neo4j and depends on the database and pull-model services.
     * Utilizes API keys and environment configurations.
5. **Bot Services**
   * **General Bot Configuration:**
     * Custom Dockerfile.
     * Utilizes `net` network and Neo4j database connections.
   * **Voice Bot Specifics:**
     * Handles tasks related to Voice processing.
6. **API Service**
   * **Purpose:** Provides an API interface for external communications.
   * **Configuration:**
     * Built from a custom Dockerfile.
     * Health checks implemented.
     * Ports exposed for external connectivity.
     * Depends on the database and pull-model service completion.

**Health Checks**

* Implemented in services such as the API and chrome plugin to ensure operational status before being available for use.

<figure><img src="/files/7VcWqK9TnuF6NxTtKDnP" alt=""><figcaption></figcaption></figure>

{% code fullWidth="true" %}

```markdown
```

{% endcode %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.aimeta.world/deploy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.