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

# Installation

NVIDIA Run:ai is a Kubernetes-native orchestration and management platform designed to maximize GPU utilization for AI workloads.

## NVIDIA Run:ai System Components

NVIDIA Run:ai is made up of two components both installed over a [Kubernetes](https://kubernetes.io) cluster:

* **NVIDIA Run:ai control plane** - Provides resource management, handles workload submission and provides cluster monitoring and analytics.
* **NVIDIA Run:ai cluster** - Provides enhanced scheduling and workload management, extending Kubernetes native capabilities.

As part of the installation process, you will install:

* NVIDIA Run:ai [control plane](/self-hosted/getting-started/installation/install-using-helm/install-control-plane.md) that manages one or more clusters
* One or more NVIDIA Run:ai [clusters](/self-hosted/getting-started/installation/install-using-helm/helm-install.md)

Both the Nvidia Run:ai control plane and cluster/s require Kubernetes. In typical deployment, the control plane and first cluster are installed on the same Kubernetes cluster.

<figure><img src="https://1843187746-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZNGVYs8RM1KF89eNrzzE%2Fuploads%2Fgit-blob-898aaccba9be1e47c47f5ec9917c61875a9cbfeb%2Fself-hosted.png?alt=media" alt="" width="375"><figcaption></figcaption></figure>

## Installation Types

The self-hosted option is for organizations that cannot use a SaaS solution due to data leakage concerns. NVIDIA Run:ai self-hosting comes with two variants:

| Type       | Description                                                                           |
| ---------- | ------------------------------------------------------------------------------------- |
| Connected  | The organization can freely download from the internet (though upload is not allowed) |
| Air-gapped | The organization has no connection to the internet                                    |

## Software Artifact Sources

NVIDIA Run:ai software artifacts (container images and Helm charts) can be obtained from two sources:

| Source                   | Description                                                                                                    |
| ------------------------ | -------------------------------------------------------------------------------------------------------------- |
| NVIDIA NGC (Recommended) | The NVIDIA NGC catalog. Recommended for all new and existing installations.                                    |
| JFrog                    | The NVIDIA Run:ai artifact repository. JFrog artifacts are deprecated and will be removed in a future release. |

Before installing, complete the [Preparations](/self-hosted/getting-started/installation/install-using-helm/preparations.md) steps to set up access to your chosen artifact source.


---

# 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://run-ai-docs.nvidia.com/self-hosted/getting-started/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.